["Device, Applied": "Frailty Device"]
Data Element Scope: This value set may use a model element related to Device.
Inclusion Criteria: Includes concepts that represent durable medical equipment (DME) or devices for frailty.
Exclusion Criteria: No exclusions.
Constrained to codes in the Device, Applied: Frailty Device value set (2.16.840.1.113883.3.464.1003.118.12.1300)
"Device, Applied"
Data elements that meet criteria using this datatype should document that the device indicated by the QDM category and its corresponding value set is in use, or impacts or alters the treatment, care plan, or encounter (e.g., an antithrombotic device has been placed on the patient's legs to prevent thromboembolism or a cardiac pacemaker is in place).
Timing:
- relevantPeriod addresses:
- startTime - when the device is inserted or first used.
- stopTime - when the device is removed or last used.
- relevantPeriod references a start and stop time for a device if the application occurred over a time interval.
- relevant dateTime addresses the time the device is applied if it was used at a single point in time.
- author dateTime references the time the action was recorded.
- Refer to the eCQM expression to determine allowable timings to meet measure criteria.
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.
See Appendix 6.1 for updated guidance regarding how to use Device, Applied
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.
relevantDateTime
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.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatyperelated actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod