Unattributed Code Systems

• http://snomed.info/sct
• http://standardterms.edqm.eu
• http://unstats.un.org/unsd/methods/m49/m49.htm
• http://www.whocc.no/atc

Copyright Fragment

This fragment is not visible to the reader

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-03-20 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 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/tree/offLabelUse 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
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 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/tree/offLabelUse 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-03-20 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	should use a security framework. Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
web	profiles.ihe.net	should use a security framework. Recommend ATNA , encouraged IHE-IUA or SMART-app-launch
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 .
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 ITI 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