"Procedure, Order"

Performance/Reporting Period

2022

QDM Datatype (QDM Version 5.5 Guidance Update):

Data elements that meet criteria using this datatype should document a request for the procedure indicated by the QDM category and its corresponding value set.

Timing: The time the order is signed; author dateTime.

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

QDM Datatype and Definition

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:

["Procedure, Order": "Injection of leuprolide acetate for twelve month period (regime/therapy)"]

QDM Attributes

anatomicalLocationSite

The anatomical site or structure

Where the diagnosis/problem manifests itself (a).
That is the focus of the action represented by the datatype (b).

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.

negationRationale

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.

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.

priority

priority indicates the urgency of the procedure or the encounter referenced. In eCQMs the priority attribute will help specify elective from urgent encounters (e.g., hospital admissions) or procedures. priority is a codable concept (i.e., may use a direct reference code or a value set). For example, priority is used to express an elective procedure or encounter from an emergency procedure or encounter.)

rank

Rank defines a position in a hierarchy for diagnoses or procedures. It replaces ordinality previously assigned to "Procedure, Performed", "Procedure, Order", and "Procedure, Recommended". ordinality does not align with any FHIR resources; it does align with definitions for FHIR encounter.diagnosis. Thus, the concept fits best consistently across QDM for the concept of principal for encounter diagnosis and for procedure.

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.

reason

requester

The requester is who or what is requesting service (e.g., the individual or organization asking for the service to be carried out). The requester attribute references the new QDM entities (Patient, Care Partner, Practitioner, or Organization) and any or all of the attributes of the respective QDM entity. For example, to reference that a physician who requested a procedure is the same person who was the primary participant in an "Encounter, Performed" and assure the physician's specialty meets the measures requirements, the eCQM can use the Practitioner Entity and its attributes. Should the eCQM choose to reference a physician practice or a hospital, the performer can reference the Organization Entity and indicate the identifier and/or the organization type.

We want your feedback