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 guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/pharm-mpd/ and changes regularly. See the Directory of published versions

Logical Model: Medication prescription (model)

Official URL: http://profiles.ihe.net/PHARM/ihe.pharm.mpd/StructureDefinition/MedicationPrescription Version: 0.1.0
Active as of 2024-10-26 Computable Name: MedicationPrescription

Copyright/Legal: IHE http://www.ihe.net/Governance/#Intellectual_Property

Logical model for medication prescription (or some other form of order)

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... @id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationPrescription 0..* Base Medication prescription (model)
Instances of this logical model can be the target of a Reference
... identifier 1..* II Business identifier(s) for the prescription
... groupIdentifier 0..1 II Identifier for the group that this prescription belongs to. This might be the common identifier in use cases where one national prescription contains several medication items, which can be handled as separate orders
... recordingDate 0..1 DT Time of authoring the prescription/draft in the information system
... recorder 0..1 Reference(Practitioner (model) | PractitionerRole) The recorder of the prescription/draft in the information system
... prescriber 1..1 Reference(Practitioner (model) | PractitionerRole) The person who made the prescription, and who takes the responsibility of the treatment
... category 0..* CD Category or categories of prescription. For example type of reimbursement, or type of prescription (e.g. hospital, private, etc).
... validFrom 0..1 DT Effective date of the prescription. The prescription is not dispensable before this date. In most cases this information repeats issueDate
... validUntil 0..1 DT The validity period end date. The prescription is not dispensable after this date.
... patient 1..1 Reference(Patient (model)) The person for whom the medication is prescribed/ordered
... status 1..1 CD Status of the prescription, this should not be status of treatment
... statusReason 0..* CD Reason for the current status of prescription, for example the reason why the prescription was made invalid
... statusReasonText 0..1 ST Textual reason for the current status of prescription
... medication 1..1 Reference(Medicinal product (model)) Prescribed product, branded, generic, virtual, extemporal, etc
... indication 0..* CD Reason for the prescription (typically diagnosis, or a procedure)
... indicationText 0..1 ST Reason for the prescription in textual form. This might not be allowed by some implementations.
... treatmentPeriod 0..1 Period Period over which the medication is to be taken (in case of multiple dosaging schemes, this would be the overall period of all dosages.)
... usageInstructions 0..* Reference(Dosaging (model)) Dosaging and administration instructions
... preparationInstructions 0..1 ST Additional instructions about preparation or dispense
... substitution 0..1 Class Whether and which type of substitution is allowed for this medication treatment line
.... @id 0..1 id Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... allowed 0..1 BL Whether substitution is allowed or not.
.... type 1..1 CD The type of substitution that is allowed.
.... typeReason[x] 0..1 CD, ST Reason for the substitution requirement
... comment 0..* ST Additional information or comments

doco Documentation for this format

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel