update artifact types to include publishable fields #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Create new CRMIRepositoryMeasure and CRMIRepositoryLibrary types that implement CRMIPublishable (in addition to CRMIShareable) according to https://hl7.org/fhir/uv/crmi/StructureDefinition-crmi-publishablemeasure.html and https://hl7.org/fhir/uv/crmi/StructureDefinition-crmi-publishablelibrary.html
New behavior
The
date
field is now required for a Measure artifact, and bothdate
andtype
are required for Library. This also required an update to_elements
to include required fields.Code changes
date
s (andtype
s where applicable) in code and in test structures_elements
projection indbOperations
inputUtils
to check fordate
andtype
as neededTesting guidance
npm run check:all
Note that date cannot be easily be updated in the front end at the moment. Do we want an additional input field for that? Or we could default it to current date when it's created.
TBD: How do we want to update the capability statement? Particularly, do we want to include a
profile
on the measure and library resource description, defined asBase System profile for all uses of resource
.