Back to top
Top
U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

CMS Measure ID: CMS142v11    Performance/Reporting Period: 2023    NQF Number: Not Applicable
Description:

Percentage of patients aged 18 years and older with a diagnosis of diabetic retinopathy who had a dilated macular or fundus exam performed with documented communication to the physician who manages the ongoing care of the patient with diabetes mellitus regarding the findings of the macular or fundus exam at least once within 12 months

Data Elements and coded QDM Attributes contained within the eCQM

+ Expand all

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for diagnoses of the level of severity of retinopathy.
Data Element Scope: This value set may use a model element related to Diagnosis or Communication.
Inclusion Criteria: Includes concepts that represent a diagnosis of mild, moderate, severe, or very severe non-proliferative and proliferative diabetic retinopathy.
Exclusion Criteria: No exclusions.

Constrained to codes in the Communication, Performed: Level of Severity of Retinopathy Findings value set (2.16.840.1.113883.3.526.3.1283)

QDM Datatype and Definition

"Communication, Performed"

Data elements that meet criteria using this datatype reference conveyance of information from one entity (e.g., person, organization, or device) to another.

The "Communication, Performed" code attribute represents the reason for the communication (i.e., the subject). The category attribute allows reference to the type, or category, of communication (e.g., notification, request). In many cases, the eCQM developer may not know the local workflow to address the type of communication; hence, it is listed as an attribute to be used as feasibility allows.

Timing:

  • sent dateTime - when the communication was sent.
  • received dateTime - when the communication was received.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Direct Reference Code

Constrained to 'Macular edema absent (situation)' SNOMEDCT code

QDM Datatype and Definition

"Communication, Performed"

Data elements that meet criteria using this datatype reference conveyance of information from one entity (e.g., person, organization, or device) to another.

The "Communication, Performed" code attribute represents the reason for the communication (i.e., the subject). The category attribute allows reference to the type, or category, of communication (e.g., notification, request). In many cases, the eCQM developer may not know the local workflow to address the type of communication; hence, it is listed as an attribute to be used as feasibility allows.

Timing:

  • sent dateTime - when the communication was sent.
  • received dateTime - when the communication was received.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for diagnoses to identify the presence of macular edema.
Data Element Scope: This value set may use a model element related to Diagnosis.
Inclusion Criteria: Includes concepts that represent a diagnosis of macular edema.
Exclusion Criteria: Excludes concepts that represent a diagnosis of non-macular edema.

Constrained to codes in the Communication, Performed: Macular Edema Findings Present value set (2.16.840.1.113883.3.526.3.1320)

QDM Datatype and Definition

"Communication, Performed"

Data elements that meet criteria using this datatype reference conveyance of information from one entity (e.g., person, organization, or device) to another.

The "Communication, Performed" code attribute represents the reason for the communication (i.e., the subject). The category attribute allows reference to the type, or category, of communication (e.g., notification, request). In many cases, the eCQM developer may not know the local workflow to address the type of communication; hence, it is listed as an attribute to be used as feasibility allows.

Timing:

  • sent dateTime - when the communication was sent.
  • received dateTime - when the communication was received.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts of a diagnosis of diabetic retinopathy.
Data Element Scope: This value set may use a model element related to Diagnosis.
Inclusion Criteria: Includes concepts that represent a diagnosis of diabetic retinopathy.
Exclusion Criteria: Excludes concepts that represent a diagnosis for 'unspecified eye.'

Constrained to codes in the Diagnosis: Diabetic Retinopathy value set (2.16.840.1.113883.3.526.3.327)

QDM Datatype and Definition

"Diagnosis"

Data elements that meet criteria using this datatype should document the Condition/Diagnosis/Problem and its corresponding value set. The onset dateTime corresponds to the implicit start dateTime of the datatype and the abatement dateTime corresponds to the implicit stop dateTime of the datatype. If the abatement dateTime is not present, then the diagnosis is considered to still be active. When this datatype is used with timing relationships, the criterion is looking for an active diagnosis for the time frame indicated by the timing relationships.

