Struct ImmunizationInner

pub struct ImmunizationInner {

    pub id: Option<String>,
    pub meta: Option<Meta>,
    pub implicit_rules: Option<String>,
    pub language: Option<String>,
    pub text: Option<Narrative>,
    pub contained: Vec<Resource>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub identifier: Vec<Option<Identifier>>,
    pub identifier_ext: Vec<Option<FieldExtension>>,
    pub based_on: Vec<Option<Reference>>,
    pub based_on_ext: Vec<Option<FieldExtension>>,
    pub status: String,
    pub status_ext: Option<FieldExtension>,
    pub status_reason: Option<CodeableConcept>,
    pub status_reason_ext: Option<FieldExtension>,
    pub vaccine_code: CodeableConcept,
    pub vaccine_code_ext: Option<FieldExtension>,
    pub administered_product: Option<CodeableReference>,
    pub administered_product_ext: Option<FieldExtension>,
    pub manufacturer: Option<CodeableReference>,
    pub manufacturer_ext: Option<FieldExtension>,
    pub lot_number: Option<String>,
    pub lot_number_ext: Option<FieldExtension>,
    pub expiration_date: Option<Date>,
    pub expiration_date_ext: Option<FieldExtension>,
    pub patient: Reference,
    pub patient_ext: Option<FieldExtension>,
    pub encounter: Option<Reference>,
    pub encounter_ext: Option<FieldExtension>,
    pub supporting_information: Vec<Option<Reference>>,
    pub supporting_information_ext: Vec<Option<FieldExtension>>,
    pub occurrence: ImmunizationOccurrence,
    pub occurrence_ext: Option<ImmunizationOccurrenceExtension>,
    pub primary_source: Option<bool>,
    pub primary_source_ext: Option<FieldExtension>,
    pub information_source: Option<CodeableReference>,
    pub information_source_ext: Option<FieldExtension>,
    pub location: Option<Reference>,
    pub location_ext: Option<FieldExtension>,
    pub site: Option<CodeableConcept>,
    pub site_ext: Option<FieldExtension>,
    pub route: Option<CodeableConcept>,
    pub route_ext: Option<FieldExtension>,
    pub dose_quantity: Option<Quantity>,
    pub dose_quantity_ext: Option<FieldExtension>,
    pub performer: Vec<Option<ImmunizationPerformer>>,
    pub performer_ext: Vec<Option<FieldExtension>>,
    pub note: Vec<Option<Annotation>>,
    pub note_ext: Vec<Option<FieldExtension>>,
    pub reason: Vec<Option<CodeableReference>>,
    pub reason_ext: Vec<Option<FieldExtension>>,
    pub is_subpotent: Option<bool>,
    pub is_subpotent_ext: Option<FieldExtension>,
    pub subpotent_reason: Vec<Option<CodeableConcept>>,
    pub subpotent_reason_ext: Vec<Option<FieldExtension>>,
    pub program_eligibility: Vec<Option<ImmunizationProgramEligibility>>,
    pub program_eligibility_ext: Vec<Option<FieldExtension>>,
    pub funding_source: Option<CodeableConcept>,
    pub funding_source_ext: Option<FieldExtension>,
    pub reaction: Vec<Option<ImmunizationReaction>>,
    pub reaction_ext: Vec<Option<FieldExtension>>,
    pub protocol_applied: Vec<Option<ImmunizationProtocolApplied>>,
    pub protocol_applied_ext: Vec<Option<FieldExtension>>,
    /* private fields */
}

Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.

Immunization v5.0.0

Immunization event information

Describes the event of a patient being administered a vaccine or a record of an immunization as reported by a patient, a clinician or another party.

Fields

id: Option<String>

Logical id of this artifact

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

meta: Option<Meta>

Metadata about the resource

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

implicit_rules: Option<String>

A set of rules under which this content was created

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

language: Option<String>

Language; Language of the resource content

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

text: Option<Narrative>

Text summary of the resource, for human interpretation

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it “clinically safe” for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.

contained: Vec<Resource>

Contained, inline Resources

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

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

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 is allowed to 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.

identifier: Vec<Option<Identifier>>

Business identifier

A unique identifier assigned to this immunization record.

