[CQM-3462] CLONE - NQF 69: Diagnosis of URI and exclusion diagnosis are documented on same encounter Created: 02/04/19  Updated: 04/30/19  Resolved: 04/30/19

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

Type: EC eCQMs - Eligible Clinicians Priority: Moderate
Reporter: Aniek Valentine (Inactive) Assignee: Mathematica EC eCQM Team (Inactive)
Resolution: Done Votes: 0
Labels: None

Issue Links:
Cloners
clones CQM-1125 NQF 69: Diagnosis of URI and exclusi... Closed
Solution: Thank you for your inquiry. In the example you provide, where URI and an exclusion diagnosis are documented on the same encounter, the patient would qualify as an exclusion, as the competing diagnosis can occur anytime on the same day.
This is due to timing of the diagnosis, specifically the “day of” timing, which under definition ‘Has Competing Diagnosis for Upper Respiratory Infection’ states that “…competing condition starts 3 days or less after day of start of EncounterWithURI.ValidEncounter.relevantPeriod”.
Solution Posted On:
2015 Performance Period EP eCQMs :
CMS154v1/NQF0069
Impact: High
Comment Posted On:

 Description   

NQF 0069: If the diagnosis of URI and exclusion diagnosis (Competing Condition for Respiratory Condtions) are documented on same encounter, should the patient quality as an exclusion? The text in the measure leads one to beleive it should be a different encounter than the URI encounter. Please advise.



 Comments   
Comment by Mathematica EC eCQM Team (Inactive) [ 02/19/19 ]

We apologize for the delay in providing a response for your question. We continue to investigate the issue noted in your ticket and will provide a response as soon as we are able. Thank you for your continued patience.

Comment by Mathematica EC eCQM Team (Inactive) [ 02/12/19 ]

We continue to investigate the issue noted in your ticket and will provide a response as soon as we are able. Thank you for your patience.

Comment by Aniek Valentine (Inactive) [ 02/08/19 ]

rmongeau Can you please provide an update on this?

Generated at Sun Sep 21 15:32:59 UTC 2025 using Jira 10.3.9#10030009-sha1:eff8913ed2270ee44ab422c3609af4c4f36536d0.