Medication Prescription and Delivery (MPD)
0.1.0 - ci-build International flag

Medication Prescription and Delivery (MPD), published by Integrating the Healthcare Enterprise (IHE). This is not an authorized publication; it is the continuous build for version 0.1.0). This version is based on the current content of https://github.com/IHE/pharm-mm/ and changes regularly. See the Directory of published versions

Logical Model: MedicationDispenseIHEMM - Detailed Descriptions

Active as of 2023-02-04

Definitions for the MedicationDispenseIHEMM logical model.

Guidance on how to interpret the contents of this table can be found here.

1. MedicationDispenseIHEMM
Definition

A medication dispense relates to zero or one prescription item of one prescription. There are cases when a medication is dispensed before the prescription is created. Medications dispensed outside the context of any prescription are considered as self-prescribed by the professional who dispenses. Thus they are still attached to a pseudo-prescription. A medication dispense is issued by one pharmacy staff. It is related to zero (community use case) or one (hospital use case) encounter of care.

Control0..?
2. MedicationDispenseIHEMM.identifier
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
3. MedicationDispenseIHEMM.status
Control0..1
Typecode
4. MedicationDispenseIHEMM.statusReason
Control0..1
TypeCodeableConcept
5. MedicationDispenseIHEMM.category
Control0..1
TypeCodeableConcept
6. MedicationDispenseIHEMM.medication
Control0..1
TypeCodeableConcept
7. MedicationDispenseIHEMM.subject
Control0..1
TypeReference(Patient)
8. MedicationDispenseIHEMM.context
Control0..1
TypeReference(Encounter)
9. MedicationDispenseIHEMM.supportingInformation
Control0..1
TypeReference
10. MedicationDispenseIHEMM.type
Control0..1
TypeCodeableConcept
11. MedicationDispenseIHEMM.quantity
Control0..1
TypeQuantity
12. MedicationDispenseIHEMM.note
Control0..1
TypeAnnotation
13. MedicationDispenseIHEMM.prescription
Control0..1
TypeReference(MedicationRequest)
14. MedicationDispenseIHEMM.steps
Control0..*
TypeBackboneElement
15. MedicationDispenseIHEMM.steps.stepName
Control0..1
TypeCodeableConcept
16. MedicationDispenseIHEMM.steps.datetimeStep
Control0..1
TypedateTime
17. MedicationDispenseIHEMM.steps.actor
Control0..1
Typestring
18. MedicationDispenseIHEMM.substitution
Control0..1
Typeboolean
19. MedicationDispenseIHEMM.receiver
Control0..1
TypeReference(Patient|Person|Practitioner)
20. MedicationDispenseIHEMM.destination
Control0..1
TypeReference(location)
21. MedicationDispenseIHEMM.detectedIssues
Control0..1
TypeReference(DetectedIssue)
22. MedicationDispenseIHEMM.eventHistory
Control0..1
TypeReference(Provenance)

Guidance on how to interpret the contents of this table can be found here.

1. MedicationDispenseIHEMM
Definition

A medication dispense relates to zero or one prescription item of one prescription. There are cases when a medication is dispensed before the prescription is created. Medications dispensed outside the context of any prescription are considered as self-prescribed by the professional who dispenses. Thus they are still attached to a pseudo-prescription. A medication dispense is issued by one pharmacy staff. It is related to zero (community use case) or one (hospital use case) encounter of care.

Control0..*
2. MedicationDispenseIHEMM.identifier
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
3. MedicationDispenseIHEMM.status
Control0..1
Typecode
4. MedicationDispenseIHEMM.statusReason
Control0..1
TypeCodeableConcept
5. MedicationDispenseIHEMM.category
Control0..1
TypeCodeableConcept
6. MedicationDispenseIHEMM.medication
Control0..1
TypeCodeableConcept
7. MedicationDispenseIHEMM.subject
Control0..1
TypeReference(Patient)
8. MedicationDispenseIHEMM.context
Control0..1
TypeReference(Encounter)
9. MedicationDispenseIHEMM.supportingInformation
Control0..1
TypeReference
10. MedicationDispenseIHEMM.type
Control0..1
TypeCodeableConcept
11. MedicationDispenseIHEMM.quantity
Control0..1
TypeQuantity
12. MedicationDispenseIHEMM.note
Control0..1
TypeAnnotation
13. MedicationDispenseIHEMM.prescription
Control0..1
TypeReference(MedicationRequest)
14. MedicationDispenseIHEMM.steps
Control0..*
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
15. MedicationDispenseIHEMM.steps.modifierExtension
Definition

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

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
Requirements

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.