identifier_ext: Vec<Option<FieldExtension>>

Extension field.

based_on: Vec<Option<Reference>>

Authority that the immunization event is based on

A plan, order or recommendation fulfilled in whole or in part by this immunization.

Allows tracing of an authorization for the Immunization.

based_on_ext: Vec<Option<FieldExtension>>

Extension field.

status: String

ImmunizationStatus; completed | entered-in-error | not-done

Indicates the current status of the immunization event.

Will generally be set to show that the immunization has been completed or not done. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

status_ext: Option<FieldExtension>

Extension field.

status_reason: Option<CodeableConcept>

ImmunizationStatusReason; Reason for current status

Indicates the reason the immunization event was not performed.

This is generally only used for the status of “not-done”. The reason for performing the immunization event is captured in reasonCode, not here.

status_reason_ext: Option<FieldExtension>

Extension field.

vaccine_code: CodeableConcept

VaccineCode; Vaccine administered

Vaccine that was administered or was to be administered.

The code for the administered vaccine may be reported at various levels of granularity from a very generic code for a general type of vaccine (e.g. the SNOMED or CVX code for the flu vaccine) to a very discrete code for a specific product including the form and packaging (e.g. an NDC code). Because vaccineCode uses the CodeableConcept data type, multiple codes at different levels of granularity may be reported for a single immunization event provided that all codes are appropriate for the same vaccine. For example, both NDC and CVX codes may be provided for a given immunization event by repeating the coding element within vaccineCode.

vaccine_code_ext: Option<FieldExtension>

Extension field.

administered_product: Option<CodeableReference>

Product that was administered

An indication of which product was administered to the patient. This is typically a more detailed representation of the concept conveyed by the vaccineCode data element. If a Medication resource is referenced, it may be to a stand-alone resource or a contained resource within the Immunization resource.

administered_product_ext: Option<FieldExtension>

Extension field.

manufacturer: Option<CodeableReference>

Vaccine manufacturer

Name of vaccine manufacturer.

manufacturer_ext: Option<FieldExtension>

Extension field.

lot_number: Option<String>

Vaccine lot number

Lot number of the vaccine product.

lot_number_ext: Option<FieldExtension>

Extension field.

expiration_date: Option<Date>

Vaccine expiration date

Date vaccine batch expires.

expiration_date_ext: Option<FieldExtension>

Extension field.

patient: Reference

Who was immunized

The patient who either received or did not receive the immunization.

patient_ext: Option<FieldExtension>

Extension field.

encounter: Option<Reference>

Encounter immunization was part of

The visit or admission or other contact between patient and health care provider the immunization was performed as part of.

encounter_ext: Option<FieldExtension>

Extension field.

supporting_information: Vec<Option<Reference>>

Additional information in support of the immunization

Additional information that is relevant to the immunization (e.g. for a vaccine recipient who is pregnant, the gestational age of the fetus). The reason why a vaccine was given (e.g. occupation, underlying medical condition) should be conveyed in Immunization.reason, not as supporting information. The reason why a vaccine was not given (e.g. contraindication) should be conveyed in Immunization.statusReason, not as supporting information.

supporting_information_ext: Vec<Option<FieldExtension>>

Extension field.

occurrence: ImmunizationOccurrence

Vaccine administration date

Date vaccine administered or was to be administered.

When immunizations are given a specific date and time should always be known. When immunizations are patient reported, a specific date might not be known. Although partial dates are allowed, an adult patient might not be able to recall the year a childhood immunization was given. An exact date is always preferable, but the use of the String data type is acceptable when an exact date is not known. A small number of vaccines (e.g. live oral typhoid vaccine) are given as a series of patient self-administered dose over a span of time. In cases like this, often, only the first dose (typically a provider supervised dose) is recorded with the occurrence indicating the date/time of the first dose.

occurrence_ext: Option<ImmunizationOccurrenceExtension>

Extension field.

primary_source: Option<bool>

Indicates context the data was captured in

Indicates whether the data contained in the resource was captured by the individual/organization which was responsible for the administration of the vaccine rather than as ‘secondary reported’ data documented by a third party. A value of ‘true’ means this data originated with the individual/organization which was responsible for the administration of the vaccine.

