Back to top
Top

Procedure, Performed

Performance/Reporting Period
2021
QDM Datatype (QDM Version 5.5 Guidance Update):

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.

Two QDM Known Issues has been identified related to this datatype.

  • To see the QDM Known Issue related to QDM Procedure, Performed completion time, please click here.
  • To see the QDM Known Issue related to Differentiating Elective Vs Emergent or Urgent Procedures, please click here.

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.
  • For clarification, see Appendix 6.6 with 2020 guidance about differentiating between successful and unsuccessful procedures.
QDM Category (QDM Version 5.5 Guidance Update)

Procedure

Procedure is derived directly from HL7 and Canada Health Infoway: 'An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject. ...Procedure is but one among several types of clinical activities such as observation, substance-administrations, and communicative interactions ... Procedure does not comprise all acts of [sic] whose intent is intervention or treatment.' A procedure may be a surgery or other type of physical manipulation of a person's body in whole or in part for purposes of making observations and diagnoses or providing treatment.
Data Elements defined by this QDM Datatype:
QDM Attributes

Anatomical Location Site

The anatomical site or structure
  • Where the diagnosis/problem manifests itself (a).
  • That is the focus of the action represented by the datatype (b).

Author dateTime

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.

Components

Elements included or documented as part of evaluations or test panels.
  • Examples include: specific questions included in assesments, tests included in a laboratory test panel, observations included in a cardiac exam during a physical examination. Each assessment, diagnostic study, laboratory test, physical exam, or procedure may have one or more components.
components also reference specific details about an encounter diagnosis.
  • Examples include an "Encounter, Performed" diagnosis that is also present on admission and refers to the principal diagnosis (rank = 1)

Incision dateTime

The date and time of the first incision of the procedure. Incision dateTime is a single point in time available from the Operating Room and/or Anesthesia Record.

Method

Indicates the procedure or technique used in its performance.

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

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

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.

Reason

The thought process or justification for the datatype. In some measures, specific treatments are acceptable inclusion criteria only if a justified reason is present. Each of these measures uses a value set (often, but not exclusively, using SNOMED CT) to express acceptable justification reasons. Other measures specify reasons as justification for exclusions. Examples include patient, system, or medical-related reasons for declining to perform specific actions. Each of these measures also uses a value set to express acceptable justification reasons for declining to perform expected actions.

Relevant Period

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

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)

Status

Indicates the particular stage of the action represented by the datatype.
Last Updated: Aug 13, 2020