Generated Narrative: StructureDefinition BeModelMedicationDispense Name Flags Card. Type Description & Constraints BeModelMedicationDispense 0..* Base Medication Dispense (model) #xD; identifier 0..* Identifier The business identifier(s) for the medication dispense record #xD; recordedDate 0..1 dateTime The date (or date+time) when the dispense was recorded #xD; basedOnMedicationLine 0..1 Reference(Medication Line (model)) The medication line that this dispense is related to #xD; patient 1..1 Reference(BePatient) The person for which the medication is dispensed #xD; status 1..1 code The status of the dispense record Binding: MedicationDispense Status Codes (required) #xD; statusReason 0..1 CodeableConcept The reason why the dispense was not performed, if it was not performed Binding: MedicationDispense Status Reason Codes (required) #xD; dispenser 0..1 BackboneElement The dispenser, if known and relevant #xD; dispenser 0..1 Reference(BePractitioner) Reference to person that performed the recording or reporting #xD; organization 0..1 Reference(BeOrganization) Reference to person that performed the recording or reporting #xD; dispenseDate 1..1 dateTime The date (or date+time) when the dispense ocurred #xD; prescription 0..1 BackboneElement Information about a prescription related to the dispense #xD; isPrescribed 0..1 boolean Whether this dispense was performed against a prescription #xD; prescription 0..1 Reference() The prescription identification #xD; dispensedItem 1..1 BackboneElement Each product that was dispensed #xD; product 1..1 CodeableConcept The product that was dispensed - coded or not (e.g. for magistral preparations) #xD; quantityDispensed 0..1 SimpleQuantity The amount of product that was dispensed #xD; dosage 0..* Dosage The structured dosage or text instructions for use #xD; offLabel 0..1 CodeableConcept Text or coded reason for different dosage #xD; note 0..* Annotation Additional information about the dispense - this can be relevant history, any remarks by the patient or professional, etc. #xD; Documentation for this format
This is the logical model for the Dispense Record entry - the information that can be captured upon the act of dispensing - in a hospital pharmacy, or a community pharmacy. This is not for a future dispense, rather a record of an actual dispense.
Logical data model for Medication Dispense.
The business identifier(s) for the medication dispense record
The business identifier(s) for the medication dispense session, also known as Session GUID (SGUID).
The date (or date+time) when the dispense was recorded
The medication line that this dispense is related to
The person for which the medication is dispensed
The person for which the medication is dispensed.
The reason why the dispense was not performed, if it was not performed
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. 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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 can 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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Reference to person that performed the recording or reporting
The date (or date+time) when the dispense ocurred
Information about a prescription related to the dispense
Whether this dispense was performed against a prescription
The product that was dispensed - coded or not (e.g. for magistral preparations)
The amount of product that was dispensed
The structured dosage or text instructions for use
Text or coded reason for different dosage
Additional information about the dispense - this can be relevant history, any remarks by the patient or professional, etc.