Reflects the “reliability” of the content.

primary_source_ext: Option<FieldExtension>

Extension field.

information_source: Option<CodeableReference>

ImmunizationReportOrigin; Indicates the source of a reported record

Typically the source of the data when the report of the immunization event is not based on information from the person who administered the vaccine.

Typically will not be populated if primarySource = True, not required even if primarySource = False.

information_source_ext: Option<FieldExtension>

Extension field.

location: Option<Reference>

Where immunization occurred

The service delivery location where the vaccine administration occurred.

location_ext: Option<FieldExtension>

Extension field.

site: Option<CodeableConcept>

ImmunizationSite; Body site vaccine was administered

Body site where vaccine was administered.

site_ext: Option<FieldExtension>

Extension field.

route: Option<CodeableConcept>

ImmunizationRoute; How vaccine entered body

The path by which the vaccine product is taken into the body.

route_ext: Option<FieldExtension>

Extension field.

dose_quantity: Option<Quantity>

Amount of vaccine administered

The quantity of vaccine product that was administered.

dose_quantity_ext: Option<FieldExtension>

Extension field.

performer: Vec<Option<ImmunizationPerformer>>

Who performed event

Indicates who performed the immunization event.

performer_ext: Vec<Option<FieldExtension>>

Extension field.

note: Vec<Option<Annotation>>

Additional immunization notes

Extra information about the immunization that is not conveyed by the other attributes.

note_ext: Vec<Option<FieldExtension>>

Extension field.

reason: Vec<Option<CodeableReference>>

ImmunizationReason; Why immunization occurred

Describes why the immunization occurred in coded or textual form, or Indicates another resource (Condition, Observation or DiagnosticReport) whose existence justifies this immunization.

reason_ext: Vec<Option<FieldExtension>>

Extension field.

is_subpotent: Option<bool>

Dose potency

Indication if a dose is considered to be subpotent. By default, a dose should be considered to be potent.

Typically, the recognition of the dose being sub-potent is retrospective, after the administration (ex. notification of a manufacturer recall after administration). However, in the case of a partial administration (the patient moves unexpectedly and only some of the dose is actually administered), subpotency may be recognized immediately, but it is still important to record the event.

is_subpotent_ext: Option<FieldExtension>

Extension field.

subpotent_reason: Vec<Option<CodeableConcept>>

SubpotentReason; Reason for being subpotent

Reason why a dose is considered to be subpotent.

subpotent_reason_ext: Vec<Option<FieldExtension>>

Extension field.

program_eligibility: Vec<Option<ImmunizationProgramEligibility>>

Patient eligibility for a specific vaccination program

Indicates a patient’s eligibility for a funding program.

program_eligibility_ext: Vec<Option<FieldExtension>>

Extension field.

funding_source: Option<CodeableConcept>

FundingSource; Funding source for the vaccine

Indicates the source of the vaccine actually administered. This may be different than the patient eligibility (e.g. the patient may be eligible for a publically purchased vaccine but due to inventory issues, vaccine purchased with private funds was actually administered).

funding_source_ext: Option<FieldExtension>

Extension field.

reaction: Vec<Option<ImmunizationReaction>>

Details of a reaction that follows immunization

Categorical data indicating that an adverse event is associated in time to an immunization.

A reaction may be an indication of an allergy or intolerance and, if this is determined to be the case, it should be recorded as a new AllergyIntolerance resource instance as most systems will not query against past Immunization.reaction elements.

reaction_ext: Vec<Option<FieldExtension>>

Extension field.

protocol_applied: Vec<Option<ImmunizationProtocolApplied>>

Protocol followed by the provider

The protocol (set of recommendations) being followed by the provider who administered the dose.

protocol_applied_ext: Vec<Option<FieldExtension>>

Extension field.

Trait Implementations

impl Clone for ImmunizationInner

fn clone(&self) -> ImmunizationInner

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ImmunizationInner

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for ImmunizationInner

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<ImmunizationInner> for Immunization

fn from(inner: ImmunizationInner) -> Immunization

Converts to this type from the input type.

impl PartialEq for ImmunizationInner

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

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 ImmunizationInner