FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R4.IssueType for use in FHIR R5

Official URL: http://hl7.org/fhir/4.0/ValueSet/R4-issue-type-for-R5 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 5 Computable Name: R4_issue_type_for_R5

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/issue-type 4.0.1 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R4 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)

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/issue-type version 4.0.1
    CodeDisplayDefinition
    invalidInvalid ContentContent invalid against the specification or a profile.
    requiredRequired element missingA required element is missing.
    invariantValidation rule failedA content validation rule failed - e.g. a schematron rule.
    loginLogin RequiredThe client needs to initiate an authentication process.
    expiredSession ExpiredUser session expired; a login may be required.
    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.
    not-supportedContent not supportedThe interaction, operation, resource or profile is not supported.
    multiple-matchesMultiple MatchesMultiple matching records were found when the operation required only one match.
    deletedDeletedThe reference pointed to content (usually a resource) that has been deleted.
    code-invalidInvalid CodeThe code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.
    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.
    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.).
    lock-errorLock ErrorA resource/record locking failure (usually in an underlying database).
    exceptionExceptionAn unexpected internal error has occurred.
    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).
    informationalInformational 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.).
    unknownUnknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).

 

Expansion

This value set expansion contains 17 concepts.

CodeSystemDisplayDefinition
  invalidhttp://hl7.org/fhir/issue-typeInvalid ContentContent invalid against the specification or a profile.
  requiredhttp://hl7.org/fhir/issue-typeRequired element missingA required element is missing.
  invarianthttp://hl7.org/fhir/issue-typeValidation rule failedA content validation rule failed - e.g. a schematron rule.
  loginhttp://hl7.org/fhir/issue-typeLogin RequiredThe client needs to initiate an authentication process.
  expiredhttp://hl7.org/fhir/issue-typeSession ExpiredUser session expired; a login may be required.
  suppressedhttp://hl7.org/fhir/issue-typeInformation 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.
  not-supportedhttp://hl7.org/fhir/issue-typeContent not supportedThe interaction, operation, resource or profile is not supported.
  multiple-matcheshttp://hl7.org/fhir/issue-typeMultiple MatchesMultiple matching records were found when the operation required only one match.
  deletedhttp://hl7.org/fhir/issue-typeDeletedThe reference pointed to content (usually a resource) that has been deleted.
  code-invalidhttp://hl7.org/fhir/issue-typeInvalid CodeThe code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.
  too-costlyhttp://hl7.org/fhir/issue-typeOperation Too CostlyThe operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT.
  conflicthttp://hl7.org/fhir/issue-typeEdit 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.).
  lock-errorhttp://hl7.org/fhir/issue-typeLock ErrorA resource/record locking failure (usually in an underlying database).
  exceptionhttp://hl7.org/fhir/issue-typeExceptionAn unexpected internal error has occurred.
  incompletehttp://hl7.org/fhir/issue-typeIncomplete 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).
  informationalhttp://hl7.org/fhir/issue-typeInformational 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.).
  unknownhttp://hl7.org/fhir/issue-typeUnknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).

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