ecqm.unions

Historyof Uterine Surgery Diagnosis Union

Description:

Based On: Union53

Used By:

• CMS113v7

QDM Attributes

CornualEctopicPregnancyDiagnosis

Clinical Focus: This set of values contains diagnosis that represent a cornual ectopic pregnancy

Data Element Scope: The intent of this data element is to identify a cornual ectopic pregnancy.

Inclusion Criteria: Includes codes representing cornual ectopic pregancy

Exclusion Criteria: Excludes codes representing ectopic pregnancies other than cornual ectopic pregnancies, such as tubal ectopic pregnancies.

ResultValue constrained to codes in the Cornual Ectopic Pregnancy valueset (2.16.840.1.113762.1.4.1110.12)

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

CornualEctopicPregnancyDiagnosis

0..*

PerforationOfUterusDiagnosis

Clinical Focus: This set of values contains diagnoses that represent perforation of the uterus.

Data Element Scope: The intent of this data element is to identify perforation of the uterus.

Inclusion Criteria: Includes codes that identify perforation of the uterus.

Exclusion Criteria: Excludes codes indentifying perforation to body structures other than the uterus.

ResultValue constrained to codes in the Perforation of Uterus valueset (2.16.840.1.113762.1.4.1110.14)

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

PerforationOfUterusDiagnosis

0..*

UterineRuptureDiagnosis

Clinical Focus: This set of values contains diagnoses that represent a uterine rupture

Data Element Scope: The intent of this data element is to identify a uterine rupture.

Inclusion Criteria: Include codes that identify a uterine rupture.

Exclusion Criteria: None

ResultValue constrained to codes in the Uterine Rupture valueset (2.16.840.1.113762.1.4.1110.16)

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

UterineRuptureDiagnosis

0..*

UterineWindowDiagnosis

Clinical Focus: This set of values contains diagnoses that represent a uterine window.

Data Element Scope: The intent of this data element is to identify a uterine window. Using the Quality Data Model, this particular element will map to the 'Diagnosis' category.

Inclusion Criteria: Include SNOMED CT codes that identify a uterine window.

Exclusion Criteria: None

ResultValue constrained to codes in the Uterine Window valueset (2.16.840.1.113883.3.117.1.7.1.137)

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

UterineWindowDiagnosis

0..*