Struct MedicationAdministrationInner

pub struct MedicationAdministrationInner {

    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 part_of: Vec<Option<Reference>>,
    pub part_of_ext: Vec<Option<FieldExtension>>,
    pub status: MedicationAdministrationStatusCodes,
    pub status_ext: Option<FieldExtension>,
    pub status_reason: Vec<Option<CodeableConcept>>,
    pub status_reason_ext: Vec<Option<FieldExtension>>,
    pub category: Vec<Option<CodeableConcept>>,
    pub category_ext: Vec<Option<FieldExtension>>,
    pub medication: CodeableReference,
    pub medication_ext: Option<FieldExtension>,
    pub subject: Reference,
    pub subject_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 occurence: MedicationAdministrationOccurence,
    pub occurence_ext: Option<MedicationAdministrationOccurenceExtension>,
    pub recorded: Option<DateTime>,
    pub recorded_ext: Option<FieldExtension>,
    pub is_sub_potent: Option<bool>,
    pub is_sub_potent_ext: Option<FieldExtension>,
    pub sub_potent_reason: Vec<Option<CodeableConcept>>,
    pub sub_potent_reason_ext: Vec<Option<FieldExtension>>,
    pub performer: Vec<Option<MedicationAdministrationPerformer>>,
    pub performer_ext: Vec<Option<FieldExtension>>,
    pub reason: Vec<Option<CodeableReference>>,
    pub reason_ext: Vec<Option<FieldExtension>>,
    pub request: Option<Reference>,
    pub request_ext: Option<FieldExtension>,
    pub device: Vec<Option<CodeableReference>>,
    pub device_ext: Vec<Option<FieldExtension>>,
    pub note: Vec<Option<Annotation>>,
    pub note_ext: Vec<Option<FieldExtension>>,
    pub dosage: Option<MedicationAdministrationDosage>,
    pub dosage_ext: Option<FieldExtension>,
    pub event_history: Vec<Option<Reference>>,
    pub event_history_ext: Vec<Option<FieldExtension>>,
    /* private fields */
}

Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner. This event can also be used to record waste using a status of not-done and the appropriate statusReason.

MedicationAdministration v5.0.0

Administration of medication to a patient

Describes the event of a patient consuming or otherwise being administered a medication. This may be as simple as swallowing a tablet or it may be a long running infusion. Related resources tie this event to the authorizing prescription, and the specific encounter between patient and health care practitioner.

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

External identifier

Identifiers associated with this Medication Administration that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate. They are business identifiers assigned to this resource by the performer or other systems and remain constant as the resource is updated and propagates from server to server.

This is a business identifier, not a resource identifier.

identifier_ext: Vec<Option<FieldExtension>>

Extension field.

based_on: Vec<Option<Reference>>

Plan this is fulfilled by this administration

A plan that is fulfilled in whole or in part by this MedicationAdministration.

based_on_ext: Vec<Option<FieldExtension>>

Extension field.

part_of: Vec<Option<Reference>>

Part of referenced event

A larger event of which this particular event is a component or step.

MedicationDispense will be used to indicate waste.

part_of_ext: Vec<Option<FieldExtension>>

Extension field.

status: MedicationAdministrationStatusCodes

MedicationAdministrationStatus; in-progress | not-done | on-hold | completed | entered-in-error | stopped | unknown

Will generally be set to show that the administration has been completed. For some long running administrations such as infusions, it is possible for an administration to be started but not completed or it may be paused while some other process is under way.

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: Vec<Option<CodeableConcept>>

MedicationAdministrationNegationReason; Reason administration not performed

A code indicating why the administration was not performed.

status_reason_ext: Vec<Option<FieldExtension>>

Extension field.

category: Vec<Option<CodeableConcept>>

MedicationAdministrationLocation; Type of medication administration

The type of medication administration (for example, drug classification like ATC, where meds would be administered, legal category of the medication).

category_ext: Vec<Option<FieldExtension>>

Extension field.

medication: CodeableReference

MedicationCode; What was administered

Identifies the medication that was administered. This is either a link to a resource representing the details of the medication or a simple attribute carrying a code that identifies the medication from a known list of medications.

If only a code is specified, then it needs to be a code for a specific product. If more information is required, then the use of the medication resource is recommended. For example, if you require form or lot number, then you must reference the Medication resource.

