Struct BundleEntryResponse

pub struct BundleEntryResponse {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub status: String,
    pub status_ext: Option<FieldExtension>,
    pub location: Option<String>,
    pub location_ext: Option<FieldExtension>,
    pub etag: Option<String>,
    pub etag_ext: Option<FieldExtension>,
    pub last_modified: Option<Instant>,
    pub last_modified_ext: Option<FieldExtension>,
    pub outcome: Option<Resource>,
    pub outcome_ext: Option<FieldExtension>,
}

Sub-fields of the response field in BundleEntry

Fields

id: Option<String>

Unique id for inter-element referencing

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

extension: Vec<Extension>

Additional content defined by implementations

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

modifier_extension: Vec<Extension>

Extensions that cannot be ignored even if unrecognized

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

status: String

Status response code (text optional)

The status code returned by processing this entry. The status SHALL start with a 3 digit HTTP code (e.g. 404) and may contain the standard HTTP description associated with the status code.

status_ext: Option<FieldExtension>

Extension field.

location: Option<String>

The location (if the operation returns a location)

The location header created by processing this operation, populated if the operation returns a location.

location_ext: Option<FieldExtension>

Extension field.

etag: Option<String>

The Etag for the resource (if relevant)

The Etag for the resource, if the operation for the entry produced a versioned resource (see Resource Metadata and Versioning and Managing Resource Contention).

Etags match the Resource.meta.versionId. The ETag has to match the version id in the header if a resource is included.

etag_ext: Option<FieldExtension>

Extension field.

last_modified: Option<Instant>

Server’s date time modified

The date/time that the resource was modified on the server.

This has to match the same time in the meta header (meta.lastUpdated) if a resource is included.

last_modified_ext: Option<FieldExtension>

Extension field.

outcome: Option<Resource>

OperationOutcome with hints and warnings (for batch/transaction)

An OperationOutcome containing hints and warnings produced as part of processing this entry in a batch or transaction.

For a POST/PUT operation, this is the equivalent outcome that would be returned for prefer = operationoutcome - except that the resource is always returned whether or not the outcome is returned.

This outcome is not used for error responses in batch/transaction, only for hints and warnings. In a batch operation, the error will be in Bundle.entry.response, and for transaction, there will be a single OperationOutcome instead of a bundle in the case of an error.

outcome_ext: Option<FieldExtension>

Extension field.

Implementations

impl BundleEntryResponse

pub fn builder() -> BundleEntryResponseBuilder

Start building a new instance

Trait Implementations

impl Clone for BundleEntryResponse

fn clone(&self) -> BundleEntryResponse

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for BundleEntryResponse

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for BundleEntryResponse

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for BundleEntryResponse

fn eq(&self, other: &BundleEntryResponse) -> 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 BundleEntryResponse

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for BundleEntryResponse