Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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

4.4.1.381 Value Set http://hl7.org/fhir/ValueSet/issue-type

FHIR Infrastructure Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Any
This page has been approved as part of an ANSI standard. See the Infrastructure Package for further details.

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/issue-type
Version:4.2.0
Name:IssueType
Title:IssueType
Definition:

A code that describes the type of issue.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.410 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.381.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.1.381.2 Expansion

This expansion generated 31 Dec 2019

This value set contains 31 concepts

Expansion based on http://hl7.org/fhir/issue-type version 4.2.0

All codes from system http://hl7.org/fhir/issue-type

LvlCodeDisplayDefinition
0invalidInvalid ContentContent invalid against the specification or a profile.
1  structureStructural IssueA structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc.
1  requiredRequired element missingA required element is missing.
1  valueElement value invalidAn element or header value is invalid.
1  invariantValidation rule failedA content validation rule failed - e.g. a schematron rule.
0securitySecurity ProblemAn authentication/authorization/permissions issue of some kind.
1  loginLogin RequiredThe client needs to initiate an authentication process.
1  unknownUnknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).
1  expiredSession ExpiredUser session expired; a login may be required.
1  forbiddenForbiddenThe user does not have the rights to perform this action.
1  suppressedInformation 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.
0processingProcessing FailureProcessing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.
1  not-supportedContent not supportedThe interaction, operation, resource or profile is not supported.
1  duplicateDuplicateAn attempt was made to create a duplicate record.
1  multiple-matchesMultiple MatchesMultiple matching records were found when the operation required only one match.
1  not-foundNot 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    deletedDeletedThe reference pointed to content (usually a resource) that has been deleted.
1  too-longContent Too LongProvided content is too long (typically, this is a denial of service protection type of error).
1  code-invalidInvalid CodeThe code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.
1  extensionUnacceptable ExtensionAn extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.
1  too-costlyOperation Too CostlyThe operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT.
1  business-ruleBusiness Rule ViolationThe content/operation failed to pass some business rule and so could not proceed.
1  conflictEdit 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.).
0transientTransient IssueTransient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved.
1  lock-errorLock ErrorA resource/record locking failure (usually in an underlying database).
1  no-storeNo 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.
1  exceptionExceptionAn unexpected internal error has occurred.
1  timeoutTimeoutAn internal timeout has occurred.
1  incompleteIncomplete 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).
1  throttledThrottledThe system is not prepared to handle this request due to load management.
0informationalInformational 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:

LvlA 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
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