R5 Final QA

This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - 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

4.3.2.168 CodeSystem http://hl7.org/fhir/issue-type

FHIR Infrastructure icon Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Country: World
Official URL: http://hl7.org/fhir/issue-type Version: 5.0.0-draft-final
active as of 2021-01-05 Computable Name: IssueType
Flags: CaseSensitive, Complete. All codes ValueSet: Issue Type OID: 2.16.840.1.113883.4.642.4.411

This Code system is used in the following value sets:

  • ValueSet: Issue Type (A code that describes the type of issue.)

4.3.2.168.1 Definition

A code that describes the type of issue.

4.3.2.168.2 Content

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

LvlCodeDisplayDefinitionCopy
1invalid Invalid ContentContent invalid against the specification or a profile.btn btn
2  structure Structural IssueA structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc.btn btn
2  required Required element missingA required element is missing.btn btn
2  value Element value invalidAn element or header value is invalid.btn btn
2  invariant Validation rule failedA content validation rule failed - e.g. a schematron rule.btn btn
1security Security ProblemAn authentication/authorization/permissions issue of some kind.btn btn
2  login Login RequiredThe client needs to initiate an authentication process.btn btn
2  unknown Unknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).btn btn
2  expired Session ExpiredUser session expired; a login may be required.btn btn
2  forbidden ForbiddenThe user does not have the rights to perform this action.btn btn
2  suppressed Information SuppressedSome 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.btn btn
1processing Processing FailureProcessing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.btn btn
2  not-supported Content not supportedThe interaction, operation, resource or profile is not supported.btn btn
2  duplicate DuplicateAn attempt was made to create a duplicate record.btn btn
2  multiple-matches Multiple MatchesMultiple matching records were found when the operation required only one match.btn btn
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.btn btn
3    deleted DeletedThe reference pointed to content (usually a resource) that has been deleted.btn btn
2  too-long Content Too LongProvided content is too long (typically, this is a denial of service protection type of error).btn btn
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.btn btn
2  extension Unacceptable ExtensionAn extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.btn btn
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.btn btn
2  business-rule Business Rule ViolationThe content/operation failed to pass some business rule and so could not proceed.btn btn
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 409 error, but this code may be used where the conflict is discovered further into the application architecture.).btn btn
1transient Transient IssueTransient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved.btn btn
2  lock-error Lock ErrorA resource/record locking failure (usually in an underlying database).btn btn
2  no-store No Store AvailableThe persistent store is unavailable; e.g. the database is down for maintenance or similar action, and the interaction or operation cannot be processed.btn btn
2  exception ExceptionAn unexpected internal error has occurred.btn btn
2  timeout TimeoutAn internal timeout has occurred.btn btn
2  incomplete Incomplete ResultsNot 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).btn btn
2  throttled ThrottledThe system is not prepared to handle this request due to load management.btn btn
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.).btn btn
1success Operation SuccessfulThe operation completed successfully.btn btn

 

See the full registry of code systems 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. See Code System for further information.
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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