ecqm.measure

CMS72v7 - Antithrombotic Therapy By End of Hospital Day 2 (STK-05)

Rationale:

Antithrombotic Therapy By End of Hospital Day 2 (STK-05). The effectiveness of antithrombotic agents in reducing stroke mortality, stroke-related morbidity and recurrence rates has been studied in several large clinical trials. While the use of these agents for patients with acute ischemic stroke and transient ischemic attacks continues to be the subject of study, substantial evidence is available from completed studies. Data at this time suggest that antithrombotic therapy should be administered within 2 days of symptom onset in acute ischemic stroke patients to reduce stroke mortality and morbidity as long as no contraindications exist. Anticoagulants at doses to prevent venous thromboembolism are insufficient antithrombotic therapy to prevent recurrent ischemic stroke or TIA.

Data Elements

NonElectiveInpatientEncounterPerformed

Clinical Focus: This set of values contains procedures that represent non-elective inpatient encounters.

Data Element Scope: The intent of this data element is to identify non-elective inpatient encounters. Using the Quality Data Model, this particular element will map to the 'Encounter' category.

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

Exclusion Criteria: None

Subject constrained to the Non-Elective Inpatient Encounter

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

NonElectiveInpatientEncounterPerformed

0..*

DischargedToHealthCareFacilityForHospiceCareDischargeDisposition

Clinical Focus: This set of values contains procedures used to represent the discharge of a patient to a health care facility for hospice care.

Data Element Scope: The intent of this data element is to identify the final place or setting to which the patient was discharged on the day of discharge from a particular inpatient encounter. This particular value set intends to identify patients who where discharged to a health care facility for hospice care. Using the Quality Data Model, this particular value set is used with the Attribute of 'Discharge status' used with the 'Encounter' category.

Inclusion Criteria: Only SNOMED CT codes representing health care facilities for hospice care should be included.

Exclusion Criteria: None

DischargeDisposition: The disposition, or location to which the patient is transferred at the time of hospital discharge.

DataType

Cardinality

DischargedToHealthCareFacilityForHospiceCareDischargeDisposition

0..*

DischargedToHomeForHospiceCareDischargeDisposition

Clinical Focus: This set of values contains procedures used to represent the discharge of a patient to home for hospice care.

Data Element Scope: The intent of this data element is to identify the final place or setting to which the patient was discharged on the day of discharge from a particular inpatient encounter. This particular value set intends to identify patients who where discharged to home for hospice care. Using the Quality Data Model, this particular value set is used with the Attribute of 'Discharge status' used with the 'Encounter' category.

Inclusion Criteria: Only SNOMED CT codes representing discharge to home for hospice care should be included.

Exclusion Criteria: None

DischargeDisposition: The disposition, or location to which the patient is transferred at the time of hospital discharge.

DataType

Cardinality

DischargedToHomeForHospiceCareDischargeDisposition

0..*

LeftAgainstMedicalAdviceDischargeDisposition

Clinical Focus: This set of values represents a patient leaving against medical advice.

Data Element Scope: The intent of this data element is to identify the final place or setting to which the patient was discharged on the day of discharge from a particular inpatient encounter. This particular value set intends to identify patients who left against medical advice. Using the Quality Data Model, this particular value set is used with the Attribute of 'Discharge status' used with the 'Encounter' category.

Inclusion Criteria: Only SNOMED CT codes representing leaving against medical advice should be included.

Exclusion Criteria: None

DischargeDisposition: The disposition, or location to which the patient is transferred at the time of hospital discharge.

DataType

Cardinality

LeftAgainstMedicalAdviceDischargeDisposition

0..*

HemorrhagicStrokePrincipalDiagnosis

Clinical Focus: This grouping of value sets identifies patients who have had a hemorrhagic stroke, or stroke caused by hemorrhage.

Data Element Scope: The intent of this data element is to identify patients who have a diagnosis of hemorrhagic stroke, or stroke caused by a hemorrhage. Using the Quality Data Model, this particular element would map to the Principal Diagnosis attribute for the Encounter category.