medication_ext: Option<FieldExtension>

Extension field.

subject: Reference

Who received medication

The person or animal or group receiving the medication.

subject_ext: Option<FieldExtension>

Extension field.

encounter: Option<Reference>

Encounter administered as part of

The visit, admission, or other contact between patient and health care provider during which the medication administration was performed.

encounter_ext: Option<FieldExtension>

Extension field.

supporting_information: Vec<Option<Reference>>

Additional information to support administration

Additional information (for example, patient height and weight) that supports the administration of the medication. This attribute can be used to provide documentation of specific characteristics of the patient present at the time of administration. For example, if the dose says “give “x” if the heartrate exceeds “y”“, then the heart rate can be included using this attribute.

supporting_information_ext: Vec<Option<FieldExtension>>

Extension field.

occurence: MedicationAdministrationOccurence

Specific date/time or interval of time during which the administration took place (or did not take place)

A specific date/time or interval of time during which the administration took place (or did not take place). For many administrations, such as swallowing a tablet the use of dateTime is more appropriate.

occurence_ext: Option<MedicationAdministrationOccurenceExtension>

Extension field.

recorded: Option<DateTime>

When the MedicationAdministration was first captured in the subject’s record

The date the occurrence of the MedicationAdministration was first captured in the record - potentially significantly after the occurrence of the event.

recorded_ext: Option<FieldExtension>

Extension field.

is_sub_potent: Option<bool>

Full dose was not administered

An indication that the full dose was not administered.

is_sub_potent_ext: Option<FieldExtension>

Extension field.

sub_potent_reason: Vec<Option<CodeableConcept>>

MedicationAdministrationSubPotentReason; Reason full dose was not administered

The reason or reasons why the full dose was not administered.

sub_potent_reason_ext: Vec<Option<FieldExtension>>

Extension field.

performer: Vec<Option<MedicationAdministrationPerformer>>

Who or what performed the medication administration and what type of performance they did

The performer of the medication treatment. For devices this is the device that performed the administration of the medication. An IV Pump would be an example of a device that is performing the administration. Both the IV Pump and the practitioner that set the rate or bolus on the pump can be listed as performers.

performer_ext: Vec<Option<FieldExtension>>

Extension field.

reason: Vec<Option<CodeableReference>>

MedicationAdministrationReason; Concept, condition or observation that supports why the medication was administered

A code, Condition or observation that supports why the medication was administered.

reason_ext: Vec<Option<FieldExtension>>

Extension field.

request: Option<Reference>

Request administration performed against

The original request, instruction or authority to perform the administration.

This is a reference to the MedicationRequest where the intent is either order or instance-order. It should not reference MedicationRequests where the intent is any other value.

request_ext: Option<FieldExtension>

Extension field.

device: Vec<Option<CodeableReference>>

Device used to administer

The device that is to be used for the administration of the medication (for example, PCA Pump).

device_ext: Vec<Option<FieldExtension>>

Extension field.

note: Vec<Option<Annotation>>

Information about the administration

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

note_ext: Vec<Option<FieldExtension>>

Extension field.

dosage: Option<MedicationAdministrationDosage>

Details of how medication was taken

Describes the medication dosage information details e.g. dose, rate, site, route, etc.

dosage_ext: Option<FieldExtension>

Extension field.

event_history: Vec<Option<Reference>>

A list of events of interest in the lifecycle

A summary of the events of interest that have occurred, such as when the administration was verified.

This might not include provenances for all versions of the request – only those deemed “relevant” or important. This SHALL NOT include the Provenance associated with this current version of the resource. (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update. Until then, it can be queried directly as the Provenance that points to this version using _revinclude All Provenances should have some historical version of this Request as their subject.

event_history_ext: Vec<Option<FieldExtension>>

Extension field.

Trait Implementations

impl Clone for MedicationAdministrationInner

fn clone(&self) -> MedicationAdministrationInner

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MedicationAdministrationInner

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MedicationAdministrationInner

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl From<MedicationAdministrationInner> for MedicationAdministration

fn from(inner: MedicationAdministrationInner) -> MedicationAdministration

Converts to this type from the input type.

impl PartialEq for MedicationAdministrationInner

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

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 MedicationAdministrationInner