Add direct reference codes to manifest during $release#665
Conversation
|
Formatting check succeeded! |
8ff4c3e to
9c1375b
Compare
9c1375b to
051b0f5
Compare
|
Copying question from the related issue here: "Is it safe to assume that STU4 will always have 'cqfm-directReferenceCode' and STU5 will always have 'cqf-directReferenceCode' or are both extension URLs valid for both versions?" This implementation assumes the former. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #665 +/- ##
============================================
+ Coverage 71.52% 71.55% +0.03%
Complexity 153 153
============================================
Files 475 475
Lines 22270 22301 +31
Branches 2868 2873 +5
============================================
+ Hits 15928 15957 +29
Misses 4922 4922
- Partials 1420 1422 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
brynrhodes
left a comment
There was a problem hiding this comment.
Test needs fixup on the cqf- extension spelling, it's an extension pack extension, so it's URL is just http://hl7.org/fhir/StructureDefinition/cqf-directReferenceCode, (i.e. remove the us/cqfmeasures part from the canonical)
|



Update $release operation to gather any direct-reference codes referenced by component measures and add them to the manifest, using the directReferenceCode extension slice on the root of the release manifest.
Functionality handles STU4/STU5+, works with cqfm-directReferenceCode (STU4) and cqf-directReferenceCode (STU5) in the Measure source, output is always cqf-directReferenceCode extensions in the Manifest because cqfm-directReferenceCode isn't allowed in a CRMIManifest.