ecqm.unions

Active Behavioral Health Medicationsor Diagnosis Union

Description:

Based On: Union2

Used By:

• CMS169v7

QDM Attributes

BhAntidepressantMedicationActive

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

Subject constrained to the BH Antidepressant Medication

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

BhAntidepressantMedicationActive

0..*

BhAntidepressantMedicationOrder

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

Subject constrained to the BH Antidepressant Medication

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

BhAntidepressantMedicationOrder

0..*

BhMoodStabilizerMedicationActive

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

Subject constrained to the BH Mood Stabilizer Medication

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

BhMoodStabilizerMedicationActive

0..*

BhMoodStabilizerMedicationOrder

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

Subject constrained to the BH Mood Stabilizer Medication

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

BhMoodStabilizerMedicationOrder

0..*

BhConditionInvolvingBipolarDisorderDiagnosis

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

ResultValue constrained to codes in the BH Condition Involving Bipolar Disorder valueset (2.16.840.1.113883.3.1257.1.1504)

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

BhConditionInvolvingBipolarDisorderDiagnosis

0..*

BhConditionInvolvingUnipolarDepressionDiagnosis

Clinical Focus: Under development

Data Element Scope: Under development

Inclusion Criteria: Under development

Exclusion Criteria: Under development

ResultValue constrained to codes in the BH Condition Involving Unipolar Depression valueset (2.16.840.1.113883.3.1257.1.1505)

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

BhConditionInvolvingUnipolarDepressionDiagnosis

0..*