Hospital Medication Workflow
Hospital Medication Workflow Profile covers the message-based workflow related to medication prescriptions inside a healthcare institution.
This is a template page. Update in process
The Hospital Medication Workflow Profile describes the interoperability and the transactions present in a typical hospital workflow concerning the prescription, dispensing, distribution and administration of medication.
It describes the transactions between the Prescription Placer, the Pharmaceutical Adviser, the Medication Dispenser, the Medication Administration Informer to establish an end-to-end operational workflow.
While covering this end-to-end scenario, the many possible exceptions and errors in each part are not covered yet. By establishing a working flow in this first release, we expect to facilitate the detailing of the exceptions in forthcoming editions of this profile.
The current release of the profile includes the messages that relate to the clinical information flow. The supply flow is foreseen, but is not detailed in this release.
<List the key benefits the profile provides (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler). Consider using a bullet list for readability>
<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>
<If the user might be familiar with the mechanisms used by the profile, you can mention them here. E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>
<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short. E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>
<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:
The actors supported are:
- Prescription Placer (typically a physician)
- Pharmaceutical advisor (typically a pharmacist)
- Medication dispenser - receives the validated prescription and prepares the medication fot the patient (typically a pharmacy technician or a pharmacist, or a robot, or, more common, a chain of actors)
- Medication administration informer (typically a nurse)
The HMW profile supports the following transactions :
- Medication Order (Prescription) ,
- Validated order (after pharmaceutical analysis, if needed),
- Medication Preparation report (after medication is assigned to the patient, for a specific administration)
- Administration Report
Optionally, the following transactions allow the dispensing pharmacist and the nurse to do any preparation while waiting for the needed pharmaceutical validation
- Advance prescription notification
- Validated order confirmation (notifying the dispenser or administration informer of the validation, or any changes to the prescription.
Profile Status: Trial Implementation
<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.>
- Vol. 1 - Section 5 (HMW Profile)
<list all the standards on which the profile is based; if possible with links to sources>
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<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.
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>
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>
<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