ecqm.dataelement

Dexa Dual Energy Xray Absorptiometry Bone Density For Urology Care Performed

Description:

Clinical Focus: Xray studies to determine bone density.

Data Element Scope: The intent of this data element is to identify patients with low bone mineral density

Inclusion Criteria: 1 or more axial sites, axial skeleton (hips, pelvis, spine) or 1 or more appendicular skeleton sites (radius, wrist, heel)

Exclusion Criteria: Study other than DEXA

Subject constrained to the DEXA Dual Energy Xray Absorptiometry, Bone Density for Urology Care

QDM Datatype: DiagnosticStudyPerformed

Data elements that meet criteria using this datatype should document the completion of the diagnostic study indicated by the QDM category and its corresponding value set. Timing: The Relevant Period addresses: startTime – when the diagnostic study is initiated stopTime – when the diagnostic study is completed Examples: 1) Initiation of a treadmill stress test to the time the treadmill stress test has completed. 2) Initiation of the ultrasound study until completion of the ultrasound study

Used By:

• CMS645v2

Included in Unions:

• BoneDensityScanOrderedorPerformedUnion,
• NoBoneDensityScanOrderedDuetoPatientRefusalUnion

QDM Attributes

Subject.Statement

Defined in Activity

DataType

Constrained in DexaDualEnergyXrayAbsorptiometryBoneDensityForUrologyCarePerformed

DexaDualEnergyXrayAbsorptiometryBoneDensityForUrologyCare

AuthorDatetime

The time the data element was entered into the clinical software. Note, some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.

RelevantPeriod

Relevant Period addresses the time between the start of an action to the end of an action. Each datatype using relevant period defines specific definitions for the start and stop time for the action listed.

NegationRationale

Indicates the reason that an action was not performed. Only QDM datatypes that represent actions (e.g., performed, recommended, communication, order, dispensed) allow the “negation rationale” attribute. The intent is to indicate a justification that such action did not happen as expected. This attribute specifically does not address the presence or absence of information in a clinical record (e.g., documented absence of allergies Vs lack of documentation about allergies). The syntax in the human readable HQMF is address in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, “Procedure, Performed not done.” QDM 5.0 DRAFT uses the syntax, “Procedure, not Performed.” Note: Some datatypes include both Relevant Time and Author dateTime attributes. The purpose is to accommodate Author dateTime if the actual start and stop times are not available when evaluating for feasibility, and also to allow specification of a time for Negation Rationale.