The Public Comment is now open through March 25, 2026 on the Draft 2027 CMS QRDA I Implementation Guide, Schematron, and Sample File for Hospital Quality Reporting
Top
Official websites use
.gov
A .gov website belongs to an official government organization in the United States.
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.
["Procedure, Performed": "Tumor staging (tumor staging)"]
Performance/Reporting Period
2024
Direct Reference Code
Constrained to 'Tumor staging (tumor staging)' SNOMEDCT code
QDM Datatype and Definition
"Procedure, Performed"
Data elements that meet criteria using this datatype should document the completion of the procedure indicated by the QDM category and its corresponding value set.
Timing:
- relevant dateTime references the time the procedure is performed when the procedure occurs at a single point in time.
- relevantPeriod references a start and stop time for a procedure that occurs over a time interval. relevantPeriod addresses:
- startTime - The time the procedure begins.
- stopTime - The time the procedure ends.
- author dateTime references the time the action was recorded.
- Refer to the eCQM expression to determine allowable timings to meet measure criterion.
Notes:
- Timing refers to a single instance of a procedure. If a measure seeks to evaluate multiple procedures over a period of time, the measure developer should use CQL logic to represent the query request.
- The incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
- 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 section 6.4 for guidance about differentiating between successful and unsuccessful procedures.
eCQMs using this data element:
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 relevantPeriod.
relevantPeriod
relevantPeriod addresses the time between the start of an action to the end of an action. Each QDM datatype using relevantPeriod 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 datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod
result
The final consequences or data collected from the datatype. results can be used in four ways to express:
- That a result is present in the electronic record but any entry is acceptable
- A numerical result is reported directly as a value. Values may be integers or decimal numbers without units, or as a quantity with a value and units - examples:
- 100mg/dL for a lab test
- 140 mmHg for blood pressure
- as a percentage (actually as a quantity with % as units)
- as a titer or ratio (e.g., 1:4, 1:80)
- A result that matches one of a specific set of coded concepts in a value set or a code that matches a direct reference code
- A result as a dateTime ("Assessment, Performed" and components)
Last Updated: Jun 29, 2023