Release
5
4
Terminology
This
page
is
part
of
the
FHIR
Specification
(v5.0.0:
R5
(v4.0.1:
R4
-
Mixed
Normative
and
STU
).
This
is
the
)
in
it's
permanent
home
(it
will
always
be
available
at
this
URL).
The
current
published
version.
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
|
FHIR
Infrastructure
Work
Group
|
Maturity Level : N | Normative (from v4.0.0) |
Use
Context
:
|
|
This
page
has
been
approved
as
part
of
an
ANSI
|
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/issue-type |
| Version: | 4.0.1 |
| Name: | IssueType |
| Title: | IssueType |
| Definition: |
A code that describes the type of issue. |
| Committee: |
Work
Group
|
| OID: | 2.16.840.1.113883.4.642.3.410 (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:
http://hl7.org/fhir/issue-type
This
expansion
generated
26
Mar
2023
01
Nov
2019
This
value
set
contains
33
31
concepts
Expansion based on http://hl7.org/fhir/issue-type version 4.0.1
All
codes
from
system
Issue
Type
v5.0.0
(CodeSystem)
http://hl7.org/fhir/issue-type
|
|
Code |
|
Definition |
|
|
|
|
Content invalid against the specification or a profile. |
|
|
|
|
A structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc. |
|
|
|
|
A required element is missing. |
|
|
|
|
An element or header value is invalid. |
|
|
|
|
A content validation rule failed - e.g. a schematron rule. |
|
|
|
|
An authentication/authorization/permissions issue of some kind. |
|
|
|
|
The client needs to initiate an authentication process. |
|
|
|
|
The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable). |
|
|
|
|
User session expired; a login may be required. |
|
|
|
|
The user does not have the rights to perform this action. |
|
|
|
|
Some information was not or might not have been returned due to business rules, consent or privacy rules, or access permission constraints. This information may be accessible through alternate processes. |
|
|
|
|
Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged. |
|
|
|
|
The interaction, operation, resource or profile is not supported. |
|
|
|
|
An attempt was made to create a duplicate record. |
|
|
|
|
Multiple matching records were found when the operation required only one match. |
|
|
|
|
The reference provided was not found. In a pure RESTful environment, this would be an HTTP 404 error, but this code may be used where the content is not found further into the application architecture. |
|
|
|
|
The reference pointed to content (usually a resource) that has been deleted. |
|
|
|
|
Provided content is too long (typically, this is a denial of service protection type of error). |
|
|
|
|
The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code. |
|
|
|
|
An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized. |
|
|
|
|
The operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT. |
|
|
|
|
The content/operation failed to pass some business rule and so could not proceed. |
|
|
|
|
Content
could
not
be
accepted
because
of
an
edit
conflict
(i.e.
version
aware
updates).
(In
a
pure
RESTful
environment,
this
would
be
an
HTTP
409
error,
but
this
code
may
be
used
where
the
conflict
is
discovered
further
into
the
application
architecture.).
|
|
|
|
|
Transient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved. |
|
|
|
|
A resource/record locking failure (usually in an underlying database). |
|
|
|
|
The persistent store is unavailable; e.g. the database is down for maintenance or similar action, and the interaction or operation cannot be processed. |
|
|
|
|
An unexpected internal error has occurred. |
|
|
|
|
An internal timeout has occurred. |
|
|
|
|
Not all data sources typically accessed could be reached or responded in time, so the returned information might not be complete (applies to search interactions and some operations). |
|
|
|
|
The system is not prepared to handle this request due to load management. |
|
|
|
|
A
message
unrelated
to
the
processing
success
of
the
completed
operation
(examples
of
the
latter
include
things
like
reminders
of
password
expiry,
system
maintenance
times,
etc.).
|
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 |
FHIR
®©
HL7.org
2011+.
FHIR
R5
hl7.fhir.core#5.0.0
Release
4
(Technical
Correction
#1)
(v4.0.1)
generated
on
Sun,
Mar
26,
2023
15:23+1100.
Fri,
Nov
1,
2019
09:33+1100.
QA
Page
Links:
Search
|
Version
History
|
Table
of
Contents
|
Glossary
|
QA
|
Compare
to
R4
Credits
|
Compare
to
R4B
R3
|
|
Propose
a
change