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: [IHE PHARM White Paper] Logical Model for order

Official URL: http://profiles.ihe.net/PHARM/ihe.pharm.mpd/StructureDefinition/MedicationOrderIHEPWP Version: 0.1.0
Active as of 2023-02-04 Computable Name: MedicationOrderIHEPWP

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

A prescription is issued by one ordering healthcare professional for one patient, in the context of zero or one encounter (between the patient and the ordering physician and/or the healthcare institution).

Usage:

  • This Logical Model Profile is not used by any profiles in this Implementation Guide

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
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

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
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

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

This structure is derived from Base

Summary

Mandatory: 0 element (3 nested mandatory elements)

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

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
.. MedicationOrderIHEPWP 0..*Base[IHE PHARM White Paper] Logical Model for order
... identifier 0..1IdentifierThe business identifier(s) for the medication Order
... date 0..1dateTimeWhen prescription was initially made
... patient 1..1Reference(Patient)The person for which the medication is prescribed.
... note 0..*AnnotationAdditional Information about the prescription
... requester 0..1Reference(Practitioner)Who made the prescription
... status 1..1codeStatus of the prescription ORDERED|PLACED|IN PROGRESS|COMPLETED|CANCELLED|DISCONTINUED|SUSPENDED
... prescriptionItem 0..*BackboneElementA prescription item belongs to one prescription and represents one prescribed medication. It may be associated with one or more observations. Prescription Item is the atomic entity for logistics, distribution and billing.
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... prescriptionItemID 1..1Identifier Prescription Item ID
.... treatmentDate 0..1DurationBeginning date of treatment / length of treatment / End of treatment date ( the date the treatment is due to end) and/or number of renewals
.... reasonForPrescribing 0..1stringReason for prescribing (e.g. diagnosis, prognosis, protocol, clinical assessment …)
.... Frequency 0..1string
.... substitutionAllowed 0..1stringSubstitution allowed or not (can the pharmacist do a substitution of medication?)
.... route 0..1stringRoute of administration
.... Dosage 0..1string
.... intakePattern 0..1stringIntake pattern for the medication
.... medicalInstructions 0..1stringDiagnosis or reason for prescribing is this similar the 3rd bullet point?
.... alertAboutRestrictions 0..1stringAlert about prescribing restrictions
.... relatedtoChronic 0..1stringRelated to a chronic disease or not (listed or unlisted)
.... specificFollowUp 0..1stringSpecific follow-up elements
.... additionalComment 0..1stringAdditional comment (may be used by the prescriber to inform the pharmacist that he is aware of a potential ICA)
.... status 0..1stringStatus (see the “Relevant Standards” chapter)

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

This structure is derived from Base

Summary

Mandatory: 0 element (3 nested mandatory elements)

 

Other representations of profile: CSV, Excel