IssueType

Issue Type

activeExtensions for Using Data Elements from FHIR R5 in FHIR R40.1.0complete33 concepts

A code that describes the type of issue.

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/fhir/issue-type
ID
issue-type
Version
5.0.0
Publisher
FHIR Infrastructure
Case Sensitive
Yes
Hierarchy
is-a

Concepts (33)

CodeDisplayDefinition
invalidInvalid ContentContent invalid against the specification or a profile.
└structureStructural IssueA structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc.
└requiredRequired element missingA required element is missing.
└valueElement value invalidAn element or header value is invalid.
└invariantValidation rule failedA content validation rule failed - e.g. a schematron rule.
securitySecurity ProblemAn authentication/authorization/permissions issue of some kind.
└loginLogin RequiredThe client needs to initiate an authentication process.
└unknownUnknown UserThe user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).
└expiredSession ExpiredUser session expired; a login may be required.
└forbiddenForbiddenThe user does not have the rights to perform this action.
└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.
processingProcessing FailureProcessing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.
└not-supportedContent not supportedThe interaction, operation, resource or profile is not supported.
└duplicateDuplicateAn attempt was made to create a duplicate record.
└multiple-matchesMultiple MatchesMultiple matching records were found when the operation required only one match.
└not-foundNot FoundThe 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.
└deletedDeletedThe reference pointed to content (usually a resource) that has been deleted.
└too-longContent Too LongProvided content is too long (typically, this is a denial of service protection type of error).
└code-invalidInvalid CodeThe code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.
└extensionUnacceptable ExtensionAn extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.
└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.
└business-ruleBusiness Rule ViolationThe content/operation failed to pass some business rule and so could not proceed.
└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.).
└limited-filterLimited Filter ApplicationSome 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`.
transientTransient IssueTransient processing issues. The system receiving the message may be able to resubmit the same content once an underlying issue is resolved.
└lock-errorLock ErrorA resource/record locking failure (usually in an underlying database).
└no-storeNo Store AvailableThe persistent store is unavailable; e.g. the database is down for maintenance or similar action, and the interaction or operation cannot be processed.
└exceptionExceptionAn unexpected internal error has occurred.
└timeoutTimeoutAn internal timeout 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).
└throttledThrottledThe system is not prepared to handle this request due to load management.
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.).
successOperation SuccessfulThe operation completed successfully.