You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create all encompassing CQL file to allow for generating test data for unit testing. The eventual goal being that Measure Evaluation processes and logic can have basic resources used to validate specific scenarios are performing correctly, instead of using complex scenarios that are difficult to root cause issues in.
This is found in SimpleCQL.cql
The overall design allows for one Library and CQL to be used for constructing any MeasureScoringType and a TestDataGeneration class to create patient populations of varying sizes.
The scope of this initial change is aimed at these areas:
Measure SupplementalDataElements
Measure EvaluatedResources
Measure Stratifier and Stratum
This will remove test classes and associated test data (if not used by other tests):
MeasureProcessorSdeAddCriteriaExtensionTest
MeasureProcessorSdeInstanceExpInclLibTest
MeasureProcessorSdeInstanceExpressionTest
MeasureProcessorSdeSanityTest
StratifierMeasureProcessorTest
EvaluatedResourcesTest
Testing Enhancements
This will also introduce additional testing on areas by introducing:
SelectedContainedResources test class for SDE tests to perform more granular checks on values
Enhancing SelectedReference class for evaluatedResources checks
SelectedStratifier tests to validate format differences between Individual/populations as well as stratification components vs values.
Stratification of Measure populations must be done in the same type of the stratum population, this is to allow for intersection of resourcetypes to be effective. Encounter populations can't intersect with Patient based results.
Stratification of Resource based measures (like an encounter) could previously not be done due to lack of implementation. This is now allowed.
"Supplemental Data Elements SHALL be included within the supplementalData element using a usage element of supplemental-data."
supplemental Data elements now require 'usage' to specify a code of "supplemental-data" in order to be compliant for a MeasureDefinition for R4. If this value is missing, it will throw an error before evaluating a Measure.
The text was updated successfully, but these errors were encountered:
Testing Simplification
Create all encompassing CQL file to allow for generating test data for unit testing. The eventual goal being that Measure Evaluation processes and logic can have basic resources used to validate specific scenarios are performing correctly, instead of using complex scenarios that are difficult to root cause issues in.
This is found in SimpleCQL.cql
The overall design allows for one Library and CQL to be used for constructing any MeasureScoringType and a TestDataGeneration class to create patient populations of varying sizes.
The scope of this initial change is aimed at these areas:
This will remove test classes and associated test data (if not used by other tests):
Testing Enhancements
This will also introduce additional testing on areas by introducing:
Resource Based Measure Stratification
In updating StratifierDef execution logic, this also now enforces updates made to https://build.fhir.org/ig/HL7/cqf-measures/measure-conformance.html#stratification
Stratification of Measure populations must be done in the same type of the stratum population, this is to allow for intersection of resourcetypes to be effective. Encounter populations can't intersect with Patient based results.
Stratification of Resource based measures (like an encounter) could previously not be done due to lack of implementation. This is now allowed.
SDE usage code 'supplemental-data'
per https://build.fhir.org/ig/HL7/cqf-measures/measure-conformance.html#supplemental-data-elements
"Supplemental Data Elements SHALL be included within the supplementalData element using a usage element of supplemental-data."
supplemental Data elements now require 'usage' to specify a code of "supplemental-data" in order to be compliant for a MeasureDefinition for R4. If this value is missing, it will throw an error before evaluating a Measure.
The text was updated successfully, but these errors were encountered: