This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). 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/issue-type |
Name: | IssueType |
Definition: | A code that describes the type of issue. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.2.224 (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 31 Mar 2016
This value set contains 29 concepts
All codes from system http://hl7.org/fhir/issue-type
Code | Display | Definition |
invalid | Invalid Content | Content invalid against the specification or a profile. |
structure | Structural Issue | A structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax. |
required | Required element missing | A required element is missing. |
value | Element value invalid | An element value is invalid. |
invariant | Validation rule failed | A content validation rule failed - e.g. a schematron rule. |
security | Security Problem | An authentication/authorization/permissions issue of some kind. |
login | Login Required | The client needs to initiate an authentication process. |
unknown | Unknown User | The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable). |
expired | Session Expired | User session expired; a login may be required. |
forbidden | Forbidden | The user does not have the rights to perform this action. |
suppressed | Information Suppressed | Some information was not or may 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 | Processing Failure | Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged. |
not-supported | Content not supported | The resource or profile is not supported. |
duplicate | Duplicate | An attempt was made to create a duplicate record. |
not-found | Not Found | 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. |
too-long | Content Too Long | Provided content is too long (typically, this is a denial of service protection type of error). |
code-invalid | Invalid Code | The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code. |
extension | Unacceptable Extension | An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized. |
too-costly | Operation Too Costly | The operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT. |
business-rule | Business Rule Violation | The content/operation failed to pass some business rule, and so could not proceed. |
conflict | Edit Version Conflict | 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 404 error, but this code may be used where the conflict is discovered further into the application architecture.) |
incomplete | Incomplete Results | Not all data sources typically accessed could be reached, or responded in time, so the returned information may not be complete. |
transient | Transient Issue | Transient processing issues. The system receiving the error may be able to resubmit the same content once an underlying issue is resolved. |
lock-error | Lock Error | A resource/record locking failure (usually in an underlying database). |
no-store | No Store Available | The persistent store is unavailable; e.g. the database is down for maintenance or similar action. |
exception | Exception | An unexpected internal error has occurred. |
timeout | Timeout | An internal timeout has occurred. |
throttled | Throttled | The system is not prepared to handle this request due to load management. |
informational | Informational Note | 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.). |
This value set includes codes from the following code systems:
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 |