-
Type:
Value Sets
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: Guidance
-
None
-
Vendor/Epic
-
Yes
-
In the document Clinical Quality eMeasure Logic and Implementation Guidance v1.1, section 5.5, the principal diagnosis is defined as the diagnosis that is "used for the billing transaction". It also states that this diagnosis is "typically chosen from among the diagnoses that were active during the encounter" but does not require such a linkage. It then states that "The nature of the data element will require a retrospective look back to the beginning of the diagnosis to correctly compute several of the eMeasures."
This construct appears to be fundamentally flawed. The diagnosis as assigned by the coder and which is marked as principal has no beginning or end date, it is just a diagnosis code and a principal flag. Since it has no fixed link to a clinical diagnosis which may have a beginning and end date, a software algorithm is not going to be able to establish a link between it and those dates. Therefore as defined, it cannot be used to compute e-measures that require a beginning and end date.
This definition assumes that all diagnoses recorded in the EHR, regardless of source, follow the QDM and have all specified attributes. This is a flawed assumption.