Final2.16.840.1.113883.4.642.4.411 - IssueType - FHIR: http://hl7.org/fhir/issue-type
| Level/ Type | Code | Display Name | Code System | Code System Version | Designations | Description |
|---|---|---|---|---|---|---|
| 0‑S | invalid | Invalid Content | IssueType | 2019-11-01T09:29:23 |  Preferred: Invalid Content | Content invalid against the specification or a profile. |
| 1‑L | structure | Structural Issue | IssueType | 2019-11-01T09:29:23 | Preferred: Structural Issue | A structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc. |
| 1‑L | required | Required element missing | IssueType | 2019-11-01T09:29:23 | Preferred: Required element missing | A required element is missing. |
| 1‑L | value | Element value invalid | IssueType | 2019-11-01T09:29:23 | Preferred: Element value invalid | An element or header value is invalid. |
| 1‑L | invariant | Validation rule failed | IssueType | 2019-11-01T09:29:23 | Preferred: Validation rule failed | A content validation rule failed - e.g. a schematron rule. |
| 0‑S | security | Security Problem | IssueType | 2019-11-01T09:29:23 | Preferred: Security Problem | An authentication/authorization/permissions issue of some kind. |
| 1‑L | login | Login Required | IssueType | 2019-11-01T09:29:23 | Preferred: Login Required | The client needs to initiate an authentication process. |
| 1‑L | unknown | Unknown User | IssueType | 2019-11-01T09:29:23 | Preferred: Unknown User | The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable). |
| 1‑L | expired | Session Expired | IssueType | 2019-11-01T09:29:23 | Preferred: Session Expired | User session expired; a login may be required. |
| 1‑L | forbidden | Forbidden | IssueType | 2019-11-01T09:29:23 | Preferred: Forbidden | The user does not have the rights to perform this action. |
| 1‑L | suppressed | Information Suppressed | IssueType | 2019-11-01T09:29:23 | Preferred: 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. |
| 0‑S | processing | Processing Failure | IssueType | 2019-11-01T09:29:23 | Preferred: Processing Failure | Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged. |
| 1‑L | not-supported | Content not supported | IssueType | 2019-11-01T09:29:23 | Preferred: Content not supported | The interaction, operation, resource or profile is not supported. |
| 1‑L | duplicate | Duplicate | IssueType | 2019-11-01T09:29:23 | Preferred: Duplicate | An attempt was made to create a duplicate record. |
| 1‑L | multiple-matches | Multiple Matches | IssueType | 2019-11-01T09:29:23 | Preferred: Multiple Matches | Multiple matching records were found when the operation required only one match. |
| 1‑S | not-found | Not Found | IssueType | 2019-11-01T09:29:23 | Preferred: 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. |
| 2‑L | deleted | Deleted | IssueType | 2019-11-01T09:29:23 | Preferred: Deleted | The reference pointed to content (usually a resource) that has been deleted. |
| 1‑L | too-long | Content Too Long | IssueType | 2019-11-01T09:29:23 | Preferred: Content Too Long | Provided content is too long (typically, this is a denial of service protection type of error). |
| 1‑L | code-invalid | Invalid Code | IssueType | 2019-11-01T09:29:23 | Preferred: Invalid Code | The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code. |
| 1‑L | extension | Unacceptable Extension | IssueType | 2019-11-01T09:29:23 | Preferred: Unacceptable Extension | An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized. |
| 1‑L | too-costly | Operation Too Costly | IssueType | 2019-11-01T09:29:23 | Preferred: 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. |
| 1‑L | business-rule | Business Rule Violation | IssueType | 2019-11-01T09:29:23 | Preferred: Business Rule Violation | The content/operation failed to pass some business rule and so could not proceed. |
| 1‑L | conflict | Edit Version Conflict | IssueType | 2019-11-01T09:29:23 | Preferred: 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.). |
| 0‑S | transient | Transient Issue | IssueType | 2019-11-01T09:29:23 | Preferred: Transient Issue | Transient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved. |
| 1‑L | lock-error | Lock Error | IssueType | 2019-11-01T09:29:23 | Preferred: Lock Error | A resource/record locking failure (usually in an underlying database). |
| 1‑L | no-store | No Store Available | IssueType | 2019-11-01T09:29:23 | Preferred: 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. |
| 1‑L | exception | Exception | IssueType | 2019-11-01T09:29:23 | Preferred: Exception | An unexpected internal error has occurred. |
| 1‑L | timeout | Timeout | IssueType | 2019-11-01T09:29:23 | Preferred: Timeout | An internal timeout has occurred. |
| 1‑L | incomplete | Incomplete Results | IssueType | 2019-11-01T09:29:23 | Preferred: 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). |
| 1‑L | throttled | Throttled | IssueType | 2019-11-01T09:29:23 | Preferred: Throttled | The system is not prepared to handle this request due to load management. |
| 0‑L | informational | Informational Note | IssueType | 2019-11-01T09:29:23 | Preferred: 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.). |
