ecqm.measure

CMS134v7 - Diabetes: Medical Attention for Nephropathy

Rationale:

Diabetes: Medical Attention for Nephropathy. As the seventh leading cause of death in the U.S., diabetes kills approximately 79,500 people a year (CDC Health 2017). Diabetes is a long lasting disease marked by high blood glucose levels, resulting from the body's inability to produce or use insulin properly (CDC About Diabetes 2017). People with diabetes are at increased risk of serious health complications including vision loss, heart disease, stroke, kidney failure, amputation of toes, feet or legs, and premature death. (CDC At a Glance 2016). In 2012, diabetes cost the U.S. an estimated $245 billion: $176 billion in direct medical costs and $69 billion in reduced productivity. This is a 41 percent increase from the estimated $174 billion spent on diabetes in 2007 (ADA Economic 2013). High blood sugar levels in patients with diabetes put them at a higher risk of damaging their kidneys and causing chronic kidney disease, which can lead to kidney failure (CDC Fact Sheet 2017, CDC At a Glance 2016). During 2011-2012 there were 36.5% new cases of chronic kidney disease (stages 1-4) among 297,000 diabetic patients 20 years and older (Murphy 2016). In 2014, diabetes accounted for 44% of 118,000 new cases of end stage renal disease (USRDS 2016).

Data Elements

DiabetesDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Diabetes valueset (2.16.840.1.113883.3.464.1003.103.12.1001)

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

DiabetesDiagnosis

0..*

DiabeticNephropathyDiagnosis

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

ResultValue constrained to codes in the Diabetic Nephropathy valueset (2.16.840.1.113883.3.464.1003.109.12.1004)

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

DiabeticNephropathyDiagnosis

0..*

HypertensiveChronicKidneyDiseaseDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Hypertensive Chronic Kidney Disease valueset (2.16.840.1.113883.3.464.1003.109.12.1017)

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

HypertensiveChronicKidneyDiseaseDiagnosis

0..*

GlomerulonephritisAndNephroticSyndromeDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Glomerulonephritis and Nephrotic Syndrome valueset (2.16.840.1.113883.3.464.1003.109.12.1018)

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

GlomerulonephritisAndNephroticSyndromeDiagnosis

0..*

KidneyFailureDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Kidney Failure valueset (2.16.840.1.113883.3.464.1003.109.12.1028)

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

KidneyFailureDiagnosis

0..*

ProteinuriaDiagnosis

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

ResultValue constrained to codes in the Proteinuria valueset (2.16.840.1.113883.3.526.3.1003)

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

ProteinuriaDiagnosis

0..*

EncounterInpatientPerformed

Clinical Focus: This set of values identify the most common inpatient encounter types.

Data Element Scope: The intent of this data element is to identify patients who have had an inpatient encounter. Using the Quality Data Model, this particular element will map to the 'encounter' category.

Inclusion Criteria: Only SNOMED CT codes representing inpatient encounter should be included.

Exclusion Criteria: None.

Subject constrained to the Encounter Inpatient

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

EncounterInpatientPerformed

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

HomeHealthcareServicesPerformed

Clinical Focus: This value set identifies patients who have had a home health visit by a provider for the evaluation or management of a new or existing patient.

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

Inclusion Criteria: Include all home visits for the evaluation and management of a new or established patient.

Exclusion Criteria: None

Subject constrained to the Home Healthcare 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

HomeHealthcareServicesPerformed

0..*

PreventiveCareServicesInitialOfficeVisit18AndUp1Performed

Clinical Focus: This value set identifies patients over the age of 18 who have had an initial preventive care office visit.

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

Inclusion Criteria: Includes comprehensive preventive medicine reevaluation and management of an individual over the age of 18.

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

Subject constrained to the Preventive Care Services-Initial Office Visit, 18 and Up1

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

PreventiveCareServicesInitialOfficeVisit18AndUp1Performed

0..*

PreventiveCareServicesEstablishedOfficeVisit18AndUp1Performed

Clinical Focus: This value set identifies patients over the age of 18 who have had an established preventive care office visit.

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

Inclusion Criteria: Includes comprehensive preventive medicine reevaluation and management of an individual over the age of 18.

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

Subject constrained to the Preventive Care Services - Established Office Visit, 18 and Up1

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

PreventiveCareServicesEstablishedOfficeVisit18AndUp1Performed

