[CQM-1755] CMS73v4VTE3_understanding of Numerator condition Created: 11/04/15  Updated: 12/09/15  Resolved: 12/09/15

Status: Closed
Project: eCQM Issue Tracker
Component/s: Measure

Type: EH/CAH eCQMs - Eligible Hospitals/Critical Access Hospitals Priority: Minor
Reporter: michelle (Inactive) Assignee: Joelencia Leflore
Resolution: Answered Votes: 0
Labels: None

Contact Name: Michelle
Solution: Thank you for reporting this issue. The First operator should apply to the Union of $MedicationWarfarinParenteralAnticoagulantOverlap. In the upcoming annual update, we will revisit the logic to ensure the scope of application of the First operator is clear.

The remaining logic relies on occurrences to constrain $MedicationWarfarinParenteralAnticoagulantOverlap​, to the first instance. For more information on how occurrences work with subset operators, such as the First operator, please refer to section 4.5.1 Subset Operators and Specific Occurrences​ of the ​eCQM Measure Logic Guidance (https://www.cms.gov/Regulations-and-Guidance/Legislation/EHRIncentivePrograms/Downloads/eCQM_LogicGuidance_v1-11_061915.pdf), which is published along with eCQM specifications.
Solution Posted On:
2016 Reporting Period EH eCQMs:
CMS73v4/NQF0373
Impact: high

 Description   

In the Numerator section, this mentiones as "First: Union of"

◾First: Union of: ◾$MedicationWarfarinParenteralAnticoagulantOverlap starts during Occurrence A of $EncounterInpatient
◾$MedicationWarfarinParenteralAnticoagulantOverlap starts during ◾"Encounter, Performed: Emergency Department Visit" <= 1 hour(s) ends before or concurrent with start of Occurrence A of $EncounterInpatient

◾>= 4 day(s) starts before start of ◾Most recent: "Occurrence A of Medication, Administered: Parenteral Anticoagulant" starts during Occurrence A of $EncounterInpatient

What should be considered FIRST is it the Medications Or the First of the entire block.
Also even if the First of any is considered going further in the measure its not validated further.


Generated at Tue Mar 18 10:50:42 EDT 2025 using Jira 9.12.16#9120016-sha1:6bee0863f3e6dbb91e4be2d992a3b6761c21c9e0.