Inclusion Criteria: Only use codes which represent a diagnosis of hemorrhagic stroke, or stroke caused by hemorrhage. This is a grouping of ICD10CM and SNOMED-CT codes.

Exclusion Criteria: None.

PrincipalDiagnosis: The coded diagnosis/problem established after study to be chiefly responsible for occasioning the admission of the patient to the hospital for care.

DataType

Cardinality

HemorrhagicStrokePrincipalDiagnosis

0..*

IschemicStrokePrincipalDiagnosis

Clinical Focus: This grouping of value sets identifies patients who have had a stroke caused by ischemia, where the blood supply is restricted to an area of the brain by something like thrombosis or an embolism.

Data Element Scope: The intent of this data element is to identify patients who have a diagnosis of ischemic stroke, or stroke caused by ischemia. Using the Quality Data Model, this particular element would map to the Principal Diagnosis attribute for the Encounter category or to the Diagnosis Category.

Inclusion Criteria: Only use codes which represent a diagnosis of ischemic stroke, or stroke caused by ischemia. This is a grouping of ICD10CM and SNOMED-CT codes and concepts.

Exclusion Criteria: None.

PrincipalDiagnosis: The coded diagnosis/problem established after study to be chiefly responsible for occasioning the admission of the patient to the hospital for care.

DataType

Cardinality

IschemicStrokePrincipalDiagnosis

0..*

EmergencyDepartmentVisitPerformed

Clinical Focus: This set of values identifies procedures representing an emergency department encounter.

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

Inclusion Criteria: Include codes representing an emergency department visit encounter utilizing the SNOMED CT code system.

Exclusion Criteria: None

Subject constrained to the Emergency Department Visit

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

DataType

Cardinality

EmergencyDepartmentVisitPerformed

0..*

ComfortMeasuresOrder

Clinical Focus: This set of values contains care regimes used to define comfort measure care.

Data Element Scope: The intent of this data element is to identify patients receiving comfort measures care. Using the Quality Data Model, this particular element would map to the Intervention category.

Inclusion Criteria: Include SNOMEDCT regime and therapy codes for comfort measures, terminal care, dying care, and hospice care.

Exclusion Criteria: None.

Subject constrained to the Comfort Measures

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

ComfortMeasuresOrder

0..*

ComfortMeasuresPerformed

Clinical Focus: This set of values contains care regimes used to define comfort measure care.

Data Element Scope: The intent of this data element is to identify patients receiving comfort measures care. Using the Quality Data Model, this particular element would map to the Intervention category.

Inclusion Criteria: Include SNOMEDCT regime and therapy codes for comfort measures, terminal care, dying care, and hospice care.

Exclusion Criteria: None.

Subject constrained to the Comfort Measures

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

ComfortMeasuresPerformed

0..*

AntithromboticTherapyAdministered

Clinical Focus: This set of values contains anticoagulant and antiplatelet drugs used to reduce stroke mortality and morbidity.

Data Element Scope: The intent of this data element is to identify patients who receive antithombotic therapy following stroke. Using the Quality Data Model, this particular element would map to the Medication category.

Inclusion Criteria: Include single and multi-ingredient drugs. Oral, rectal, and injectable dose forms should be included. Antithrombotic medications include anticoagulants and antiplatelet drugs.

Exclusion Criteria: Exclude enoxaparin and heparin codes generally given for VTE prophylaxis.

Subject constrained to the Antithrombotic Therapy

MedicationAdministered: Data elements that meet criteria using this datatype should document that the medication indicated by the QDM category and its corresponding value set was actually administered to the patient. Timing: The Relevant Period addresses: startTime = when a single medication administration event starts (e.g., the initiation of an intravenous infusion, or administering a pill or IM injection to a patient); stopTime = when a single medication administration event ends (e.g., the end time of the intravenous infusion, or the administration of a pill or IM injection is completed - for pills and IM injections, the start and stop times are the same) NOTE – Measure developers should address multiple administrations over a period of time using CQL logic. Refer to Special Cases in Appendix A (Section A.3) for scenarios to consider in calculating cumulative medication duration.