Timing: The prevalencePeriod references the time from the onset date to the abatement date.

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for a diagnostic study of a macular exam of the eye.
Data Element Scope: This value set may use a model element related to Diagnostic Study.
Inclusion Criteria: Includes concepts that represent a diagnostic study of macular exams, where laterality is specified or not.
Exclusion Criteria: No exclusions.

Constrained to codes in the Diagnostic Study, Performed: Macular Exam value set (2.16.840.1.113883.3.526.3.1251)

QDM Datatype and Definition

"Diagnostic Study, Performed"

Data elements that meet criteria using this datatype should document the completion of the diagnostic study indicated by the QDM category and its corresponding value set.

Timing:

  • relevant dateTime references the time the diagnostic study is performed if it occurs at a single point in time.
  • relevantPeriod references a start and stop time for an assessment that occurs over a time interval:
    • startTime - when the diagnostic study is initiated.
    • stopTime - when the diagnostic study is completed.
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criterion.

Examples using relevantPeriod:

  • Initiation of a treadmill stress test to the time the treadmill stress test has completed
  • Initiation of the ultrasound study until completion of the ultrasound study

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for encounters for patients living in assisted living, domiciliary care or rest homes.
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter for services provided to new and established patients living in assisted living, domiciliary care or rest home who have had an interaction with a member of their medical team.
Exclusion Criteria: Excludes concepts that represent an encounter for settings other than assisted living, domiciliary care, or rest homes.

Constrained to codes in the Encounter, Performed: Care Services in Long Term Residential Facility value set (2.16.840.1.113883.3.464.1003.101.12.1014)

QDM Datatype and Definition

"Encounter, Performed"

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.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.6 addresses that concept using the diagnosis rank=1.

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for encounters in a nursing facility.
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter specific to a nursing facility, including skilled, intermediate and long term care facilities.
Exclusion Criteria: Excludes concepts that represent an encounter other than a nursing facility visits.

Constrained to codes in the Encounter, Performed: Nursing Facility Visit value set (2.16.840.1.113883.3.464.1003.101.12.1012)

QDM Datatype and Definition

"Encounter, Performed"

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.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.6 addresses that concept using the diagnosis rank=1.

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for encounters for an outpatient visit.
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter for the comprehensive history, evaluation, and management of a patient presenting with minor to high severity problems.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Office Visit value set (2.16.840.1.113883.3.464.1003.101.12.1001)

QDM Datatype and Definition

"Encounter, Performed"

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.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.6 addresses that concept using the diagnosis rank=1.

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts of encounters for ophthalmological visits.
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter for a visit with an eye care professional.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Ophthalmological Services value set (2.16.840.1.113883.3.526.3.1285)

QDM Datatype and Definition

"Encounter, Performed"

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.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.6 addresses that concept using the diagnosis rank=1.

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for encounters for outpatient interactions with a member of the medical care team.
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter for the comprehensive history, evaluation, and management of a patient presenting with minor to high severity problems.
Exclusion Criteria: No exclusions.

Constrained to codes in the Encounter, Performed: Outpatient Consultation value set (2.16.840.1.113883.3.464.1003.101.12.1008)

QDM Datatype and Definition

"Encounter, Performed"

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.

The "Encounter, Performed" participant references the primary participant.

Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.6 addresses that concept using the diagnosis rank=1.

Timing:

  • The relevantPeriod addresses:
    • startTime - The time the encounter began (admission time).
    • stopTime - The time the encounter ended (discharge time).
  • author dateTime references the time the action was recorded.
  • Refer to the eCQM expression to determine allowable timings to meet measure criteria.

Notes:

  • negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
  • The locationPeriod is an attribute of the attribute facility location that addresses:
    • startTime - the time the patient arrived at the location. The time the encounter began (admission time).
    • stopTime - the time the patient departed from the location.
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for medical reasons for not receiving a therapy or service.
Data Element Scope: This value set may use a model element related to Negation Rationale.
Inclusion Criteria: Includes concepts that describe a medical reason for not receiving a therapy or service.
Exclusion Criteria: No exclusions.

