pub struct MedicationKnowledgeInner {Show 48 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 code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub status: Option<MedicationKnowledgeStatusCodes>,
pub status_ext: Option<FieldExtension>,
pub author: Option<Reference>,
pub author_ext: Option<FieldExtension>,
pub intended_jurisdiction: Vec<Option<CodeableConcept>>,
pub intended_jurisdiction_ext: Vec<Option<FieldExtension>>,
pub name: Vec<Option<String>>,
pub name_ext: Vec<Option<FieldExtension>>,
pub related_medication_knowledge: Vec<Option<MedicationKnowledgeRelatedMedicationKnowledge>>,
pub related_medication_knowledge_ext: Vec<Option<FieldExtension>>,
pub associated_medication: Vec<Option<Reference>>,
pub associated_medication_ext: Vec<Option<FieldExtension>>,
pub product_type: Vec<Option<CodeableConcept>>,
pub product_type_ext: Vec<Option<FieldExtension>>,
pub monograph: Vec<Option<MedicationKnowledgeMonograph>>,
pub monograph_ext: Vec<Option<FieldExtension>>,
pub preparation_instruction: Option<String>,
pub preparation_instruction_ext: Option<FieldExtension>,
pub cost: Vec<Option<MedicationKnowledgeCost>>,
pub cost_ext: Vec<Option<FieldExtension>>,
pub monitoring_program: Vec<Option<MedicationKnowledgeMonitoringProgram>>,
pub monitoring_program_ext: Vec<Option<FieldExtension>>,
pub indication_guideline: Vec<Option<MedicationKnowledgeIndicationGuideline>>,
pub indication_guideline_ext: Vec<Option<FieldExtension>>,
pub medicine_classification: Vec<Option<MedicationKnowledgeMedicineClassification>>,
pub medicine_classification_ext: Vec<Option<FieldExtension>>,
pub packaging: Vec<Option<MedicationKnowledgePackaging>>,
pub packaging_ext: Vec<Option<FieldExtension>>,
pub clinical_use_issue: Vec<Option<Reference>>,
pub clinical_use_issue_ext: Vec<Option<FieldExtension>>,
pub storage_guideline: Vec<Option<MedicationKnowledgeStorageGuideline>>,
pub storage_guideline_ext: Vec<Option<FieldExtension>>,
pub regulatory: Vec<Option<MedicationKnowledgeRegulatory>>,
pub regulatory_ext: Vec<Option<FieldExtension>>,
pub definitional: Option<MedicationKnowledgeDefinitional>,
pub definitional_ext: Option<FieldExtension>,
/* private fields */
}Expand description
Information about a medication that is used to support knowledge.
MedicationKnowledge v5.0.0
Definition of Medication Knowledge
Information about a medication that is used to support knowledge.
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 for this medication
Business identifier for this medication.
This is a business identifier, not a resource identifier (see discussion).
identifier_ext: Vec<Option<FieldExtension>>Extension field.
code: Option<CodeableConcept>MedicationFormalRepresentation; Code that identifies this medication
A code that specifies this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems.
Depending on the context of use, the code that was actually selected by the user (prescriber, dispenser, etc.) will have the coding.userSelected set to true. As described in the coding datatype: “A coding may be marked as a “userSelected” if a user selected the particular coded value in a user interface (e.g. the user selects an item in a pick-list). If a user selected coding exists, it is the preferred choice for performing translations etc. Other codes can only be literal translations to alternative code systems, or codes at a lower level of granularity (e.g. a generic code for a vendor-specific primary one).
code_ext: Option<FieldExtension>Extension field.
status: Option<MedicationKnowledgeStatusCodes>MedicationKnowledgeStatus; active | entered-in-error | inactive
A code to indicate if the medication referred to by this MedicationKnowledge is in active use within the drug database or inventory system. The status refers to the validity about the information of the medication and not to its medicinal properties.
This status is intended to identify if the medication in a local system is in active use within a drug database or inventory. For example, a pharmacy system may create a new drug file record for a compounded product “ABC Hospital Special Cream” with an active status. At some point in the future, it may be determined that the drug record was created with an error and the status is changed to “entered in error”. This status is not intended to specify if a medication is part of a particular formulary. It is possible that the drug record may be referenced by multiple formularies or catalogues and each of those entries would have a separate status.
status_ext: Option<FieldExtension>Extension field.
Creator or owner of the knowledge or information about the medication
The creator or owner of the knowledge or information about the medication.
Extension field.
intended_jurisdiction: Vec<Option<CodeableConcept>>Codes that identify the different jurisdictions for which the information of this resource was created
Lists the jurisdictions that this medication knowledge was written for.
The codes could have varying granularity from a country or group of countries down to a specific district.
intended_jurisdiction_ext: Vec<Option<FieldExtension>>Extension field.
name: Vec<Option<String>>A name associated with the medication being described
All of the names for a medication, for example, the name(s) given to a medication in different countries. For example, acetaminophen and paracetamol or salbutamol and albuterol.
name_ext: Vec<Option<FieldExtension>>Extension field.
Associated or related medication information
Associated or related medications. For example, if the medication is a branded product (e.g. Crestor), this is the Therapeutic Moeity (e.g. Rosuvastatin) or if this is a generic medication (e.g. Rosuvastatin), this would link to a branded product (e.g. Crestor.
Extension field.
associated_medication: Vec<Option<Reference>>The set of medication resources that are associated with this medication
Links to associated medications that could be prescribed, dispensed or administered.
associated_medication_ext: Vec<Option<FieldExtension>>Extension field.
product_type: Vec<Option<CodeableConcept>>Category of the medication or product
Category of the medication or product (e.g. branded product, therapeutic moeity, generic product, innovator product, etc.).
product_type_ext: Vec<Option<FieldExtension>>Extension field.
monograph: Vec<Option<MedicationKnowledgeMonograph>>Associated documentation about the medication
Associated documentation about the medication.
monograph_ext: Vec<Option<FieldExtension>>Extension field.
preparation_instruction: Option<String>The instructions for preparing the medication
The instructions for preparing the medication.
preparation_instruction_ext: Option<FieldExtension>Extension field.
cost: Vec<Option<MedicationKnowledgeCost>>The pricing of the medication
The price of the medication.
cost_ext: Vec<Option<FieldExtension>>Extension field.
monitoring_program: Vec<Option<MedicationKnowledgeMonitoringProgram>>Program under which a medication is reviewed
The program under which the medication is reviewed.
monitoring_program_ext: Vec<Option<FieldExtension>>Extension field.
indication_guideline: Vec<Option<MedicationKnowledgeIndicationGuideline>>Guidelines or protocols for administration of the medication for an indication
Guidelines or protocols that are applicable for the administration of the medication based on indication.
indication_guideline_ext: Vec<Option<FieldExtension>>Extension field.
medicine_classification: Vec<Option<MedicationKnowledgeMedicineClassification>>Categorization of the medication within a formulary or classification system
Categorization of the medication within a formulary or classification system.
medicine_classification_ext: Vec<Option<FieldExtension>>Extension field.
packaging: Vec<Option<MedicationKnowledgePackaging>>Details about packaged medications
Information that only applies to packages (not products).
packaging_ext: Vec<Option<FieldExtension>>Extension field.
clinical_use_issue: Vec<Option<Reference>>Potential clinical issue with or between medication(s)
Potential clinical issue with or between medication(s) (for example, drug-drug interaction, drug-disease contraindication, drug-allergy interaction, etc.).
clinical_use_issue_ext: Vec<Option<FieldExtension>>Extension field.
storage_guideline: Vec<Option<MedicationKnowledgeStorageGuideline>>How the medication should be stored
Information on how the medication should be stored, for example, refrigeration temperatures and length of stability at a given temperature.
storage_guideline_ext: Vec<Option<FieldExtension>>Extension field.
regulatory: Vec<Option<MedicationKnowledgeRegulatory>>Regulatory information about a medication
Regulatory information about a medication.
regulatory_ext: Vec<Option<FieldExtension>>Extension field.
definitional: Option<MedicationKnowledgeDefinitional>Minimal definition information about the medication
Along with the link to a Medicinal Product Definition resource, this information provides common definitional elements that are needed to understand the specific medication that is being described.
definitional_ext: Option<FieldExtension>Extension field.
Trait Implementations§
Source§impl Clone for MedicationKnowledgeInner
impl Clone for MedicationKnowledgeInner
Source§fn clone(&self) -> MedicationKnowledgeInner
fn clone(&self) -> MedicationKnowledgeInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more