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
Public
Health
and
Emergency
Response
Work
Group
|
Maturity Level : 1 | Draft | Use Context : Country: World, Not Intended for Production use |
Official
URL
:
http://hl7.org/fhir/ValueSet/immunization-route
|
Version : 5.0.0-draft-final | |||
| draft as of 2023-03-01 | Computable Name : ImmunizationRouteCodes | |||
|
|
|
|||
This value set is used in the following places:
The value set to instantiate this attribute should be drawn from a terminologically robust code system that consists of or contains concepts to support describing the administrative routes used during vaccination. This value set is provided as a suggestive example.
http://terminology.hl7.org/CodeSystem/v3-RouteOfAdministration
| Code | Display | Definition |
IDINJ
|
Injection, intradermal | Injection, intradermal |
IM
|
Injection, intramuscular | Injection, intramuscular |
|
Injection, intravenous | Injection, intravenous |
PO
|
Swallow, oral | Swallow, oral |
SQ
|
Injection, subcutaneous | Injection, subcutaneous |
TRNSDERM
|
Transdermal | Transdermal |
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 |