Constrained to codes in the Negation Rationale: Medical Reason value set (2.16.840.1.113883.3.526.3.1007)

QDM Attribute and Definition

negationRationale

Indicates the reason that an action was not performed. Only QDM datatypes that represent actions (e.g., performed, recommended, communication, order, dispensed) allow the negation rationale attribute. The intent is to indicate a justification that such action did not happen as expected. This attribute specifically does not address the presence or absence of information in a clinical record (e.g., documented absence of allergies versus lack of documentation about allergies). QDM assumes a world view that absence of evidence indicates information does not exist or an action did not happen. To express such lack of evidence, an eCQM author should use the CQL expression not exists with reference to the data element rather than the QDM data model. negation rationale in QDM signifies only a reason for such absence, i.e., the reason must be present to qualify for negation rationale. The syntax in the human readable HQMF is addressed in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, Procedure, Performed not done. QDM versions starting with 5.3 use the syntax, Procedure, not Performed. Section A-5 provides examples for expressing negation rationale in CQL.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

For updated guidance and implementer feedback regarding use of the QDM negation rationale attribute see Section 6.6.

Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for patient-specific reasons for not receiving a therapy or service.
Data Element Scope: This value set may use a model element related to Negation Rationale.
Inclusion Criteria: Includes concepts that represent a patient-specific reason for not receiving a therapy or service.
Exclusion Criteria: No exclusions.

Constrained to codes in the Negation Rationale: Patient Reason value set (2.16.840.1.113883.3.526.3.1008)

QDM Attribute and Definition

negationRationale

Indicates the reason that an action was not performed. Only QDM datatypes that represent actions (e.g., performed, recommended, communication, order, dispensed) allow the negation rationale attribute. The intent is to indicate a justification that such action did not happen as expected. This attribute specifically does not address the presence or absence of information in a clinical record (e.g., documented absence of allergies versus lack of documentation about allergies). QDM assumes a world view that absence of evidence indicates information does not exist or an action did not happen. To express such lack of evidence, an eCQM author should use the CQL expression not exists with reference to the data element rather than the QDM data model. negation rationale in QDM signifies only a reason for such absence, i.e., the reason must be present to qualify for negation rationale. The syntax in the human readable HQMF is addressed in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, Procedure, Performed not done. QDM versions starting with 5.3 use the syntax, Procedure, not Performed. Section A-5 provides examples for expressing negation rationale in CQL.

Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.

For updated guidance and implementer feedback regarding use of the QDM negation rationale attribute see Section 6.6.

Value Set Description from VSAC
Clinical Focus: n/a Data Element Scope: n/a Inclusion Criteria: n/a Exclusion Criteria: n/a

Constrained to codes in the Patient Characteristic, Ethnicity: Ethnicity value set (2.16.840.1.114222.4.11.837)

QDM Datatype and Definition

"Patient Characteristic, Ethnicity"

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.

Value Set Description from VSAC
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

Constrained to codes in the Patient Characteristic, Payer: Payer value set (2.16.840.1.114222.4.11.3591)

QDM Datatype and Definition

"Patient Characteristic, Payer"

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 relevantPeriod addresses:

  • startTime – the first day of insurance coverage with the referenced payer.
  • stopTime – the last day of insurance coverage with the referenced payer.
Value Set Description from VSAC
Clinical Focus: n/a Data Element Scope: n/a Inclusion Criteria: n/a Exclusion Criteria: n/a

Constrained to codes in the Patient Characteristic, Race: Race value set (2.16.840.1.114222.4.11.836)

QDM Datatype and Definition

"Patient Characteristic, Race"

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.

Value Set Description from VSAC
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.

Constrained to codes in the Patient Characteristic, Sex: ONC Administrative Sex value set (2.16.840.1.113762.1.4.1)

QDM Datatype and Definition

"Patient Characteristic, Sex"

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.