IssueType

Content invalid against the specification or a profile.

A structural issue in the content such as wrong namespace, or unable to parse the content completely, or invalid json syntax.

A required element is missing.

An element value is invalid.

A content validation rule failed - e.g. a schematron rule.

An authentication/authorization/permissions issue of some kind.

The client needs to initiate an authentication process.

The user or system was not able to be authenticated (either there is no process, or the proferred token is unacceptable).

User session expired; a login may be required.

The user does not have the rights to perform this action.

Some information was not or may not have been returned due to business rules, consent or privacy rules, or access permission constraints. This information may be accessible through alternate processes.

Processing issues. These are expected to be final e.g. there is no point resubmitting the same content unchanged.

The resource or profile is not supported.

An attempt was made to create a duplicate record.

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.

Provided content is too long (typically, this is a denial of service protection type of error).

The code or system could not be understood, or it was not valid in the context of a particular ValueSet.code.

An extension was found that was not acceptable, could not be resolved, or a modifierExtension was not recognized.

The operation was stopped to protect server resources; e.g. a request for a value set expansion on all of SNOMED CT.

The content/operation failed to pass some business rule, and so could not proceed.

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 404 error, but this code may be used where the conflict is discovered further into the application architecture.)

Not all data sources typically accessed could be reached, or responded in time, so the returned information may not be complete.

Transient processing issues. The system receiving the error may be able to resubmit the same content once an underlying issue is resolved.

A resource/record locking failure (usually in an underlying database).

The persistent store is unavailable; e.g. the database is down for maintenance or similar action.

An unexpected internal error has occurred.

An internal timeout has occurred.

The system is not prepared to handle this request due to load management.

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.).