IP Review

Unattributed Code Systems

Copyright Fragment

This fragment is not visible to the reader

This publication includes IP covered under the following statements.

The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
- Unified Code for Units of Measure (UCUM) : Medication/01A-Cefuroxime1500GenericExplicit , Medication/01C-Cefuroxime1500Branded ... Show 10 more
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org .
Show Usage
- SNOMED Clinical Terms® (SNOMED CT®): Bundle/200-multiitem-prescription-without-orchestration , IHEMedication ... Show 16 more
This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
Show Usage
- MedicationKnowledge Characteristic Codes : MedicationCharacteristic

Copyright and Registered Trademark Uses

IG © 2021+ Integrating the Healthcare Enterprise (IHE). Package ihe.pharm.mpd#0.1.0 based on FHIR 5.0.0. Generated 2025-04-01 Links: Table of Contents | QA Report Version History | CC0 | Propose a changeexternal ( src )
hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
Medication - Product Name: Tilidin HEXAL® comp Lösung, 50/4 mg je 0,72 ml Tropfen zum Einnehmen, Lösung ( src )
Medication Prescription and Dispense (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/tree/jct-wip and changes regularly. See the Directory of published versions ( src )
There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed. In general, each prescribed drug will be a separate Medication Request. ( src )

External References

Type Reference Content

web profiles.ihe.net Recommend ATNA , encouraged IHE-IUA or SMART-app-launch

Type	Reference	Content
web	profiles.ihe.net	Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web	profiles.ihe.net	Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web	profiles.ihe.net
web	profiles.ihe.net
web	github.com	Medication Prescription and Dispense (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/tree/jct-wip and changes regularly. See the Directory of published versions
web	ihe.net	IG © 2021+ Integrating the Healthcare Enterprise (IHE) . Package ihe.pharm.mpd#0.1.0 based on FHIR 5.0.0 . Generated 2025-04-01 Links: Table of Contents \| QA Report Version History \| \| Propose a change
web	profiles.ihe.net	Links: Table of Contents \| QA Report Version History \| \| Propose a change
web	www.ihe.net	Links: Table of Contents \| QA Report Version History \| \| Propose a change
web	profiles.ihe.net	This publication is in the form of a FHIR implementation guide. Readers are invited to refer to the IHE General Intro . Implementers are expected to be familiar with the key concepts of the IHE approach.
web	profiles.ihe.net	This specification defines `Must Support` in StructureDefinition profiles as the element, when the minimal cardionality is zero, is R2 `Required if Known` , as found in Appendix Z . `Must Support` when the element minimal cardionality is not zero means R . Note that data access controls may apply to this rule.
web	hl7.eu	The IHE MPD Work was initiated based on the existing IHE profiles and anticipating a FHIR implementation, but has been decisively supported by HL7 Europe, who has worked on related specifications , which are related to past and ongoing projects and specifications that may be relevant.:
web	www.ihe.net	the IHE Community Medication Prescription and Dispense is a CDA-based specification of Prescription and Dispense documents. The current IHE MPD profile covers a superset of the functionalities in CMPD, to allow transitioning from CDA-based architeture to FHIR-based interoperability.
web	www.ihe.net	The IHE Mobile Medication Administration supports the request and report of medication administrations. The Medication Administration is a specific type of medication order, and therefore is technically compatible with the current profile, but is further specified in the MMA profile.
web	ihe.net	The author should pay special consideration to security profiles in this grouping section. Consideration should be given to Consistent Time (CT) Client, ATNA Secure Node or Secure Application, as well as other profiles. For the sake of clarity and completeness, even if this table begins to become long, a line should be added for each actor for each of the required grouping for security. Also see the ITI document titled 'Cookbook: Preparing the IHE Profile Security Section' at http://ihe.net/Technical_Frameworks/#IT for a list of suggested IT and security groupings.
web	profiles.ihe.net	See ITI TF-2x: Appendix Z.8 "Mobile Security Considerations"
web	profiles.ihe.net	IHE FHIR based profiles should reference the PHARM Appendix Z section 8 Mobile Security and Privacy Considerations base when appropriate.
web	wiki.ihe.net	This section is informative, not normative. It is intended to put this profile in context with other profiles. Any required groupings should have already been described above. Brief descriptions can go directly into this section; lengthy descriptions should go into an appendix. Examples of this material include ITI Cross Community Access (XCA) Grouping Rules (Section 18.2.3), the Radiology associated profiles listed at wiki.ihe.net, or ITI Volume 1 Appendix E "Cross Profile Considerations", and the "See Also" sections Radiology Profile descriptions on the wiki such as http://wiki.ihe.net/index.php/Scheduled_Workflow#See_Also . If this section is left blank, add "Not applicable."

web

profiles.ihe.net

web

profiles.ihe.net

web github.com Medication Prescription and Dispense (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/tree/jct-wip and changes regularly. See the Directory of published versions

web ihe.net IG © 2021+ Integrating the Healthcare Enterprise (IHE) . Package ihe.pharm.mpd#0.1.0 based on FHIR 5.0.0 . Generated 2025-04-01
Links: Table of Contents | QA Report Version History | | Propose a change

web profiles.ihe.net Links: Table of Contents | QA Report Version History | | Propose a change

web www.ihe.net Links: Table of Contents | QA Report Version History | | Propose a change

web profiles.ihe.net This publication is in the form of a FHIR implementation guide. Readers are invited to refer to the IHE General Intro . Implementers are expected to be familiar with the key concepts of the IHE approach.

web profiles.ihe.net This specification defines Must Support in StructureDefinition profiles as the element, when the minimal cardionality is zero, is R2 Required if Known , as found in Appendix Z . Must Support when the element minimal cardionality is not zero means R . Note that data access controls may apply to this rule.

web hl7.eu The IHE MPD Work was initiated based on the existing IHE profiles and anticipating a FHIR implementation, but has been decisively supported by HL7 Europe, who has worked on related specifications , which are related to past and ongoing projects and specifications that may be relevant.:

web www.ihe.net the IHE Community Medication Prescription and Dispense is a CDA-based specification of Prescription and Dispense documents. The current IHE MPD profile covers a superset of the functionalities in CMPD, to allow transitioning from CDA-based architeture to FHIR-based interoperability.

web www.ihe.net The IHE Mobile Medication Administration supports the request and report of medication administrations. The Medication Administration is a specific type of medication order, and therefore is technically compatible with the current profile, but is further specified in the MMA profile.

web ihe.net The author should pay special consideration to security profiles in this grouping section. Consideration should be given to Consistent Time (CT) Client, ATNA Secure Node or Secure Application, as well as other profiles. For the sake of clarity and completeness, even if this table begins to become long, a line should be added for each actor for each of the required grouping for security. Also see the ITI document titled 'Cookbook: Preparing the IHE Profile Security Section' at http://ihe.net/Technical_Frameworks/#IT for a list of suggested IT and security groupings.

web profiles.ihe.net See ITI TF-2x: Appendix Z.8 "Mobile Security Considerations"

web profiles.ihe.net IHE FHIR based profiles should reference the PHARM Appendix Z section 8 Mobile Security and Privacy Considerations base when appropriate.

web wiki.ihe.net This section is informative, not normative. It is intended to put this profile in context with other profiles. Any required groupings should have already been described above. Brief descriptions can go directly into this section; lengthy descriptions should go into an appendix. Examples of this material include ITI Cross Community Access (XCA) Grouping Rules (Section 18.2.3), the Radiology associated profiles listed at wiki.ihe.net, or ITI Volume 1 Appendix E "Cross Profile Considerations", and the "See Also" sections Radiology Profile descriptions on the wiki such as http://wiki.ihe.net/index.php/Scheduled_Workflow#See_Also . If this section is left blank, add "Not applicable."

Internal Images

gemini-logo-fin.png