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.

["Procedure, Performed": "Rehabilitation Therapy"]

Performance/Reporting Period
2019
Value Set Description from VSAC
Clinical Focus: This value set contains concepts that represent procedures that represent rehabilitation therapy post stroke.
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Procedure. The intent of this data element is to identify stroke rehabilitation therapies.
Inclusion Criteria: Includes only relevant concepts associated with SNOMED CT codes that identify rehabilitation therapies used appropriate for stroke rehabilitation.
Exclusion Criteria: Excludes codes that do not meet the inclusion criteria.

Constrained to codes in the Procedure, Performed: Rehabilitation Therapy value set (2.16.840.1.113762.1.4.1045.19)

QDM Datatype and Definition (QDM Version 5.3)

"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.

A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.

Timing: The Relevant Period addresses:

  • startTime -the time the procedure begins,
  • stopTime -the time the procedure is completed

NOTE:

  1. 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.
  2. The Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.
QDM Attributes

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.

negationRationale

The QDM attribute, negation rationale 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 that any information expected will be in a clinical record. The situation is different when something that normally would be expected to be done is specifically not done because of a valid clinical reason (such as the patient is allergic, they are suffering from a complication, or some other rationale. In this case, the 'thing not done' is rarely documented, especially as a code, in the patient record. To express such lack of evidence, an eCQM author should use a CQL 'not exists' expression noted in the examples, and they must also capture the Negation rationale to capture a reason for the absence, i.e., the reason must be included to qualify as a negation rationale type expression. The syntax in the human readable HQMF is described in CQL examples and in the MAT User Guide. Prior versions of QDM used the syntax, 'Procedure, Performed not done.' QDM 5.5 uses the syntax, 'Procedure, not Performed' and this is then associated with either a DRC or a value set used to identify 'the expected thing,' that in this case was not done. Negation Rationale attribute value 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.

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.
Last Updated: Jul 08, 2021