ecqm.measure

CMS167v7 - Diabetic Retinopathy: Documentation of Presence or Absence of Macular Edema and Level of Severity of Retinopathy

Rationale:

Diabetic Retinopathy: Documentation of Presence or Absence of Macular Edema and Level of Severity of Retinopathy. Diabetic retinopathy is a leading cause of new cases of legal blindness among working-age Americans and represents a leading cause of blindness in this age group worldwide. (Klein, 2007). In 2005-2008, the estimated prevalence of diabetic retinopathy and vision-threatening diabetic retinopathy was 28.5 percent among persons with diabetes aged 40 years and older (Zhang, 2010). Approximately 1.5% of adults with diabetes had proliferative diabetic retinopathy and 2.7% had clinically significant macular edema (Zhang, 2010). Several level 1 RCT studies demonstrate the ability of timely treatment to reduce the rate and severity of vision loss from diabetes (Diabetic Retinopathy Study -- DRS, Early Treatment Diabetic Retinopathy Study -- ETDRS). Necessary examination prerequisites to applying the study results are that the presence and severity of both peripheral diabetic retinopathy and macular edema be accurately documented. In the RAND chronic disease quality project, while administrative data indicated that roughly half of the patients had an eye exam in the recommended time period, chart review data indicated that only 19% had documented evidence of a dilated examination (McGlynn, 2003). Thus, ensuring timely treatment that could prevent 95% of the blindness due to diabetes requires the performance and documentation of key examination parameters. The documented level of severity of retinopathy and the documented presence or absence of macular edema assists with the on-going plan of care for the patient with diabetic retinopathy.

Data Elements

DiabeticRetinopathyDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Diabetic Retinopathy valueset (2.16.840.1.113883.3.526.3.327)

Diagnosis: Condition/Diagnosis/Problem represents a practitioner’s identification of a patient’s disease, illness, injury, or condition. This category contains a single datatype to represent all of these concepts: Diagnosis. A practitioner determines the diagnosis by means of examination, diagnostic test results, patient history, and/or family history. Diagnoses are usually considered unfavorable, but may also represent neutral or favorable conditions that affect a patient’s plan of care (e.g., pregnancy). The QDM does not prescribe the source of diagnosis data in the EHR. Diagnoses may be found in a patient’s problem list, encounter diagnosis list, claims data, or other sources within the EHR. The preferred terminology for diagnoses is SNOMED-CT, but diagnoses may also be encoded using ICD-9/10. The Diagnosis datatype should not be used for differential diagnoses or rule-out diagnoses (neither of which are currently supported by the QDM).

DataType

Cardinality

DiabeticRetinopathyDiagnosis

0..*

LevelOfSeverityOfRetinopathyFindingsComponents

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Components: Elements included or documented as part of evaluations or test panels. Examples include: specific questions included in assesments, tests included in a laboratory test panel, observations included in a cardiac exam during a physical examination. Each assessment, diagnostic study, laboratory test, physical exam or procedure may have one or more components.

DataType

Cardinality

LevelOfSeverityOfRetinopathyFindingsComponents

0..*

OfficeVisit1Performed

Clinical Focus: This value set identifies patients who have had an office or other outpatient visit.

Data Element Scope: This value set was intended to map to the QDM data type of encounter.

Inclusion Criteria: Includes comprehensive history, evaluation, and management of a patient in an office or outpatient facility. Patient can be presenting with problems that are minor to high severity.

Exclusion Criteria: Excludes non-office visits, including telehealth services.

Subject constrained to the Office Visit1

EncounterPerformed: Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed. Timing: The Relevant Period addresses: startTime – The time the encounter began (admission time) stopTime – The time the encounter ended (discharge time). The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained. The Location Period is an attribute of the attribute facility location addresses: startTime = the time the patient arrived at the location; stopTime = the time the patient departed from the location

DataType

Cardinality

OfficeVisit1Performed

0..*

OutpatientConsultationPerformed

Clinical Focus: This value set indentifies patients who have had an outpatient interaction at an office with a member of their medical care team.

Data Element Scope: This value set was intended to map to the QDM data type of encounter.

Inclusion Criteria: Includes comprehensive history, evaluation, and management of a patient in an office or outpatient facility. Patient can be presenting with problems that are minor to high severity.

Exclusion Criteria: Excludes non-office visits, including telehealth services.

Subject constrained to the Outpatient Consultation