0..*

EsrdMonthlyOutpatientServicesPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the ESRD Monthly Outpatient 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

EsrdMonthlyOutpatientServicesPerformed

0..*

AnnualWellnessVisit1Performed

Clinical Focus: This value set contains concepts related to annual wellness visits.

Data Element Scope: The intent of this data element is to identify patients who have had an annual wellness visit. Using the Quality Data Model, this particular data element would be classified under the 'Encounter' category.

Inclusion Criteria: Includes encounters specific to annual wellness visits.

Exclusion Criteria: None

Subject constrained to the Annual Wellness 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

AnnualWellnessVisit1Performed

0..*

HospiceCareAmbulatoryOrder

Clinical Focus: Patients receiving hospice care outside of hospital or long term care facility.

Data Element Scope: The intent of this value set is to identify all patients receiving hospice care outside of hospital or long term care facility . Using the quality data model this maps to 'Intervention, Order' and 'Procedure, Order'.

Inclusion Criteria: All hospice care concepts should be included.

Exclusion Criteria: Do not include concepts for palliative care or comfort measures.

Subject constrained to the Hospice care ambulatory

InterventionOrder: Data elements that meet criteria using this datatype should document a request to perform the intervention indicated by the QDM category and its corresponding value set. Timing: The time the order is signed; Author dateTime

DataType

Cardinality

HospiceCareAmbulatoryOrder

0..*

HospiceCareAmbulatoryPerformed

Clinical Focus: Patients receiving hospice care outside of hospital or long term care facility.

Data Element Scope: The intent of this value set is to identify all patients receiving hospice care outside of hospital or long term care facility . Using the quality data model this maps to 'Intervention, Order' and 'Procedure, Order'.

Inclusion Criteria: All hospice care concepts should be included.

Exclusion Criteria: Do not include concepts for palliative care or comfort measures.

Subject constrained to the Hospice care ambulatory

InterventionPerformed: Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: startTime – The time the intervention begins stopTime – The time the intervention ends NOTE - timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.

DataType

Cardinality

HospiceCareAmbulatoryPerformed

0..*

OtherServicesRelatedToDialysisPerformed

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

Subject constrained to the Other Services Related to Dialysis

InterventionPerformed: Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: startTime – The time the intervention begins stopTime – The time the intervention ends NOTE - timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.

DataType

Cardinality

OtherServicesRelatedToDialysisPerformed

0..*

DialysisEducationPerformed

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

Subject constrained to the Dialysis Education

InterventionPerformed: Data elements that meet criteria using this datatype should document the completion of the intervention indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: startTime – The time the intervention begins stopTime – The time the intervention ends NOTE - timing refers to a single instance of an intervention. If a measure seeks to evaluate multiple interventions over a period of time, the measure developer should use CQL logic to represent the query request.

DataType

Cardinality

DialysisEducationPerformed

0..*

UrineProteinTestsPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Urine Protein Tests

LaboratoryTestPerformed: Data elements that meet criteria using this datatype should document the laboratory test indicated by the QDM category and its corresponding value set was performed. Timing: The Relevant Period addresses: startTime – When the laboratory test is initiated (i.e., the time the specimen collection begins). stopTime – when the laboratory test is completed (i.e., the time the specimen collection ends). Examples: 1) Initiation of a venipuncture for a fasting blood glucose to the time venipuncture for the fasting blood glucose is completed – basically a single point in time for many specimen collections. 2) Initiation of a 24-hour urine collection for measured creatinine clearance until completion of the 24-hour urine collection Note – the time that the result report is available is a separate attribute than the time of the study (specimen collection)

DataType

Cardinality

UrineProteinTestsPerformed

0..*

AceInhibitorOrArbActive

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the ACE Inhibitor or ARB

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

AceInhibitorOrArbActive

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

VascularAccessForDialysisPerformed

Clinical Focus: Under Development

Data Element Scope: Under Development

Inclusion Criteria: Under Development

Exclusion Criteria: Under Development

Subject constrained to the Vascular Access for Dialysis

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

VascularAccessForDialysisPerformed

0..*

KidneyTransplantPerformed

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

Subject constrained to the Kidney Transplant

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

KidneyTransplantPerformed

0..*

DialysisServicesPerformed

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

Subject constrained to the Dialysis Services

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

DialysisServicesPerformed

0..*