This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
FHIR Infrastructure Work Group | Maturity Level: N | Normative (from v4.0.0) | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/issue-type
|
Version: 5.0.0 | |||
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.
http://hl7.org/fhir/issue-type
This expansion generated 26 Mar 2023
This value set contains 33 concepts
Expansion based on Issue Type v5.0.0 (CodeSystem)
Level | Code | System | Display | Definition |
1 | invalid | http://hl7.org/fhir/issue-type | Invalid Content | Content invalid against the specification or a profile. |
2 | structure | http://hl7.org/fhir/issue-type | Structural Issue | A structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc. |
2 | required | http://hl7.org/fhir/issue-type | Required element missing | A required element is missing. |
2 | value | http://hl7.org/fhir/issue-type | Element value invalid | An element or header value is invalid. |
2 | invariant | http://hl7.org/fhir/issue-type | Validation rule failed | A content validation rule failed - e.g. a schematron rule. |
1 | security | http://hl7.org/fhir/issue-type | Security Problem | An authentication/authorization/permissions issue of some kind. |
2 | login | http://hl7.org/fhir/issue-type | Login Required | The client needs to initiate an authentication process. |
2 | unknown | http://hl7.org/fhir/issue-type | Unknown User | The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable). |
2 | expired | http://hl7.org/fhir/issue-type | Session Expired | User session expired; a login may be required. |
2 | forbidden | http://hl7.org/fhir/issue-type | Forbidden | The user does not have the rights to perform this action. |
2 | suppressed | http://hl7.org/fhir/issue-type | Information 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 | processing | http://hl7.org/fhir/issue-type | Processing Failure | Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged. |
2 | not-supported | http://hl7.org/fhir/issue-type | Content not supported | The interaction, operation, resource or profile is not supported. |
2 | duplicate | http://hl7.org/fhir/issue-type | Duplicate | An attempt was made to create a duplicate record. |
2 | multiple-matches | http://hl7.org/fhir/issue-type | Multiple Matches | Multiple matching records were found when the operation required only one match. |
2 | not-found | http://hl7.org/fhir/issue-type | 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. |
3 | deleted | http://hl7.org/fhir/issue-type | Deleted | The reference pointed to content (usually a resource) that has been deleted. |
2 | too-long | http://hl7.org/fhir/issue-type | Content Too Long | Provided content is too long (typically, this is a denial of service protection type of error). |
2 | code-invalid | http://hl7.org/fhir/issue-type | Invalid Code | The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code. |
2 | extension | http://hl7.org/fhir/issue-type | Unacceptable Extension | An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized. |
2 | too-costly | http://hl7.org/fhir/issue-type | 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. |
2 | business-rule | http://hl7.org/fhir/issue-type | Business Rule Violation | The content/operation failed to pass some business rule and so could not proceed. |
2 | conflict | http://hl7.org/fhir/issue-type | 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 409 error, but this code may be used where the conflict is discovered further into the application architecture.). |
2 | limited-filter | http://hl7.org/fhir/issue-type | Limited 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 |
1 | transient | http://hl7.org/fhir/issue-type | Transient 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-error | http://hl7.org/fhir/issue-type | Lock Error | A resource/record locking failure (usually in an underlying database). |
2 | no-store | http://hl7.org/fhir/issue-type | No 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 | exception | http://hl7.org/fhir/issue-type | Exception | An unexpected internal error has occurred. |
2 | timeout | http://hl7.org/fhir/issue-type | Timeout | An internal timeout has occurred. |
2 | incomplete | http://hl7.org/fhir/issue-type | Incomplete 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 | throttled | http://hl7.org/fhir/issue-type | Throttled | The system is not prepared to handle this request due to load management. |
1 | informational | http://hl7.org/fhir/issue-type | 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.). |
1 | success | http://hl7.org/fhir/issue-type | Operation 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:
Lvl | A 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 |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |