[MAT-7966] Use DataRequirementsProcessor to build Data Requirements for Included Libraries #269
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.
MADiE FHIR SERVICE
Jira Ticket: MAT-7966
(Optional) Related Tickets:
Summary
Use Data Requirements Processor (DRP) to build Data Requirements for Included Libraries instead of creating them manually from the ANTLR parse of the CQL.
With the inclusion of US-Core and QI-Core Profiles, we need to use the DRP to properly typecast Profile based Types to their FHIR relative. The Parser is limited to the CQL text and will build Data Requirements such as "QICore Simple Observation" (instead of "Observation"), which will cause the downstream FHIR converter (R4 to R5) to error out.
Note: We have to perform the R4 to R5 conversion because we're using the R5 Liquid Engine to generate the Human Readable. The R4 Liquid Engine doesn't have the necessary support to process the provided Liquid templates.
All Submissions
DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.
Reviewers
By Approving this PR you are attesting to the following: