ecqm.unions

Nephropathy Diagnoses Union

Description:

Based On: Union85

Used By:

• CMS134v7

QDM Attributes

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

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

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

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