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
define "Has Medical or Patient Reason for Not Ordering Beta Blocker for LVSD":
exists ( ["MedicationNotRequested"] NoBetaBlockerOrdered
with AHA."Heart Failure Outpatient Encounter with History of Moderate or Severe LVSD" ModerateOrSevereLVSDHFOutpatientEncounter
such that NoBetaBlockerOrdered.authoredOn during ModerateOrSevereLVSDHFOutpatientEncounter.period
where NoBetaBlockerOrdered.medication in "Beta Blocker Therapy for LVSD"
and ( NoBetaBlockerOrdered.reasonCode in "Medical Reason"
or NoBetaBlockerOrdered.reasonCode in "Patient Reason"
)
)
With the correct set of patients, we should see “NoBetaBlockerOrdered.medication” highlighted. However, it is not highlighted as seen below:
The root cause for lack of highlighting is that the ELM is missing the localId for the expression. To see this, the generated ELM for this expression is as follows:
With the arrows pointing at the location where a localId should be found.
What’s particularly odd is that a localId for this expression does exist in the annotations:
It is likely a bug that the localId exists in the annotation, but not the ELM expression. If the annotation is added to the ELM as expected:
Then highlighting works as expected (Note: the localId could also be placed in the “code” clause):
The text was updated successfully, but these errors were encountered:
This issue arises from ticket projecttacoma/fqm-execution#290 coming from a MADiE user issue.
For this CQL:
With the correct set of patients, we should see “NoBetaBlockerOrdered.medication” highlighted. However, it is not highlighted as seen below:
The root cause for lack of highlighting is that the ELM is missing the localId for the expression. To see this, the generated ELM for this expression is as follows:
With the arrows pointing at the location where a localId should be found.
What’s particularly odd is that a localId for this expression does exist in the annotations:
It is likely a bug that the localId exists in the annotation, but not the ELM expression. If the annotation is added to the ELM as expected:
Then highlighting works as expected (Note: the localId could also be placed in the “code” clause):
The text was updated successfully, but these errors were encountered: