This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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 R2
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/message-reason-encounter | 
| Name: | Example Message Reason Codes | 
| Definition: | Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update. | 
| Committee: | FHIR Infrastructure   Work Group | 
| OID: | 2.16.840.1.113883.4.642.2.202 (for OID based terminology systems) | 
| Source Resource | XML / JSON | 
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 06 Dec 2016
This value set contains 6 concepts
Expansion based on http://hl7.org/fhir/message-reasons-encounter version 1.8.0
All codes from system http://hl7.org/fhir/message-reasons-encounter
| Code | Display | Definition | 
| admit | Admit | The patient has been admitted. | 
| discharge | Discharge | The patient has been discharged. | 
| absent | Absent | The patient has temporarily left the institution. | 
| return | Returned | The patient has returned from a temporary absence. | 
| moved | Moved | The patient has been moved to a new location. | 
| edit | Edit | Encounter details have been updated (e.g. to correct a coding error). | 
See the full registry of value sets 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. In this scheme, some codes are under other codes, and imply that the code they are under also applies | 
| 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) | 
| 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 |