ecqm.measure

CMS132v7 - Cataracts: Complications within 30 Days Following Cataract Surgery Requiring Additional Surgical Procedures

Rationale:

Cataracts: Complications within 30 Days Following Cataract Surgery Requiring Additional Surgical Procedures. In the United States, cataracts affect more than 24 million adults over 40 years. (NEI, 2016) According to the American Academy of Ophthalmology (AAO), cataract surgery leads to favorable outcomes and improved vision. (AAO, 2016) Although uncommon, complications from cataract surgery do occur and may result in vision loss. (AAO, 2016) 1. Scientific basis for assessing short-term complications following cataract surgery. This short-term outcome of surgery indicator seeks to identify those complications from surgery that can reasonably be attributed to the surgery and surgeon and which reflect situations which - if untreated - generally result in significant avoidable vision loss that would negatively impact patient functioning. Further, it seeks to reduce surgeon burden and enhance accuracy in reporting by focusing on those significant complications that can be assessed from administrative data alone and which can be captured by the care of another physician or the provision of additional, separately coded, post-operative services. Finally, it focuses on patient safety and monitoring for events that, while hopefully uncommon, can signify important issues in the care being provided. For example, the need to reposition or exchange an intraocular lens (IOL) reflects in part 'wrong power' IOL placement, a major patient safety issue. In order to achieve these ends, the indicator excludes patients with other known, pre-operative ocular conditions that could impact the likelihood of developing a complication. Based on the results of the Cataract Appropriateness Project at RAND, other published studies, and one analysis performed on a national MCO data base, the exclusion codes would preserve over 2/3 of all cataract surgery cases for analysis. Thus, this provides a 'clean' indicator that captures care for the large majority of patients undergoing cataract surgery. 2. Evidence for gap in care. The advances in technology and surgical skills over the last 30 years have made cataract surgery much safer and more effective although complications that threaten vision do occur. For example, a study of more than 220,000 Medicare beneficiaries who underwent cataract surgery between 1994 and 2006 found that more than 1,000, or about 0.5%, of patients had at least one severe post-operative complication. These severe complications were defined as endophthalmitis (0.16%), suprachoroidal hemorrhage (0.06%), and retinal detachment (0.26%). (Stein, 2011) In a review, Taban et al. found a postoperative rate of endophthalmitis of 0.128%. (Taban, 2005) The occurrence of one of these events is associated with a significant potential for vision loss that is otherwise avoidable.

Data Elements

AcuteAndSubacuteIridocyclitisDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Acute and Subacute Iridocyclitis valueset (2.16.840.1.113883.3.526.3.1241)

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

AcuteAndSubacuteIridocyclitisDiagnosis

0..*

AdhesionsAndDisruptionsOfIrisAndCiliaryBodyDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Adhesions and Disruptions of Iris and Ciliary Body valueset (2.16.840.1.113883.3.526.3.1405)

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

AdhesionsAndDisruptionsOfIrisAndCiliaryBodyDiagnosis

0..*

AnomaliesOfPupillaryFunctionDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Anomalies of Pupillary Function valueset (2.16.840.1.113883.3.526.3.1406)

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

AnomaliesOfPupillaryFunctionDiagnosis

0..*

AphakiaAndOtherDisordersOfLensDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Aphakia and Other Disorders of Lens valueset (2.16.840.1.113883.3.526.3.1407)

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

AphakiaAndOtherDisordersOfLensDiagnosis

0..*

BurnConfinedToEyeAndAdnexaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Burn Confined to Eye and Adnexa valueset (2.16.840.1.113883.3.526.3.1409)

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

BurnConfinedToEyeAndAdnexaDiagnosis

0..*

CataractSecondaryToOcularDisordersDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cataract Secondary to Ocular Disorders valueset (2.16.840.1.113883.3.526.3.1410)

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

CataractSecondaryToOcularDisordersDiagnosis

0..*

CataractCongenitalDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cataract, Congenital valueset (2.16.840.1.113883.3.526.3.1412)

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

CataractCongenitalDiagnosis

0..*

CataractMatureOrHypermatureDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cataract, Mature or Hypermature valueset (2.16.840.1.113883.3.526.3.1413)

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

CataractMatureOrHypermatureDiagnosis

0..*

CataractPosteriorPolarDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cataract, Posterior Polar valueset (2.16.840.1.113883.3.526.3.1414)

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

CataractPosteriorPolarDiagnosis

0..*

CertainTypesOfIridocyclitisDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Certain Types of Iridocyclitis valueset (2.16.840.1.113883.3.526.3.1415)

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

CertainTypesOfIridocyclitisDiagnosis

0..*

ChronicIridocyclitisDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Chronic Iridocyclitis valueset (2.16.840.1.113883.3.526.3.1416)

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

ChronicIridocyclitisDiagnosis

0..*

CloudyCorneaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cloudy Cornea valueset (2.16.840.1.113883.3.526.3.1417)

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

CloudyCorneaDiagnosis

0..*

CornealEdemaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Corneal Edema valueset (2.16.840.1.113883.3.526.3.1418)

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

CornealEdemaDiagnosis

0..*

CornealOpacityAndOtherDisordersOfCorneaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Corneal Opacity and Other Disorders of Cornea valueset (2.16.840.1.113883.3.526.3.1419)

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

CornealOpacityAndOtherDisordersOfCorneaDiagnosis

0..*

