Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.3.16.347 Code System http://terminology.hl7.org/CodeSystem/adverse-event-seriousness

Patient Care

Work Group

Maturity Level: 1

Draft

Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL: http://terminology.hl7.org/CodeSystem/adverse-event-seriousness

Version: 4.6.0

Name: AdverseEventSeriousness

Title: AdverseEventSeriousness

Definition:

Overall seriousness of this event for the patient.

Committee: Patient Care Work Group

OID: 2.16.840.1.113883.4.642.1.1253 (for OID based terminology systems)

Source Resource XML / JSON

This Code system is used in the following value sets:

ValueSet: AdverseEventSeriousness (Overall seriousness of this event for the patient.)
ValueSet: AdverseEventSeriousness (Overall seriousness of this event for the patient.)

4.3.16.347.1 Content

This code system http://terminology.hl7.org/CodeSystem/adverse-event-seriousness defines the following codes:

Code	Display	Definition
non-serious	Non-serious	This event is considered not to have the potential for persistent or costly injury or consequence.
serious	Serious	This event is considered to have the potential for persistent or costly injury or consequence.

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')

Display

The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code