DataType

Cardinality

AntithromboticTherapyAdministered

0..*

AntithromboticTherapyOrder

Clinical Focus: This set of values contains anticoagulant and antiplatelet drugs used to reduce stroke mortality and morbidity.

Data Element Scope: The intent of this data element is to identify patients who receive antithombotic therapy following stroke. Using the Quality Data Model, this particular element would map to the Medication category.

Inclusion Criteria: Include single and multi-ingredient drugs. Oral, rectal, and injectable dose forms should be included. Antithrombotic medications include anticoagulants and antiplatelet drugs.

Exclusion Criteria: Exclude enoxaparin and heparin codes generally given for VTE prophylaxis.

Subject constrained to the Antithrombotic Therapy

MedicationOrder: Data elements that meet criteria using this datatype should document a request to a pharmacy to provide the medication indicated by the QDM category and its corresponding value set. Timing: The Author dateTime is the time the order is signed. Timing: The Relevant Period addresses: startTime = when the first administration of the medication is expected. The first administration may be expected at the time of the order or at a specified future date (i.e., the active time for the order); such information should be identified in the medication order. If the startTime is not specified in the order, the startTime defaults to the Author dateTime (the time the order is signed). stopTime = when the medication supply provided by the medication order is expected to be completed, including all fulfillments covered by the number of refills. Note that when calculating cumulative medication duration, the stopTime may be present directly in the medication order. If the stopTime is not available, the duration in days is the difference between the Relevant Period start and stop times multiplied by (1 + the number of refills). Refer to Special Cases in Appendix A (Section A.3) for scenarios to consider in calculating cumulative medication duration.

DataType

Cardinality

AntithromboticTherapyOrder

0..*

ThrombolyticTPaTherapyAdministered

Clinical Focus: This set of values contains medications that are prescribed for Thrombolytic (t-PA) Therapy for treatment of ischemic stroke.

Data Element Scope: The intent of this data element is to identify patients who are administered appropriate Thrombolytic (t-PA) Therapy for stroke. Using the Quality Data Model, this particular element would map to the 'Medication' category.

Inclusion Criteria: Include RxNorm thombolytic medications appropriate for stroke treatment consistent with administration by IV route.

Exclusion Criteria: None.

Subject constrained to the Thrombolytic (t-PA) Therapy

MedicationAdministered: Data elements that meet criteria using this datatype should document that the medication indicated by the QDM category and its corresponding value set was actually administered to the patient. Timing: The Relevant Period addresses: startTime = when a single medication administration event starts (e.g., the initiation of an intravenous infusion, or administering a pill or IM injection to a patient); stopTime = when a single medication administration event ends (e.g., the end time of the intravenous infusion, or the administration of a pill or IM injection is completed - for pills and IM injections, the start and stop times are the same) NOTE – Measure developers should address multiple administrations over a period of time using CQL logic. Refer to Special Cases in Appendix A (Section A.3) for scenarios to consider in calculating cumulative medication duration.

DataType

Cardinality

ThrombolyticTPaTherapyAdministered

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

IntravenousOrIntraArterialThrombolyticTPaTherapyPerformed

Clinical Focus: This grouping value set contain procedures that represent intravenous or intra-arterial thrombolytic (t-PA) therapy.

Data Element Scope: The intent of this data element is to identify intravenous or intra-arterial thrombolytic (t-PA) therapy procedures. Using the Quality Data Model, this particular element will map to the 'Procedure' category.

Inclusion Criteria: Include codes that identify intravenous or intra-arterial thrombolytic (t-PA) therapy procedures.

Exclusion Criteria: None

Subject constrained to the Intravenous or Intra-arterial Thrombolytic (t-PA) Therapy

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

IntravenousOrIntraArterialThrombolyticTPaTherapyPerformed

0..*