CystsOfIrisCiliaryBodyAndAnteriorChamberDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Cysts of Iris, Ciliary Body, and Anterior Chamber valueset (2.16.840.1.113883.3.526.3.1420)

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

CystsOfIrisCiliaryBodyAndAnteriorChamberDiagnosis

0..*

EnophthalmosDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Enophthalmos valueset (2.16.840.1.113883.3.526.3.1421)

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

EnophthalmosDiagnosis

0..*

GlaucomaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Glaucoma valueset (2.16.840.1.113883.3.526.3.1423)

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

GlaucomaDiagnosis

0..*

HereditaryCornealDystrophiesDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Hereditary Corneal Dystrophies valueset (2.16.840.1.113883.3.526.3.1424)

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

HereditaryCornealDystrophiesDiagnosis

0..*

HighHyperopiaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the High Hyperopia valueset (2.16.840.1.113883.3.526.3.1425)

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

HighHyperopiaDiagnosis

0..*

HypotonyOfEyeDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Hypotony of Eye valueset (2.16.840.1.113883.3.526.3.1426)

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

HypotonyOfEyeDiagnosis

0..*

InjuryToOpticNerveAndPathwaysDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Injury to Optic Nerve and Pathways valueset (2.16.840.1.113883.3.526.3.1427)

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

InjuryToOpticNerveAndPathwaysDiagnosis

0..*

CentralCornealUlcerDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Central Corneal Ulcer valueset (2.16.840.1.113883.3.526.3.1428)

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

CentralCornealUlcerDiagnosis

0..*

OpenWoundOfEyeballDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Open Wound of Eyeball valueset (2.16.840.1.113883.3.526.3.1430)

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

OpenWoundOfEyeballDiagnosis

0..*

PathologicMyopiaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Pathologic Myopia valueset (2.16.840.1.113883.3.526.3.1432)

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

PathologicMyopiaDiagnosis

0..*

PosteriorLenticonusDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Posterior Lenticonus valueset (2.16.840.1.113883.3.526.3.1433)

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

PosteriorLenticonusDiagnosis

0..*

PseudoexfoliationSyndromeDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Pseudoexfoliation Syndrome valueset (2.16.840.1.113883.3.526.3.1435)

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

PseudoexfoliationSyndromeDiagnosis

0..*

RetrolentalFibroplasiasDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Retrolental Fibroplasias valueset (2.16.840.1.113883.3.526.3.1438)

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

RetrolentalFibroplasiasDiagnosis

0..*

TraumaticCataractDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Traumatic Cataract valueset (2.16.840.1.113883.3.526.3.1443)

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

TraumaticCataractDiagnosis

0..*

UveitisDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Uveitis valueset (2.16.840.1.113883.3.526.3.1444)

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

UveitisDiagnosis

0..*

VascularDisordersOfIrisAndCiliaryBodyDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Vascular Disorders of Iris and Ciliary Body valueset (2.16.840.1.113883.3.526.3.1445)

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

VascularDisordersOfIrisAndCiliaryBodyDiagnosis

0..*

MorgagnianCataractDiagnosis

Clinical Focus: This value set includes concepts related to 'morgagnian cataract'.

Data Element Scope: This value set includes concepts related to 'morgagnian cataract'.

Inclusion Criteria: This value set includes concepts related to 'morgagnian cataract'.

Exclusion Criteria: Concepts not related to 'morgagnian cataract.'

ResultValue constrained to codes in the Morgagnian Cataract valueset (2.16.840.1.113883.3.526.3.1558)

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

MorgagnianCataractDiagnosis

0..*

UseOfSystemicSympatheticAlpha1aAntagonistMedicationForTreatmentOfProstaticHypertrophyActive

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Use of Systemic Sympathetic alpha-1a Antagonist Medication for Treatment of Prostatic Hypertrophy

MedicationActive: Data elements that meet criteria using this datatype should document that the medication indicated by the QDM category and its corresponding value set is being taken by the patient. Keep in mind that when this datatype is used with timing relationships, the criterion is looking for a medication being taken for the time frame indicated by the timing relationships. Timing: The Relevant Period addresses: StartTime = when the medication is first known to be used (generally the time of entry on the medication list); StopTime = when the medication is discontinued (generally, the time discontinuation is recorded on the medication list)

DataType

Cardinality

UseOfSystemicSympatheticAlpha1aAntagonistMedicationForTreatmentOfProstaticHypertrophyActive

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..*

AspirationAndInjectionProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Aspiration and Injection Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

AspirationAndInjectionProceduresPerformed

0..*

ExcisionOfAdhesionsPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Excision of Adhesions

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

ExcisionOfAdhesionsPerformed

0..*

LensProcedurePerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Lens Procedure

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

LensProcedurePerformed

0..*

RemovalProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Removal Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

RemovalProceduresPerformed

0..*

RetinalRepairProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Retinal Repair Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

RetinalRepairProceduresPerformed

0..*

RevisionProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Revision Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

RevisionProceduresPerformed

0..*

ScleralProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Scleral Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

ScleralProceduresPerformed

0..*

VitreousProceduresPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Vitreous Procedures

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

VitreousProceduresPerformed

0..*

CataractSurgeryPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Cataract Surgery

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

CataractSurgeryPerformed

0..*

PriorParsPlanaVitrectomyPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Prior Pars Plana Vitrectomy

ProcedurePerformed: Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: StartTime = the time the procedure begins; StopTime = the time the procedure is completed NOTE: 1) Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request. 2) The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

DataType

Cardinality

PriorParsPlanaVitrectomyPerformed

0..*