pub struct MedicationStatementInner {Show 42 fields
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 part_of: Vec<Option<Reference>>,
pub part_of_ext: Vec<Option<FieldExtension>>,
pub status: MedicationStatementStatusCodes,
pub status_ext: 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 effective: Option<MedicationStatementEffective>,
pub effective_ext: Option<MedicationStatementEffectiveExtension>,
pub date_asserted: Option<DateTime>,
pub date_asserted_ext: Option<FieldExtension>,
pub information_source: Vec<Option<Reference>>,
pub information_source_ext: Vec<Option<FieldExtension>>,
pub derived_from: Vec<Option<Reference>>,
pub derived_from_ext: Vec<Option<FieldExtension>>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub related_clinical_information: Vec<Option<Reference>>,
pub related_clinical_information_ext: Vec<Option<FieldExtension>>,
pub rendered_dosage_instruction: Option<String>,
pub rendered_dosage_instruction_ext: Option<FieldExtension>,
pub dosage: Vec<Option<Dosage>>,
pub dosage_ext: Vec<Option<FieldExtension>>,
pub adherence: Option<MedicationStatementAdherence>,
pub adherence_ext: Option<FieldExtension>,
/* private fields */
}Expand description
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 medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement 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.
MedicationStatement v5.0.0
Record of medication being taken by a patient
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 medicationstatement and a medicationadministration is that the medication administration has complete administration information and is based on actual administration information from the person who administered the medication. A medicationstatement 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.
The MedicationStatement resource was previously called MedicationStatement.
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 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.
This is a business identifier, not a resource identifier.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
part_of: Vec<Option<Reference>>Part of referenced event
A larger event of which this particular MedicationStatement is a component or step.
part_of_ext: Vec<Option<FieldExtension>>Extension field.
status: MedicationStatementStatusCodesMedicationStatementStatus; recorded | entered-in-error | draft
A code representing the status of recording the medication statement.
This status concerns just the recording of the medication statement. MedicationStatement.adherence should be used for indicating a patient’s adherence to the information in this resource. Note, the statuses are different than in previous releases for MedicationStatement or MedicationStatement.
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.
category: Vec<Option<CodeableConcept>>MedicationStatementAdministrationLocation; Type of medication statement
Type of medication statement (for example, drug classification like ATC, where meds would be administered, legal category of the medication.).
category_ext: Vec<Option<FieldExtension>>Extension field.
medication: CodeableReferenceMedicationCode; What medication was taken
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.
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: ReferenceWho is/was taking the medication
The person, animal or group who is/was taking the medication.
subject_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>Encounter associated with MedicationStatement
The encounter that establishes the context for this MedicationStatement.
encounter_ext: Option<FieldExtension>Extension field.
effective: Option<MedicationStatementEffective>The date/time or interval when the medication is/was/will be taken
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.adherence element is Not Taking).
This attribute reflects the period over which the patient consumed the medication and is expected to be populated on the majority of Medication Statements. If the medication is still being taken and is expected to continue indefinitely at the time the usage is recorded, the “end” date will be omitted. If the end date is known, then it is included as the “end date”. The date/time attribute supports a variety of dates - year, year/month and exact date. If something more than this is required, this should be conveyed as text.
effective_ext: Option<MedicationStatementEffectiveExtension>Extension field.
date_asserted: Option<DateTime>When the usage was asserted?
The date when the Medication Statement was asserted by the information source.
date_asserted_ext: Option<FieldExtension>Extension field.
information_source: Vec<Option<Reference>>Person or organization that provided the information about the taking of this medication
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.
information_source_ext: Vec<Option<FieldExtension>>Extension field.
derived_from: Vec<Option<Reference>>Link to information used to derive the MedicationStatement
Allows linking the MedicationStatement to the underlying MedicationRequest, or to other information that supports or is used to derive the MedicationStatement.
Likely references would be to MedicationRequest, MedicationDispense, Claim, Observation or QuestionnaireAnswers. The most common use cases for deriving a MedicationStatement comes from creating a MedicationStatement from a MedicationRequest or from a lab observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the MedicationStatement from.
derived_from_ext: Vec<Option<FieldExtension>>Extension field.
reason: Vec<Option<CodeableReference>>MedicationReason; Reason for why the medication is being/was taken
A concept, Condition or observation that supports why the medication is being/was taken.
This could be a diagnosis code. If a full condition record exists or additional detail is needed, use reasonForUseReference.
reason_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Further information about the usage
Provides extra information about the Medication Statement that is not conveyed by the other attributes.
note_ext: Vec<Option<FieldExtension>>Extension field.
Link to information relevant to the usage of a medication
Link to information that is relevant to a medication statement, for example, illicit drug use, gestational age, etc.
Extension field.
rendered_dosage_instruction: Option<String>Full representation of the dosage instructions
The full representation of the dose of the medication included in all dosage instructions. To be used when multiple dosage instructions are included to represent complex dosing such as increasing or tapering doses.
rendered_dosage_instruction_ext: Option<FieldExtension>Extension field.
dosage: Vec<Option<Dosage>>Details of how medication is/was taken or should be taken
Indicates how the medication is/was or should be taken by the patient.
The dates included in the dosage on a Medication Statement reflect the dates for a given dose. For example, “from November 1, 2016 to November 3, 2016, take one tablet daily and from November 4, 2016 to November 7, 2016, take two tablets daily.” It is expected that this specificity may only be populated where the patient brings in their labeled container or where the Medication Statement is derived from a MedicationRequest.
dosage_ext: Vec<Option<FieldExtension>>Extension field.
adherence: Option<MedicationStatementAdherence>Indicates whether the medication is or is not being consumed or administered
Indicates whether the medication is or is not being consumed or administered.
This element can be used to indicate whether a patient is following a course of treatment as instructed/prescribed or whether they are taking medications of their own volition. It can also be used to indicate that a patient is not taking a medication, either because they were told not to or because they decided on their own.
adherence_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for MedicationStatementInner
impl Clone for MedicationStatementInner
Source§fn clone(&self) -> MedicationStatementInner
fn clone(&self) -> MedicationStatementInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more