Alternate Namesextensions, user content, modifiers
Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
16. MedicationDispenseIHEMM.steps.stepName
Control0..1
TypeCodeableConcept
17. MedicationDispenseIHEMM.steps.datetimeStep
Control0..1
TypedateTime
18. MedicationDispenseIHEMM.steps.actor
Control0..1
Typestring
19. MedicationDispenseIHEMM.substitution
Control0..1
Typeboolean
20. MedicationDispenseIHEMM.receiver
Control0..1
TypeReference(Patient|Person|Practitioner)
21. MedicationDispenseIHEMM.destination
Control0..1
TypeReference(location)
22. MedicationDispenseIHEMM.detectedIssues
Control0..1
TypeReference(DetectedIssue)
23. MedicationDispenseIHEMM.eventHistory
Control0..1
TypeReference(Provenance)

Guidance on how to interpret the contents of this table can be found here.

1. MedicationDispenseIHEMM
Definition

A medication dispense relates to zero or one prescription item of one prescription. There are cases when a medication is dispensed before the prescription is created. Medications dispensed outside the context of any prescription are considered as self-prescribed by the professional who dispenses. Thus they are still attached to a pseudo-prescription. A medication dispense is issued by one pharmacy staff. It is related to zero (community use case) or one (hospital use case) encounter of care.

Control0..*
2. MedicationDispenseIHEMM.identifier
NoteThis is a business identifier, not a resource identifier (see discussion)
Control0..1
TypeIdentifier
3. MedicationDispenseIHEMM.status
Control0..1
Typecode
4. MedicationDispenseIHEMM.statusReason
Control0..1
TypeCodeableConcept
5. MedicationDispenseIHEMM.category
Control0..1
TypeCodeableConcept
6. MedicationDispenseIHEMM.medication
Control0..1
TypeCodeableConcept
7. MedicationDispenseIHEMM.subject
Control0..1
TypeReference(Patient)
8. MedicationDispenseIHEMM.context
Control0..1
TypeReference(Encounter)
9. MedicationDispenseIHEMM.supportingInformation
Control0..1
TypeReference
10. MedicationDispenseIHEMM.type
Control0..1
TypeCodeableConcept
11. MedicationDispenseIHEMM.quantity
Control0..1
TypeQuantity
12. MedicationDispenseIHEMM.note
Control0..1
TypeAnnotation
13. MedicationDispenseIHEMM.prescription
Control0..1
TypeReference(MedicationRequest)
14. MedicationDispenseIHEMM.steps
Control0..*
TypeBackboneElement
InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
15. MedicationDispenseIHEMM.steps.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
16. MedicationDispenseIHEMM.steps.extension
Definition

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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, user content
Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
SlicingThis element introduces a set of slices on MedicationDispenseIHEMM.steps.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
17. MedicationDispenseIHEMM.steps.modifierExtension
Definition

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

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
Requirements

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.

Alternate Namesextensions, user content, modifiers
Comments

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.

InvariantsDefined on this element
ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
18. MedicationDispenseIHEMM.steps.stepName
Control0..1
TypeCodeableConcept
19. MedicationDispenseIHEMM.steps.datetimeStep
Control0..1
TypedateTime
20. MedicationDispenseIHEMM.steps.actor
Control0..1
Typestring
21. MedicationDispenseIHEMM.substitution
Control0..1
Typeboolean
22. MedicationDispenseIHEMM.receiver
Control0..1
TypeReference(Patient|Person|Practitioner)
23. MedicationDispenseIHEMM.destination
Control0..1
TypeReference(location)
24. MedicationDispenseIHEMM.detectedIssues
Control0..1
TypeReference(DetectedIssue)
25. MedicationDispenseIHEMM.eventHistory
Control0..1
TypeReference(Provenance)