US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 10.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions

Adverse Events: Clinical Records and Patient Safety Reporting

Page standards status: Trial-use

This artifact is new for US Core Version 10.0.0-ballot

Introduction

The U.S. Core Data for Interoperability (USCDI) Adverse Events Data Class comprises two Data Elements, Adverse Event Condition and Adverse Event Outcome. An adverse event condition is a change to a patient's condition that could be an unintended effect of a clinical intervention, such as a rash or a fever. An adverse event outcome is the resulting patient status or consequence following that change, such as hospitalization, recovery, recovery with sequelae, or death.

US Core does not define an AdverseEvent profile and does not use the FHIR AdverseEvent resource. Instead, this page documents how the information the two Data Elements describe is already recorded by existing US Core Profiles, and which profiles to look in.

Clinical Records and Patient Safety Reporting

The distinction this page draws is between two different activities that the same incident can give rise to:

1. The clinical record. A clinician documents what happened to the patient, using the same resources used for any other clinical finding, note, or procedure. This is the information the USCDI Adverse Events Data Class describes, and it is what US Core supports.
2. Patient safety reporting. A separate process classifies an incident, investigates its cause, and reports it for safety or regulatory purposes. This typically happens outside the clinical record, in risk management systems.

USCDI v7 scopes the Adverse Events Data Class to the first of these. It explicitly excludes the exchange of patient safety analyses, internal risk management documentation, and patient safety work products as defined under the Patient Safety and Quality Improvement Act of 2005 and its implementing regulations, and it excludes Patient Safety Organization investigations, safety reviews, and facility-level reporting activities. US Core follows that boundary: nothing on this page concerns patient safety work product, and no US Core Profile is intended to carry it.

Two consequences follow for implementers:

• Adverse events are recorded as ordinary clinical events, and are not tagged as adverse events. A rash following an immunization is recorded as a reaction, a condition, an observation, or a note, in the same way any other rash would be. Systems should not expect a flag, a category code, or a dedicated resource that marks a clinical record entry as an adverse event. Determining that an event was adverse, and that a clinical intervention caused it, is a judgment made elsewhere.
• A query for adverse events is a query across several profiles. Because the information is recorded wherever the clinician documented it, there is no single place to look. The profiles below are the candidates.

Where Adverse Event Information Is Recorded

The following US Core Profiles shown in the figure below record the information the two Data Elements describe. The profiles overlap: the same incident may be recorded in more than one of them, and which one a system uses depends on how the clinician documented it.

Adverse Event Condition can be recorded by the profiles listed below, and by:

• US Core Immunization Profile - in Immunization.reaction, for a reaction following an immunization
• US Core Procedure Profile - when a procedure is the intervention the change is associated with

Adverse Event Condition and Adverse Event Outcome can be recorded by:

• US Core AllergyIntolerance Profile - in AllergyIntolerance.reaction.manifestation, for a reaction to a substance the patient is sensitive to
• US Core Condition Problems and Health Concerns Profile and US Core Condition Encounter Diagnosis Profile - when the change to the patient's condition is recorded as a problem or an encounter diagnosis
• US Core DocumentReference Profile - when it is documented in a clinical note (see the Clinical Notes page)
• US Core Simple Observation Profile - when it is recorded as an observation that no more specific profile covers

Adverse Event Outcome can be recorded by the profiles above, and by:

• US Core Encounter Profile - in Encounter.hospitalization.dischargeDisposition, where an outcome such as hospitalization or death is recorded as part of the encounter
• US Core CarePlan Profile - where the response to the outcome is recorded as part of the plan of treatment

Overlap with Other USCDI Data Classes

Note the overlap with the USCDI Allergies and Intolerances Data Class. AllergyIntolerance.reaction records a known patient sensitivity and the manifestations it produces; the Adverse Events Data Class describes an occurrence associated with a specific clinical intervention. The same manifestation can appear in both contexts, recorded in the same element.

Terminology

USCDI names SNOMED CT as an applicable vocabulary standard for Adverse Event Condition. It names no vocabulary standard for Adverse Event Outcome. US Core places no additional binding on any element for this Data Class beyond what the profiles above already require, so the terminology for each element is the terminology that profile already specifies.

This guidance page is a draft for this ballot. Further editing and examples are still pending.