Back to top
Top

"Adverse Event"

QDM Datatype

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

Data elements that meet criteria using this datatype should document the adverse event and its corresponding value set.

The relevant dateTime references the adverse event occurred.

The author dateTime references the time the adverse event was recorded.

QDM Category (QDM Version 5.5 Guidance Update)

Adverse Event

Adverse Event is used to define any untoward medical occurrence associated with the clinical care delivery, whether or not considered drug related.
Data Elements defined by this QDM Datatype:
QDM Attributes

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.

facilityLocation

The particular locations in a facility in which the diagnostic study or encounter occurs or occurred. Examples include intensive care units (ICUs), nonICUs, burn critical care unit, neonatal ICU, and respiratory care unit. Each "Encounter, Performed" may have one or more locations. For example, a patient treated in multiple locations during an individual encounter might be expressed as:
  • "Encounter, Performed": Inpatient Admission, facility locations
    • ICU (locationPeriod)
    • Non-ICU Admission (locationPeriod)
    • Rehab (locationPeriod)

recorder

The recorder indicates who recorded (or documented) the information (e.g., the individual or organization documenting the information). Note that HL7 FHIR modeling includes reference to asserter for concepts such as diagnosis and Allergy/Intolerance. Feedback from implementers and EHR vendors suggest that asserter fields default to the individual entering the information without clear evidence about how often clinicians change the default to theperson who reported the information. Therefore, QDM retains a recorder attribute for the referenced QDM datatypes.

The prescriber 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 recorded a diagnosis is the same person who was the primary participant in an Encounter 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.

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

severity

Indicates the intensity of the specified datatype (e.g., persistent, moderate, or severe).

type

The characterization of the reaction (e.g., hypersensitivity, rash, gastroenteric symptoms, etc.).
Last Updated: Jul 08, 2021