Table 5:
Measurement Process Summary for Some Measures
| Measure | Measurement Process Summary | MeasurementResult | ||||
|---|---|---|---|---|---|---|
| Systolic | Diastolic | BloodPressure Observation | Encounter | Patient | ||
| Measures that involve only the Representation | ||||||
| RepresentationConsistency | Satisfied if all Representations conform to their DataValueTypes. Patient2. Encounter.Blood PressureObservation.Diastolic is an invalid value. | 4/4 1.0 |
2/3 .67 |
3/4 .75 |
4/5 .80 |
4/5 .80 |
| RepresentationComplete | Patient3.Encounter.BloodPressureObservation.Diastolic has a missing value so it is not RepresentationComplete. | 4/4 1.0 |
2/3 .67 |
3/4 .75 |
4/5 .80 |
4/5 .80 |
| Measures that involve the Representation and Domain | ||||||
| DomainConsistency |
DomainConsistency is satisfied if all of the concepts in the Domain exist in the data (true for this example). Also, the data must have RepresentationConsistency (Patient2 does not) and all of the constraints for all of the Domain concepts must be satisfied. Patient4 has a diastolic blood pressure value that is higher than the systolic value, so the constraint is not satisfied. But Patient5’s missing BloodPressureObservation is allowed by the Domain. |
3/4 .75 |
1/3 .33 |
1/4 .25 |
2/5 .40 |
2/5 .40 |
| CodingConsistency | True if all coded text Representations have valid values. Patient4.Encounter.Diagnosis is invalid in the ICD9 terminology. |
4/5 .80 |
4/5 .80 |
|||
| DomainMetadata | The Domain ontology is defined and contains no logical inconsistencies. It would be considered inconsistent if it contained another rule that stated patient age was optional (i.e. “Patient has [0 or 1] Age”). | 4/4 1.0 |
3/3 1.0 |
4/4 1.0 |
5/5 1.0 |
5/5 1.0 |
| DomainComplete | Even though Patient5.Encounter.BloodPressureObservation.Diastolic is missing, the Domain ontology indicates that it is optional, so the constraint is satisfied. | 4/4 1.0 |
4/4 1.0 |
4/4 1.0 |
5/5 1.0 |
5/5 1.0 |
| DomainCoverage | Satisfied since all of the Domain concepts are represented in the data. | 4/4 1.0 |
3/3 1.0 |
4/4 1.0 |
5/5 1.0 |
5/5 1.0 |
| Measures that involve the Representation, Domain and Task | ||||||
| Sufficiency | The Task specifies a SufficiencyContraint that requires at least 1 BloodPressureObservation must exist during the assessment period. Patient5 and Patient3 don’t have valid blood pressure observations recorded. |
3/5 .60 |
3/5 .60 |
|||
| TaskCoverage | TaskCoverage is satisfied if the Task concepts are a subset of the concepts represented in the Dataset. In this case, only the data at the Patient level has all of the Task concepts represented. Therefore, the eMeasure can only be calculated when all the data from the Patient level and below is available. | 0/4 0.0 |
0/3 0.0 |
0/4 0.0 |
0/5 0.0 |
5/5 1.0 |