FHIR Cross-Version Extensions package for FHIR R5 from FHIR R2 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/1.0/ValueSet/R2-issue-type-for-R5 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 0 | Computable Name: R2_issue_type_for_R5 | ||
| This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/issue-type | 1.0.2 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R2 to R5. |
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/issue-type version 1.0.2| Code | Display | Definition |
| unknown | Unknown User | The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable). |
| required | Required element missing | A required element is missing. |
| invariant | Validation rule failed | A content validation rule failed - e.g. a schematron rule. |
| invalid | Invalid Content | Content invalid against the specification or a profile. |
| login | Login Required | The client needs to initiate an authentication process. |
| expired | Session Expired | User session expired; a login may be required. |
| suppressed | 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. |
| not-supported | Content not supported | The interaction, operation, resource or profile is not supported. |
| code-invalid | Invalid Code | The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code. |
| too-costly | 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. |
| conflict | 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.). |
| incomplete | 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). |
| lock-error | Lock Error | A resource/record locking failure (usually in an underlying database). |
| exception | Exception | An unexpected internal error has occurred. |
| informational | 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.). |
This value set expansion contains 15 concepts.
| Code | System | Display | Definition |
| 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). |
| required | http://hl7.org/fhir/issue-type | Required element missing | A required element is missing. |
| invariant | http://hl7.org/fhir/issue-type | Validation rule failed | A content validation rule failed - e.g. a schematron rule. |
| invalid | http://hl7.org/fhir/issue-type | Invalid Content | Content invalid against the specification or a profile. |
| login | http://hl7.org/fhir/issue-type | Login Required | The client needs to initiate an authentication process. |
| expired | http://hl7.org/fhir/issue-type | Session Expired | User session expired; a login may be required. |
| 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. |
| not-supported | http://hl7.org/fhir/issue-type | Content not supported | The interaction, operation, resource or profile is not supported. |
| 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. |
| 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. |
| 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.). |
| 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). |
| lock-error | http://hl7.org/fhir/issue-type | Lock Error | A resource/record locking failure (usually in an underlying database). |
| exception | http://hl7.org/fhir/issue-type | Exception | An unexpected internal error has occurred. |
| 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.). |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | 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) |
| 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 |