-
Bug/Issue
-
Resolution: Referred to External Party for Resolution
-
Critical
-
None
-
MADiE
-
QI-Core
-
Coronary Artery Disease (CAD): Beta-Blocker Therapy-Prior Myocardial Infarction (MI) or Left Ventricular Systolic Dysfunction (LVEF <40%)FHIR
-
466e5d36-1e01-478b-9dcb-edac33594dd5
-
QI-Core/CQL
-
MedNotOrderedPatRsn
-
Negation test cases using notDoneValueSet extension will not pass. This impacts various measures.
-
The test case mentioned in this ticket is failing. I suspect this is related to the use of the notDoneValueSet extension in the JSON. In QI-Core 4.1.0, a notDoneValueSet extension for handling a value set for a negated event was introduced. This enables negation for every event in the value set for the respective resource (e.g., MedicationRequest for MedicationNotRequested) - e.g., the "Beta Blocker Therapy for LVSD" value set, which is in use in the "Has Medical or Patient Reason for Not Ordering Beta Blocker for LVSD" definition. An example of the notDoneValueSet extension is exampled here. This capability is not working in MADiE currently. My understanding is that this issue is due to this not being a part of cql-execution, which still lists this feature as something to be implemented - https://github.com/cqframework/cql-execution/issues/296.
Without this feature, users will have to handle this issue at the logic level. At least 2 CQL expressions will be needed for every code in the respective value set - depending on whether the code system has been defined for the code or not. This will proliferate codes and CQL expressions in the library. Note that some value sets have hundreds of codes. In this case, it would be approximately 50 separate entries. In addition, a resource entry would be required for each code in the value set in the test case JSON.
When will this capability be available?