Back to top
Top
U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

["Device, Applied": "Cardiac Pacer"]

Performance/Reporting Period
2022
Value Set Description from VSAC
Clinical Focus: The purpose of this value set is to represent concepts for a cardiac pacer device.
Data Element Scope: This value set may use a model element related to Device.
Inclusion Criteria: Includes concepts that represent a device that is a cardiac pacer.
Exclusion Criteria: No exclusions.

Constrained to codes in the Device, Applied: Cardiac Pacer value set (2.16.840.1.113883.3.526.3.1193)

QDM Datatype and Definition

"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

 

QDM Attributes

relevantDateTime

Relevant dateTime addresses the time an activity occurs as a single point in time. If the activity occurs over a period of time, use Relevant Period.

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

Last Updated: Jul 08, 2021