Enum IssueType

pub enum IssueType {
    BusinessRule,
    CodeInvalid,
    Conflict,
    Deleted,
    Duplicate,
    Exception,
    Expired,
    Extension,
    Forbidden,
    Incomplete,
    Informational,
    Invalid,
    Invariant,
    LimitedFilter,
    LockError,
    Login,
    MultipleMatches,
    NoStore,
    NotFound,
    NotSupported,
    Processing,
    Required,
    Security,
    Structure,
    Success,
    Suppressed,
    Throttled,
    Timeout,
    TooCostly,
    TooLong,
    Transient,
    Unknown,
    Value,
}

IssueType. A code that describes the type of issue.

FHIR version: 5.0.0.

Variants

BusinessRule

business-rule

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

CodeInvalid

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.

Conflict

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

Deleted

deleted

Deleted. The reference pointed to content (usually a resource) that has been deleted.

Duplicate

duplicate

Duplicate. An attempt was made to create a duplicate record.

Exception

exception

Exception. An unexpected internal error has occurred.

Expired

expired

Session Expired. User session expired; a login may be required.

Extension

extension

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

Forbidden

forbidden

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

Incomplete

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

Informational

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

Invalid

invalid

Invalid Content. Content invalid against the specification or a profile.

Invariant

invariant

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

LimitedFilter

limited-filter

Limited Filter Application. Some 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.

LockError

lock-error

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

Login

login

Login Required. The client needs to initiate an authentication process.

MultipleMatches

multiple-matches

Multiple Matches. Multiple matching records were found when the operation required only one match.

NoStore

no-store

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.

NotFound

not-found

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.

NotSupported

not-supported

Content not supported. The interaction, operation, resource or profile is not supported.

Processing

processing

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

Required

required

Required element missing. A required element is missing.

Security

security

Security Problem. An authentication/authorization/permissions issue of some kind.

Structure

structure

Structural Issue. A structural issue in the content such as wrong namespace, unable to parse the content completely, invalid syntax, etc.

Success

success

Operation Successful. The operation completed successfully.

Suppressed

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.

Throttled

throttled

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

Timeout

timeout

Timeout. An internal timeout has occurred.

TooCostly

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.

TooLong

too-long

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

Transient

transient

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

Unknown

unknown

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

Value

value

Element value invalid. An element or header value is invalid.

Trait Implementations

impl AsRef<str> for IssueType

fn as_ref(&self) -> &str

Converts this type into a shared reference of the (usually inferred) input type.

impl Clone for IssueType

fn clone(&self) -> IssueType

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for IssueType

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for IssueType

fn deserialize<D>( deserializer: D, ) -> Result<IssueType, <D as Deserializer<'de>>::Error>

where D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Display for IssueType

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl From<IssueType> for CodeableConcept

fn from(code: IssueType) -> CodeableConcept

Converts to this type from the input type.

impl From<IssueType> for Coding

fn from(code: IssueType) -> Coding

Converts to this type from the input type.

impl FromStr for IssueType

type Err = String

The associated error which can be returned from parsing.

fn from_str(s: &str) -> Result<IssueType, <IssueType as FromStr>::Err>

Parses a string s to return a value of this type.

impl Hash for IssueType

fn hash<__H>(&self, state: &mut __H)

where __H: Hasher,

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for IssueType

fn eq(&self, other: &IssueType) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for IssueType

fn serialize<S>( &self, serializer: S, ) -> Result<<S as Serializer>::Ok, <S as Serializer>::Error>

where S: Serializer,

Serialize this value into the given Serde serializer.

impl Copy for IssueType

impl Eq for IssueType

impl StructuralPartialEq for IssueType