This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon ValueSet http://hl7.org/fhir/ValueSet/issue-type

FHIR Infrastructure icon Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Country: World
Official URL: http://hl7.org/fhir/ValueSet/issue-type Version: 6.0.0-cibuild
active as of 2020-12-28 Computable Name: IssueType
Flags: Immutable OID: 2.16.840.1.113883.4.642.3.410

This value set is used in the following places:

A code that describes the type of issue.


This expansion generated 19 Jul 2024

Expansion based on codesystem Issue Type v6.0.0-cibuild (CodeSystem)

This value set contains 33 concepts.

1  invalidhttp://hl7.org/fhir/issue-typeInvalid Content

Content invalid against the specification or a profile.

2    structurehttp://hl7.org/fhir/issue-typeStructural Issue

A structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc.

2    requiredhttp://hl7.org/fhir/issue-typeRequired element missing

A required element is missing.

2    valuehttp://hl7.org/fhir/issue-typeElement value invalid

An element or header value is invalid.

2    invarianthttp://hl7.org/fhir/issue-typeValidation rule failed

A content validation rule failed - e.g. a schematron rule.

1  securityhttp://hl7.org/fhir/issue-typeSecurity Problem

An authentication/authorization/permissions issue of some kind.

2    loginhttp://hl7.org/fhir/issue-typeLogin Required

The client needs to initiate an authentication process.

2    unknownhttp://hl7.org/fhir/issue-typeUnknown User

The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).

2    expiredhttp://hl7.org/fhir/issue-typeSession Expired

User session expired; a login may be required.

2    forbiddenhttp://hl7.org/fhir/issue-typeForbidden

The user does not have the rights to perform this action.

2    suppressedhttp://hl7.org/fhir/issue-typeInformation Suppressed

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.

1  processinghttp://hl7.org/fhir/issue-typeProcessing Failure

Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.

2    not-supportedhttp://hl7.org/fhir/issue-typeContent not supported

The interaction, operation, resource or profile is not supported.

2    duplicatehttp://hl7.org/fhir/issue-typeDuplicate

An attempt was made to create a duplicate record.

2    multiple-matcheshttp://hl7.org/fhir/issue-typeMultiple Matches

Multiple matching records were found when the operation required only one match.

2    not-foundhttp://hl7.org/fhir/issue-typeNot 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.

3      deletedhttp://hl7.org/fhir/issue-typeDeleted

The reference pointed to content (usually a resource) that has been deleted.

2    too-longhttp://hl7.org/fhir/issue-typeContent Too Long

Provided content is too long (typically, this is a denial of service protection type of error).

2    code-invalidhttp://hl7.org/fhir/issue-typeInvalid Code

The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.

2    extensionhttp://hl7.org/fhir/issue-typeUnacceptable Extension

An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.

2    too-costlyhttp://hl7.org/fhir/issue-typeOperation Too Costly

The operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT.

2    business-rulehttp://hl7.org/fhir/issue-typeBusiness Rule Violation

The content/operation failed to pass some business rule and so could not proceed.

2    conflicthttp://hl7.org/fhir/issue-typeEdit 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 409 error, but this code may be used where the conflict is discovered further into the application architecture.).

2    limited-filterhttp://hl7.org/fhir/issue-typeLimited Filter Application

Some search filters might not have applied on all results. Data may have been included that does not meet all of the filters listed in the self Bundle.link.

1  transienthttp://hl7.org/fhir/issue-typeTransient Issue

Transient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved.

2    lock-errorhttp://hl7.org/fhir/issue-typeLock Error

A resource/record locking failure (usually in an underlying database).

2    no-storehttp://hl7.org/fhir/issue-typeNo Store Available

The persistent store is unavailable; e.g. the database is down for maintenance or similar action, and the interaction or operation cannot be processed.

2    exceptionhttp://hl7.org/fhir/issue-typeException

An unexpected internal error has occurred.

2    timeouthttp://hl7.org/fhir/issue-typeTimeout

An internal timeout has occurred.

2    incompletehttp://hl7.org/fhir/issue-typeIncomplete Results

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).

2    throttledhttp://hl7.org/fhir/issue-typeThrottled

The system is not prepared to handle this request due to load management.

1  informationalhttp://hl7.org/fhir/issue-typeInformational 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.).

1  successhttp://hl7.org/fhir/issue-typeOperation Successful

The operation completed successfully.


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