This
page
is
part
of
the
Continuous
Integration
Build
of
FHIR
Specification
(v5.0.0:
R5
-
STU
).
This
is
the
current
published
version
in
it's
permanent
home
(it
will
always
(will
be
available
incorrect/inconsistent
at
this
URL).
For
a
full
list
of
available
versions,
see
times).
See
the
Directory
of
published
versions
Responsible
Owner:
Patient
Administration
Work
Group
|
|
Use Context : Country: World |
Official
URL
:
http://hl7.org/fhir/ValueSet/encounter-diagnosis-use
|
Version
:
|
|||
|
|
Computable Name : EncounterDiagnosisUse | |||
| Flags : Immutable | OID : 2.16.840.1.113883.4.642.4.3321 | |||
This value set is used in the following places:
What
a
specific
Encounter/EpisodeOfCare
diagnosis.condition
is
to
be
used
for.
Generated Narrative: ValueSet encounter-diagnosis-use
Last updated: 2025-11-27T16:48:47.349Z
http://hl7.org/fhir/encounter-diagnosis-use
version
📦6.0.0-ballot3
This
expansion
generated
26
Mar
2023
27
Nov
2025
ValueSet
Expansion
performed
internally
based
on
codesystem
Encounter
Diagnosis
Use
v5.0.0
v6.0.0-ballot3
(CodeSystem)
This value set contains 2 concepts
| System | Code |
|
|
http://hl7.org/fhir/encounter-diagnosis-use
| working |
|
|
http://hl7.org/fhir/encounter-diagnosis-use
| final |
|
Final diagnosis established at the end of the encounter or episode of care. |
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 |