["Communication, Performed": "Consultant Report"]

Performance/Reporting Period

2023

Value Set Description from VSAC

Clinical Focus: The purpose of this value set is to represent concepts for consultant reports.
Data Element Scope: This value set may use a model element related to Assessment.
Inclusion Criteria: Includes concepts that represent various consultant reports and notes.
Exclusion Criteria: No exclusions.

Constrained to codes in the Communication, Performed: Consultant Report value set (2.16.840.1.113883.3.464.1003.121.12.1006)

QDM Datatype and Definition

"Communication, Performed"

Data elements that meet criteria using this datatype reference conveyance of information from one entity (e.g., person, organization, or device) to another.

The "Communication, Performed" code attribute represents the reason for the communication (i.e., the subject). The category attribute allows reference to the type, or category, of communication (e.g., notification, request). In many cases, the eCQM developer may not know the local workflow to address the type of communication; hence, it is listed as an attribute to be used as feasibility allows.

Timing:

sent dateTime - when the communication was sent.
received dateTime - when the communication was received.

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.

QDM Attributes

receivedDateTime

The time a communication was received.

relatedTo

An attribute that indicates one QDM data element fulfills the expectations of another QDM data element.

See Section 5.8 for examples for using relatedTo.

Note: QDM 5.6 relatedTo attribute is consistent with the FHIR element basedOn which is available for many FHIR resources addressed by the QDM datatypes added in the QDM 5.6 version. These QDM additions allow evaluation and testing during a period of FHIR transition specifically to relate actions with orders that generate them. However, measure developers should carefully determine feasibility for each use case when using the relatedTo attribute.