EncounterPerformed: Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed. Timing: The Relevant Period addresses: startTime – The time the encounter began (admission time) stopTime – The time the encounter ended (discharge time). The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained. The Location Period is an attribute of the attribute facility location addresses: startTime = the time the patient arrived at the location; stopTime = the time the patient departed from the location

DataType

Cardinality

OutpatientConsultationPerformed

0..*

NursingFacilityVisitPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Nursing Facility Visit

EncounterPerformed: Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed. Timing: The Relevant Period addresses: startTime – The time the encounter began (admission time) stopTime – The time the encounter ended (discharge time). The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained. The Location Period is an attribute of the attribute facility location addresses: startTime = the time the patient arrived at the location; stopTime = the time the patient departed from the location

DataType

Cardinality

NursingFacilityVisitPerformed

0..*

CareServicesInLongTermResidentialFacilityPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Care Services in Long-Term Residential Facility

EncounterPerformed: Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed. Timing: The Relevant Period addresses: startTime – The time the encounter began (admission time) stopTime – The time the encounter ended (discharge time). The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained. The Location Period is an attribute of the attribute facility location addresses: startTime = the time the patient arrived at the location; stopTime = the time the patient departed from the location

DataType

Cardinality

CareServicesInLongTermResidentialFacilityPerformed

0..*

OphthalmologicalServicesPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Ophthalmological Services

EncounterPerformed: Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed. Timing: The Relevant Period addresses: startTime – The time the encounter began (admission time) stopTime – The time the encounter ended (discharge time). The Author dateTime addresses when an Encounter is documented. Documentation can occur at the beginning, during, at the end or subsequent to the end of an Encounter. The Author dateTime should be used only if the Relevant Period cannot be obtained. The Location Period is an attribute of the attribute facility location addresses: startTime = the time the patient arrived at the location; stopTime = the time the patient departed from the location

DataType

Cardinality

OphthalmologicalServicesPerformed

0..*

EthnicityPatientCharacteristicEthnicity

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

ResultValue constrained to codes in the Ethnicity valueset (2.16.840.1.114222.4.11.837)

PatientCharacteristicEthnicity: Data elements that meet criteria using this datatype should document that the patient has one or more of the ethnicities indicated by the QDM category and its corresponding value set. Timing: Ethnicity does not have a specific timing. Measures using Patient Characteristic, Ethnicity should address the most recent entry in the clinical record.

DataType

Cardinality

EthnicityPatientCharacteristicEthnicity

0..*

OncAdministrativeSexPatientCharacteristicGender

Clinical Focus: Gender identity restricted to only Male and Female used in administrative situations requiring a restriction to these two categories.

Data Element Scope: Gender

Inclusion Criteria: Male and Female only.

Exclusion Criteria: Any gender identity that is not male or female.

ResultValue constrained to codes in the ONC Administrative Sex valueset (2.16.840.1.113762.1.4.1)

PatientCharacteristicGender: Data elements that meet criteria using this datatype should document that the patient's sex matches the QDM category and its corresponding value set. Timing: Birth (administrative) sex does not have a specific timing.

DataType

Cardinality

OncAdministrativeSexPatientCharacteristicGender

0..*

PayerPatientCharacteristicPayer

Clinical Focus: Categories of types of health care payor entities as defined by the US Public Health Data Consortium SOP code system

Data Element Scope: @code in CCDA r2.1 template Planned Coverage [act: identifier urn:oid:2.16.840.1.113883.10.20.22.4.129 (open)] DYNAMIC

Inclusion Criteria: All codes in the code system

Exclusion Criteria: none

ResultValue constrained to codes in the Payer valueset (2.16.840.1.114222.4.11.3591)

PatientCharacteristicPayer: Data elements that meet criteria using this datatype should document that the patient has one or more of the payers indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: startTime – The first day of insurance coverage with the referenced payer stopTime – The last day of insurance coverage with the referenced payer

DataType

Cardinality

PayerPatientCharacteristicPayer

0..*

RacePatientCharacteristicRace

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

ResultValue constrained to codes in the Race valueset (2.16.840.1.114222.4.11.836)

PatientCharacteristicRace: Data elements that meet criteria using this datatype should document the patient’s race. Timing: Race does not have a specific timing. Measures using Patient Characteristic, Race should address the most recent entry in the clinical record.

DataType

Cardinality

RacePatientCharacteristicRace

0..*