STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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

4.2.11.224 Code System http://hl7.org/fhir/issue-type

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/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.1.224 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • IssueType (A code that describes the type of issue.)

4.2.11.224.1 Content

4.2.11.224.2 IssueType

A code that describes the type of issue.

This code system http://hl7.org/fhir/issue-type defines the following codes:

LvlCodeDisplayDefinition
1invalid Invalid ContentContent invalid against the specification or a profile.
2  structure Structural IssueA structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax.
2  required Required element missingA required element is missing.
2  value Element value invalidAn element value is invalid.
2  invariant Validation rule failedA content validation rule failed - e.g. a schematron rule.
1security Security ProblemAn authentication/authorization/permissions issue of some kind.
2  login Login RequiredThe client needs to initiate an authentication process.
2  unknown Unknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).
2  expired Session ExpiredUser session expired; a login may be required.
2  forbidden ForbiddenThe user does not have the rights to perform this action.
2  suppressed Information SuppressedSome 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.
1processing Processing FailureProcessing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.
2  not-supported Content not supportedThe resource or profile is not supported.
2  duplicate DuplicateAn attempt was made to create a duplicate record.
2  not-found Not FoundThe 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.
2  too-long Content Too LongProvided content is too long (typically, this is a denial of service protection type of error).
2  code-invalid Invalid CodeThe code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.
2  extension Unacceptable ExtensionAn extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.
2  too-costly Operation Too CostlyThe operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT.
2  business-rule Business Rule ViolationThe content/operation failed to pass some business rule, and so could not proceed.
2  conflict Edit Version ConflictContent 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.)
2  incomplete Incomplete ResultsNot all data sources typically accessed could be reached, or responded in time, so the returned information may not be complete.
1transient Transient IssueTransient processing issues. The system receiving the error may be able to resubmit the same content once an underlying issue is resolved.
2  lock-error Lock ErrorA resource/record locking failure (usually in an underlying database).
2  no-store No Store AvailableThe persistent store is unavailable; e.g. the database is down for maintenance or similar action.
2  exception ExceptionAn unexpected internal error has occurred.
2  timeout TimeoutAn internal timeout has occurred.
2  throttled ThrottledThe system is not prepared to handle this request due to load management.
1informational Informational NoteA 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:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code