Struct AttachmentInner 

pub struct AttachmentInner {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub content_type: Option<String>,
    pub content_type_ext: Option<FieldExtension>,
    pub language: Option<String>,
    pub language_ext: Option<FieldExtension>,
    pub data: Option<Base64Binary>,
    pub data_ext: Option<FieldExtension>,
    pub url: Option<String>,
    pub url_ext: Option<FieldExtension>,
    pub size: Option<Integer64>,
    pub size_ext: Option<FieldExtension>,
    pub hash: Option<Base64Binary>,
    pub hash_ext: Option<FieldExtension>,
    pub title: Option<String>,
    pub title_ext: Option<FieldExtension>,
    pub creation: Option<DateTime>,
    pub creation_ext: Option<FieldExtension>,
    pub height: Option<NonZero<u32>>,
    pub height_ext: Option<FieldExtension>,
    pub width: Option<NonZero<u32>>,
    pub width_ext: Option<FieldExtension>,
    pub frames: Option<NonZero<u32>>,
    pub frames_ext: Option<FieldExtension>,
    pub duration: Option<f64>,
    pub duration_ext: Option<FieldExtension>,
    pub pages: Option<NonZero<u32>>,
    pub pages_ext: Option<FieldExtension>,
}

Attachment Type: For referring to data content defined in other formats.

Attachment v5.0.0

Content in a format defined elsewhere

For referring to data content defined in other formats.

When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as “Signed Procedure Consent”.

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.

content_type: Option<String>

MimeType; Mime type of the content, with charset etc.

Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.

content_type_ext: Option<FieldExtension>

Extension field.

language: Option<String>

Language; Human language of the content (BCP-47)

The human language of the content. The value can be any valid value according to BCP 47.

language_ext: Option<FieldExtension>

Extension field.

data: Option<Base64Binary>

Data inline, base64ed

The actual data of the attachment - a sequence of bytes, base64 encoded.

The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.

data_ext: Option<FieldExtension>

Extension field.

url: Option<String>

Uri where the data can be found

A location where the data can be accessed.

If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.

url_ext: Option<FieldExtension>

Extension field.

size: Option<Integer64>

Number of bytes of content (if url provided)

The number of bytes of data that make up this attachment (before base64 encoding, if that is done).

The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.

size_ext: Option<FieldExtension>

Extension field.

hash: Option<Base64Binary>

Hash of the data (sha-1, base64ed)

The calculated hash of the data using SHA-1. Represented using base64.

The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature.

hash_ext: Option<FieldExtension>

Extension field.

title: Option<String>

Label to display in place of the data

A label or set of text to display in place of the data.

May sometimes be derived from the source filename.

title_ext: Option<FieldExtension>

Extension field.

creation: Option<DateTime>

Date attachment was first created

The date that the attachment was first created.

creation_ext: Option<FieldExtension>

Extension field.

height: Option<NonZero<u32>>

Height of the image in pixels (photo/video)

Height of the image in pixels (photo/video).

height_ext: Option<FieldExtension>

Extension field.

width: Option<NonZero<u32>>

Width of the image in pixels (photo/video)

Width of the image in pixels (photo/video).

width_ext: Option<FieldExtension>

Extension field.

frames: Option<NonZero<u32>>

Number of frames if > 1 (photo)

The number of frames in a photo. This is used with a multi-page fax, or an imaging acquisition context that takes multiple slices in a single image, or an animated gif. If there is more than one frame, this SHALL have a value in order to alert interface software that a multi-frame capable rendering widget is required.

if the number of frames is not supplied, the value may be unknown. Applications should not assume that there is only one frame unless it is explicitly stated.

frames_ext: Option<FieldExtension>

Extension field.

duration: Option<f64>

Length in seconds (audio / video)

The duration of the recording in seconds - for audio and video.

The duration might differ from occurrencePeriod if recording was paused.

duration_ext: Option<FieldExtension>

Extension field.

pages: Option<NonZero<u32>>

Number of printed pages

The number of pages when printed.

pages_ext: Option<FieldExtension>

Extension field.

Trait Implementations

impl Clone for AttachmentInner

fn clone(&self) -> AttachmentInner

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for AttachmentInner

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for AttachmentInner

fn deserialize<__D>( __deserializer: __D, ) -> Result<AttachmentInner, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<AttachmentInner> for Attachment

fn from(inner: AttachmentInner) -> Attachment

Converts to this type from the input type.

impl PartialEq for AttachmentInner

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

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 StructuralPartialEq for AttachmentInner