-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add maturity level annotation and/or javadoc to the fhir-model resource classes #2145
Comments
The maturity level of each resource is captured in its StructureDefinition via the following resource-level extension:
|
lmsurpre
added a commit
that referenced
this issue
Mar 25, 2021
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 25, 2021
Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
JohnTimm
added a commit
that referenced
this issue
Mar 25, 2021
issue #2145 - add MaturityLevel javadoc and annotation to model classes
lmsurpre
added a commit
that referenced
this issue
Mar 25, 2021
I had used the wiki page at https://confluence.hl7.org/display/FHIR/FHIR+Maturity+Model to determine what was draft/trial/normative, but in the StructureDefinition resources there was a different field for this. Net: my prior commit used "Trial Use" for FFM5, but the normative resources actually have a level of 5 as well...we just needed to pull the status from the other extension. 1. generate a code subtype class for StandardsStatus 2. change MaturityLeve(value) to Maturity(level, status) 3. regenerate the model Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 25, 2021
I had used the wiki page at https://confluence.hl7.org/display/FHIR/FHIR+Maturity+Model to determine what was draft/trial/normative, but in the StructureDefinition resources there was a different field for this. Net: my prior commit used "Trial Use" for FFM5, but the normative resources actually have a level of 5 as well...we just needed to pull the status from the other extension. 1. generate a code subtype class for StandardsStatus 2. change MaturityLeve(value) to Maturity(level, status) 3. regenerate the model Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 26, 2021
issue #2145 - set the StandardsStatus appropriately
They are there, and I can see them in the code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
HL7 FHIR defines a maturity model so that they can ship content at different levels of maturity in a single cohesive specification.
From https://confluence.hl7.org/display/FHIR/FHIR+Maturity+Model :
Currently, the IBM FHIR Server supports all resource types, irregardless of maturity level.
However, users of the model should be mindful of the maturity level because depending on a normative resource is a lot different than depending on a draft one (in terms of stability and future-proofing your application).
Describe the solution you'd like
To make it easier for users to consider this information, we should put it right at their fingertips, in the javadoc for the resource class.
Additionally, I would like to define a new annotation to make it possible to programatically determine the maturity level of a given resource type at runtime. The main driver behind this is that I'd like to be able to easily create "classes" of resources based on their maturity level for #819
Describe alternatives you've considered
Acceptance Criteria
Additional context
Hopefully this could help us evolve our story on backwards-compatibility as we move to FHIR R4B and, eventually R5.
The text was updated successfully, but these errors were encountered: