This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
(v4.0.1:
R4
-
Mixed
Normative
and
STU
3).
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
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:
R5
R4B
R4
R3
R4
R3
Work
Group
|
Maturity Level : 0 |
|
Use Context : Any |
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/adverse-event-outcome |
| Version: | 4.0.1 |
| Name: | AdverseEventOutcome |
| Title: | AdverseEventOutcome |
| Definition: |
TODO
(and
should
this
be
|
| Committee: |
Work
Group
|
| OID: |
|
| Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://hl7.org/fhir/adverse-event-outcome
http://terminology.hl7.org/CodeSystem/adverse-event-outcome
This
expansion
generated
19
Apr
2017
01
Nov
2019
This value set contains 6 concepts
Expansion
based
on
http://hl7.org/fhir/adverse-event-outcome
http://terminology.hl7.org/CodeSystem/adverse-event-outcome
version
3.0.2
4.0.1
All
codes
from
system
http://hl7.org/fhir/adverse-event-outcome
http://terminology.hl7.org/CodeSystem/adverse-event-outcome
| Code | Display | Definition |
| resolved | Resolved | |
| recovering | Recovering | |
| ongoing | Ongoing | |
| resolvedWithSequelae | Resolved with Sequelae | |
| fatal | Fatal | |
| unknown | Unknown |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
|
|
A
few
code
lists
that
FHIR
defines
are
hierarchical
-
each
code
is
assigned
a
level.
|
| 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 |