This
page
is
part
of
the
FHIR
Specification
(v4.3.0:
R4B
(v5.0.0-draft-final:
Final
QA
Preview
for
R5
-
STU
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:
R5
R4B
R4
R3
R2
Infrastructure
And
Messaging
Work
Group
|
Maturity Level : 1 | Draft | Use Context : Country: World, Not Intended for Production use |
Official
URL
:
http://hl7.org/fhir/ValueSet/message-reason-encounter
|
|
|||
| draft as of 2023-03-01 |
|
|||
|
|
|
|||
This value set is used in the following places:
Example Message Reasons. These are the set of codes that might be used an updating an encounter using admin-update.
http://terminology.hl7.org/CodeSystem/message-reasons-encounter
This
expansion
generated
28
May
2022
01
Mar
2023
This value set contains 6 concepts
Expansion
based
on
Example
Message
Reason
Codes
v4.3.0
v0.1.0
(CodeSystem)
All
codes
in
this
table
are
from
the
system
http://terminology.hl7.org/CodeSystem/message-reasons-encounter
| Code | System | Display | Definition |
admit
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | Admit |
The patient has been admitted. |
discharge
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | Discharge |
The patient has been discharged. |
absent
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | Absent |
The patient has temporarily left the institution. |
return
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | Returned |
The patient has returned from a temporary absence. |
moved
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | Moved |
The patient has been moved to a new location. |
edit
|
http://terminology.hl7.org/CodeSystem/message-reasons-encounter | 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:
| 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 |