This page is part of the FHIR Specification v4.1.0: R4B Ballot. About the R4B version of FHIR. 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
. Page versions: R5 R4B R4 R3
| Patient Care  Work Group | Maturity Level: 0 | Trial Use | 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.1.0 | 
| Name: | AdverseEventOutcome | 
| Title: | AdverseEventOutcome | 
| Definition: | TODO (and should this be required?). | 
| Committee: | Patient Care  Work Group | 
| OID: | 2.16.840.1.113883.4.642.3.836 (for OID based terminology systems) | 
| Source Resource | XML / JSON | 
This value set is used in the following places:
http://terminology.hl7.org/CodeSystem/adverse-event-outcome
This expansion generated 11 Mar 2021
This value set contains 6 concepts
Expansion based on AdverseEventOutcome v4.1.0 (CodeSystem)
All codes from system 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:
| Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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 |