Struct MedicationStatement 

pub struct MedicationStatement {

    pub id: Option<String>,
    pub meta: Option<Box<Meta>>,
    pub implicitRules: Option<Box<FHIRUri>>,
    pub language: Option<Box<FHIRCode>>,
    pub text: Option<Box<Narrative>>,
    pub contained: Option<Vec<Box<Resource>>>,
    pub extension: Option<Vec<Box<Extension>>>,
    pub modifierExtension: Option<Vec<Box<Extension>>>,
    pub identifier_: Option<Vec<Box<Identifier>>>,
    pub basedOn: Option<Vec<Box<Reference>>>,
    pub partOf: Option<Vec<Box<Reference>>>,
    pub status: Box<MedicationStatementStatus>,
    pub statusReason: Option<Vec<Box<CodeableConcept>>>,
    pub category: Option<Box<CodeableConcept>>,
    pub medication: MedicationStatementMedicationTypeChoice,
    pub subject: Box<Reference>,
    pub context: Option<Box<Reference>>,
    pub effective: Option<MedicationStatementEffectiveTypeChoice>,
    pub dateAsserted: Option<Box<FHIRDateTime>>,
    pub informationSource: Option<Box<Reference>>,
    pub derivedFrom: Option<Vec<Box<Reference>>>,
    pub reasonCode: Option<Vec<Box<CodeableConcept>>>,
    pub reasonReference: Option<Vec<Box<Reference>>>,
    pub note: Option<Vec<Box<Annotation>>>,
    pub dosage: Option<Vec<Box<Dosage>>>,
}

A record of a medication that is being consumed by a patient. A MedicationStatement may indicate that the patient may be taking the medication now or has taken the medication in the past or will be taking the medication in the future. The source of this information can be the patient, significant other (such as a family member or spouse), or a clinician. A common scenario where this information is captured is during the history taking process during a patient visit or stay. The medication information may come from sources such as the patient’s memory, from a prescription bottle, or from a list of medications the patient, clinician or other party maintains.

The primary difference between a medication statement and a medication administration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medication statement is often, if not always, less specific. There is no required date/time when the medication was administered, in fact we only know that a source has reported the patient is taking this medication, where details such as time, quantity, or rate or even medication product may be incomplete or missing or less precise. As stated earlier, the medication statement information may come from the patient’s memory, from a prescription bottle or from a list of medications the patient, clinician or other party maintains. Medication administration is more formal and is not missing detailed information.

Fields

id: Option<String>

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

meta: Option<Box<Meta>>

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.

implicitRules: Option<Box<FHIRUri>>

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.

language: Option<Box<FHIRCode>>

The base language in which the resource is written.

text: Option<Box<Narrative>>

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: Option<Vec<Box<Resource>>>

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

extension: Option<Vec<Box<Extension>>>

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 manageable, 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.

modifierExtension: Option<Vec<Box<Extension>>>

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

identifier_: Option<Vec<Box<Identifier>>>

Identifiers associated with this Medication Statement 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.

basedOn: Option<Vec<Box<Reference>>>

A plan, proposal or order that is fulfilled in whole or in part by this event.

partOf: Option<Vec<Box<Reference>>>

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

status: Box<MedicationStatementStatus>

A code representing the patient or other source’s judgment about the state of the medication used that this statement is about. Generally, this will be active or completed.

statusReason: Option<Vec<Box<CodeableConcept>>>

Captures the reason for the current state of the MedicationStatement.

category: Option<Box<CodeableConcept>>

Indicates where the medication is expected to be consumed or administered.

medication: MedicationStatementMedicationTypeChoice

Identifies the medication being 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.

subject: Box<Reference>

The person, animal or group who is/was taking the medication.

context: Option<Box<Reference>>

The encounter or episode of care that establishes the context for this MedicationStatement.

effective: Option<MedicationStatementEffectiveTypeChoice>

The interval of time during which it is being asserted that the patient is/was/will be taking the medication (or was not taking, when the MedicationStatement.taken element is No).

dateAsserted: Option<Box<FHIRDateTime>>

The date when the medication statement was asserted by the information source.

informationSource: Option<Box<Reference>>

The person or organization that provided the information about the taking of this medication. Note: Use derivedFrom when a MedicationStatement is derived from other resources, e.g. Claim or MedicationRequest.

derivedFrom: Option<Vec<Box<Reference>>>

Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement.

reasonCode: Option<Vec<Box<CodeableConcept>>>

A reason for why the medication is being/was taken.

reasonReference: Option<Vec<Box<Reference>>>

Condition or observation that supports why the medication is being/was taken.

note: Option<Vec<Box<Annotation>>>

Provides extra information about the medication statement that is not conveyed by the other attributes.

dosage: Option<Vec<Box<Dosage>>>

Indicates how the medication is/was or should be taken by the patient.

Trait Implementations

impl Clone for MedicationStatement

fn clone(&self) -> MedicationStatement

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for MedicationStatement

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

Formats the value using the given formatter.

impl Default for MedicationStatement

fn default() -> MedicationStatement

Returns the “default value” for a type.

impl FHIRJSONDeserializer for MedicationStatement

fn from_json_str(s: &str) -> Result<Self, DeserializeError>

fn from_serde_value( obj: &Value, context: Context<'_>, ) -> Result<Self, DeserializeError>

impl FHIRJSONSerializer for MedicationStatement

fn serialize_value( &self, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn serialize_extension( &self, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn serialize_field( &self, field: &str, writer: &mut dyn Write, ) -> Result<bool, SerializeError>

fn is_fp_primitive(&self) -> bool

impl MetaValue for MedicationStatement

fn fields(&self) -> Vec<&'static str>

fn get_field<'a>(&'a self, field: &str) -> Option<&'a dyn MetaValue>

fn get_field_mut<'a>(&'a mut self, field: &str) -> Option<&'a mut dyn MetaValue>

fn get_index_mut<'a>( &'a mut self, index: usize, ) -> Option<&'a mut dyn MetaValue>

fn get_index<'a>(&'a self, _index: usize) -> Option<&'a dyn MetaValue>

fn typename(&self) -> &'static str

fn as_any(&self) -> &dyn Any

fn flatten(&self) -> Vec<&dyn MetaValue>