["Diagnostic Study, Order": "DEXA Dual Energy Xray Absorptiometry, Bone Density for Urology Care"]
Data Element Scope: This value set may use a model element related to Diagnostic Study.
Inclusion Criteria: Includes concepts that represent a diagnostic study of a dual-energy X-ray absorptiometry (DXA, DEXA) with 1 or more axial sites, axial skeleton (hips, pelvis, spine) or 1 or more appendicular skeleton sites (radius, wrist, heel).
Exclusion Criteria: No Exclusions.
Constrained to codes in the Diagnostic Study, Order: DEXA Dual Energy Xray Absorptiometry, Bone Density for Urology Care value set (2.16.840.1.113762.1.4.1151.38)
"Diagnostic Study, Order"
Data elements that meet criteria using this datatype should document a request by a clinician or appropriately licensed care provider to an appropriate provider or organization to perform the diagnostic study indicated by the QDM category and its corresponding value set. The request may be in the form of a consultation or a direct order to the organization that performs the diagnostic study. Diagnostic studies are those that are not performed in the clinical laboratory. Such studies include, but are not limited to, imaging studies, cardiology studies (electrocardiogram, treadmill stress testing), pulmonary function testing, and vascular laboratory testing.
Timing: The time the order is signed; author dateTime.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
authorDateTime
The time the data element was entered into the clinical software. Note, some datatypes include both relevant dateTime and author dateTime attributes. When both are present, author dateTime is included to accommodate negation rationale.
The author dateTime addresses when an activity is documented. Documentation can occur at the beginning, during, at the end, or subsequent to the end of the activity. The author dateTime should be used only if the relevantPeriod cannot be obtained or to represent the time negation rationale is documented.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
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 versus lack of documentation about allergies). QDM assumes a world view that absence of evidence indicates information does not exist or an action did not happen. To express such lack of evidence, an eCQM author should use the CQL expression not exists with reference to the data element rather than the QDM data model. negation rationale in QDM signifies only a reason for such absence, i.e., the reason must be present to qualify for negation rationale. The syntax in the human readable HQMF is addressed in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, "Procedure, Performed not done." QDM versions starting with 5.3 use the syntax, "Procedure, not Performed." Section A-5 provides examples for expressing negation rationale in CQL.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.