ecqm.unions

Age Dependent Combination Risk Factors Union

Description:

Based On: Union4

Used By:

• CMS249v1

QDM Attributes

RheumatoidArthritisDiagnosis

Clinical Focus: This set of values contains diagnosis codes that are used to identify patients with Rheumatoid arthritis.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Includes rheumatoid arthritis and felty's syndrome. Includes comorbidities occuring with rheumatoid arthritis, such as rheumatoid polyneuropathy, rheumatoid myopathy, rheumatoid heart disease, rheumatoid vasculitis, and rheumatoid lung disease.

Exclusion Criteria: Exclude codes for Juvenile chronic polyarthritis, Chronic postrheumatic arthropathy, or inflammatory polyarhtropathy.

ResultValue constrained to codes in the Rheumatoid Arthritis valueset (2.16.840.1.113883.3.464.1003.113.12.1005)

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

RheumatoidArthritisDiagnosis

0..*

HyperthyroidismDiagnosis

Clinical Focus: This set of values contains codes that identify patients with a diagnosis of Hyperthyroidism.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Includes diagnosis codes for thyrotoxicosis, both with and without thyrotoxic crisis or storm, and with and without presence of goiter.

Exclusion Criteria: Excludes diagnosis codes for neonatal thyrotoxicosis.

ResultValue constrained to codes in the Hyperthyroidism valueset (2.16.840.1.113883.3.464.1003.117.12.1015)

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

HyperthyroidismDiagnosis

0..*

MalabsorptionSyndromesDiagnosis

Clinical Focus: This set of values contains codes that are used to identify patients with a diagnosis of chronic intestinal malabsorption.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Includes regional enteritis, ulcerative enterocolitis, celiac disease, tropical sprue, blind loop syndrome, Pancreatic steatorrhea, and other specified or unspecified intestinal malabsorption disorders.

Exclusion Criteria: Excludes diagnoses of specified disorders of the intestine, including fistula of intesting, ulceration of intesting, performation of intestine, angiodysplasia (with or without hemmorrhage

ResultValue constrained to codes in the Malabsorption Syndromes valueset (2.16.840.1.113883.3.464.1003.199.12.1050)

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

MalabsorptionSyndromesDiagnosis

0..*

ChronicLiverDiseaseDiagnosis

Clinical Focus: This set of values contains codes that identify patients with a diagnosis of chronic liver disease.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Include all diagnosis codes associated with chronic liver disease that are not substance-induced.

Exclusion Criteria: N/A

ResultValue constrained to codes in the Chronic Liver Disease valueset (2.16.840.1.113883.3.464.1003.199.12.1035)

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

ChronicLiverDiseaseDiagnosis

0..*

ChronicMalnutritionDiagnosis

Clinical Focus: This set of values contains codes that identify patients with a diagnosis of chronic malnutrition.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Include all diagnosis codes for specified and unspecified eating disorders.

Exclusion Criteria: Exclude all diagnosis codes for feeding disorders of infancy or childhood. These include feeding disturbances, developmental delays, loss of appetite, & rumination. Also avoide restrictive food intake disorders, and pica.

ResultValue constrained to codes in the Chronic Malnutrition valueset (2.16.840.1.113883.3.464.1003.199.12.1036)

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

ChronicMalnutritionDiagnosis

0..*

OsteopeniaDiagnosis

Clinical Focus: This value set identifies patients with a diagnosis of osteopenia.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Includes diagnosis codes for specified and unspecified disorder of bones and cartilage. Includes osteopenia of prematurity, drug-induced osteopenia, and senile osteopenia.

Exclusion Criteria: Excludes diagnosis of arrest of bone development or growth, chondromalacia, or stress fracture of bone.

ResultValue constrained to codes in the Osteopenia valueset (2.16.840.1.113883.3.464.1003.113.12.1049)

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

OsteopeniaDiagnosis

0..*

OsteoporoticFracturesDiagnosis

Clinical Focus: This set of values contains codes that are used to identify patients with a diagnosis of pathological fracture with or without occurrence of osteoporosis.

Data Element Scope: This value set is developed for the diagnosis QDM datatype. It can potentially be used for other datatypes as well.

Inclusion Criteria: Include all diagnosis codes associated with pathological fracture, with or without reference to osteoporosis.

Exclusion Criteria: Exclude all diagnosis codes for fractures that are not pathological.

ResultValue constrained to codes in the Osteoporotic Fractures valueset (2.16.840.1.113883.3.464.1003.113.12.1050)

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

OsteoporoticFracturesDiagnosis

0..*

HistoryOfHipFractureInParentPerformed

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

Subject constrained to the History of hip fracture in parent

AssessmentPerformed: Data elements that meet criteria using this datatype should document completion of the assessment indicated by the QDM category and its corresponding value set. Timing: The time the assessment is completed; Author dateTime.

DataType

Cardinality

HistoryOfHipFractureInParentPerformed

0..*

WhitePatientCharacteristicRace

Clinical Focus:

Data Element Scope:

Inclusion Criteria:

Exclusion Criteria:

ResultValue constrained to codes in the White valueset (2.16.840.1.113883.3.464.1003.123.12.1007)

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

WhitePatientCharacteristicRace

0..*