Difference between revisions of "Community Medication Prescription and Dispense"
| Line 17: | Line 17: | ||
In general, the medication business process consists of five distinct processes, which have to be connected through interactions that transfer information and/or guide the workflow. The following figure shows this flow: | In general, the medication business process consists of five distinct processes, which have to be connected through interactions that transfer information and/or guide the workflow. The following figure shows this flow: | ||
| − | [[image:Pharm_process.PNG| | + | [[image:Pharm_process.PNG|1000px|left|The Pharmacy process.]] |
In the Community Pharmacy domain, the process of “administration of medication” can usually not be governed by IT based systems so just the processes “Planning”, “Prescription”, “Pharmaceutical Advice”, “Dispense” and “Administration” are covered by the Community Medication Prescription and Dispense Profile only. | In the Community Pharmacy domain, the process of “administration of medication” can usually not be governed by IT based systems so just the processes “Planning”, “Prescription”, “Pharmaceutical Advice”, “Dispense” and “Administration” are covered by the Community Medication Prescription and Dispense Profile only. | ||
Revision as of 05:12, 6 October 2017
Summary
The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation, dispense and administration of medication in the community domain.
Benefits
- Covers the complete workflow in Community Pharmacy setting
- Planning, prescribing, managing, dispensing and administring medication of a patient
- Capable to work with XDS document-based- or database backends
- Includes XDW
Details
In general, the medication business process consists of five distinct processes, which have to be connected through interactions that transfer information and/or guide the workflow. The following figure shows this flow:
In the Community Pharmacy domain, the process of “administration of medication” can usually not be governed by IT based systems so just the processes “Planning”, “Prescription”, “Pharmaceutical Advice”, “Dispense” and “Administration” are covered by the Community Medication Prescription and Dispense Profile only.
The CMPD Profile is intended to be used in the context of the Pharmacy Content Profiles :
- Community Medication Treatment Plan (MTP)
- Community Prescription Supplement (PRE)
- Community Pharmaceutical Advice Supplement (PADV)
- Community Dispense Supplement (DIS)
- Community Medication Administration (CMA)
- Community Medication List (PML)
Systems Affected
<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>
- PACS systems may store, manage, and/or display Evidence Documents.
- Display systems may query, retrieve and display Evidence Documents.
- Reporting workstations may retrieve, process and include details from Evidence Documents in reports
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
Documents:
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
IHE Radiology Technical Framework:
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >
This page is based on the Profile Overview Template