Difference between revisions of "Pharm Tech Minutes 2011.10.13"
| Line 73: | Line 73: | ||
=====use case 2 (IPEC)===== | =====use case 2 (IPEC)===== | ||
| − | + | Send to a device observation consumer (for documentation purpose)to produce a flow sheet. | |
On the US market, sometimes it's the same system and sub-systems, sometimes not. | On the US market, sometimes it's the same system and sub-systems, sometimes not. | ||
| Line 87: | Line 87: | ||
It's less restrictive. | It's less restrictive. | ||
IPEC is a very specific infusion pump function. | IPEC is a very specific infusion pump function. | ||
| − | In DEC, | + | |
| + | In '''DEC''', | ||
| + | |||
* The device observation reporter (DOR)is a pump. | * The device observation reporter (DOR)is a pump. | ||
| + | |||
* The device observation consumer (DOC)is right behind the Medication Administration Informer(MAI). | * The device observation consumer (DOC)is right behind the Medication Administration Informer(MAI). | ||
| Line 95: | Line 98: | ||
When the BCMA is checking and the pump is started, it's the DEC profile. | When the BCMA is checking and the pump is started, it's the DEC profile. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | 2 differents actors grouping : | + | '''2 differents actors grouping :''' |
| − | 1) MAI with DOC and | + | |
| − | 2) seperatly MAI with the device ordering programmer (DOP) | + | : 1) MAI with DOC and |
| + | |||
| + | : 2) seperatly '''MAI''' with the device ordering programmer ('''DOP''') | ||
Both, because in the barcode med administration world, it's not uncommon for a nurse to have a device ordering programmer for the pharmaceutical order. | Both, because in the barcode med administration world, it's not uncommon for a nurse to have a device ordering programmer for the pharmaceutical order. | ||
| − | In all cases, the MAI is the nurse system, then it's the bridge to the PCD domain. | + | * In all cases, the MAI is the nurse system, then it's the bridge to the PCD domain. |
| − | Stay to manage a sufficient content between the 2 domains. | + | * Stay to manage a sufficient content between the 2 domains. Manage Order ID. |
| − | Manage Order ID. | ||
| − | Content of DOC has to be | + | * Content of '''DOC''' has to be sufficient to populate the PHARM-H4 message. |
| − | DEC might be to wide - should IPEC instead. | + | '''DEC''' might be to wide - should '''IPEC''' instead. |
First, speak about the Actors not the specific transactions. | First, speak about the Actors not the specific transactions. | ||
| − | IPEC is very well constrained for infusion pumps. | + | '''IPEC''' is very well constrained for infusion pumps. |
| − | A more constraint version of DEC ? | + | A more constraint version of '''DEC''' ? |
Yes, It's tailored for infusion pumps. | Yes, It's tailored for infusion pumps. | ||
DEC is a framework profile for all kind of monitoring systems. | DEC is a framework profile for all kind of monitoring systems. | ||
| Line 125: | Line 122: | ||
Must get enough information from PHARM-H3. | Must get enough information from PHARM-H3. | ||
| − | Note from Jacqueline : a "mistake" in the dose | + | * Note from Jacqueline : a "mistake" in the dose definition on the top of the slide : it's 'multiply' not 'and'. |
| + | |||
| + | * Update the graphics in the next days, It will before the F2F Meeting next week in the PCD domain. | ||
| − | + | ::* Thierry and Marc propose to investigate further the requirements of the content of messages. | |
| − | + | ::* Marc and Jürgen will review together the slide. | |
| − | |||
Below is the output : | Below is the output : | ||
[[File:PIV-HMW-2.jpg|400px|thumb|center]] | [[File:PIV-HMW-2.jpg|400px|thumb|center]] | ||
Revision as of 17:38, 24 October 2011
Attendees
- Brandstätter, Jürgen (CodeWerk Software Services and Development GmbH, IHE Pharmacy vendor co-chair)
- Cooper, Todd (Breakthrough Solutions)
- Demarmels, Marco (Lake Griffin, LLC)
- Estelrich, Ana (Association Réseau Phast - Phast)
- Géraud, Thierry (CareFusion)
- Peytchev, Vassil (Epic)
- Rica, Charles (ASIP Santé)
- Rinda, Jeffrey E. (Hospira)
- Robberecht, Marc (Agfa Healthcare)
- Sparnon, Erin (Ecri)
- Sprenger, Michiel (Nictiz)
- Surugue, Jacqueline (EAHP, IHE Pharmacy user co-chair)
Welcome and round of introduction
Presentation of the IHE Pharmacy co-chairs :
- Jürgen, Vienna, Austria,IHE Austria co-chair and PHARM vendor co-chair
- Jacqueline, user co-chair, IHE Europe steering committee co-chair
Michiel Sprenger, NICTIZ, sponsor of the domain
Marc Robberecht, working on EHR for AGFA healthcare,
Erin Sparnon, ECRI, PCD domain
Thierry Geraud, working for Carefusion in automation Pyxis domain,France
Charles, physician working for ASIP santé
Vassil, Epic, PCD & PHARM domain
Ana Estelrich, Phast, sponsor of the domain
Jeff Rinda, infusion company, PCD, San Diego, USA
Todd Cooper, PCD
Overview and introduction about the topic
Jürgen discribe the slide presented. Is that correct ?
- Status in PHARM (Jürgen)
Pharmacy transactions are talking to the medication administration informer, behind it's a black box. Need to define the information needed by the medication administration informer, populate the PHARM-4 administration report, with the right data.
- Status in PCD (Todd Cooper)
Discussions engaged in the PCD group^, during the AAMI Medical Device Alarms Summit in Washington D.C. few days ago. 2 ways of getting informations from devices DEC (Device Enterprise Communication) profile (with periodic data about infusion) & IPEC ( with events & rate changes)
Discussion
Todd, for PCD's perspective, want to know what kind of software a medication administration informer can be.
PIV profile is defined to be retricted to a (barecode medication administration) BCMA system.
use case 1
For a pump, there is 2 differents actors :
- the information come from a programmer actor
- and is sent to a consumer actor.
use case 2 (IPEC)
Send to a device observation consumer (for documentation purpose)to produce a flow sheet.
On the US market, sometimes it's the same system and sub-systems, sometimes not. What a medication administration informer can be ?
In many cases, the medication administration informer is an eMAR software (Vassil).
Marc : In the HMW, the system which is registering the administrations, it can be the a medication administration informer , but a nurse too : Manual or automatic entries.
When the BCMA is checking and the pump is started, it's the DEC profile.
DEC is the 'grandfather' of all the integration profiles in PCD. It's less restrictive. IPEC is a very specific infusion pump function.
In DEC,
- The device observation reporter (DOR)is a pump.
- The device observation consumer (DOC)is right behind the Medication Administration Informer(MAI).
Grouping MAI and DOC make sense.
When the BCMA is checking and the pump is started, it's the DEC profile.
2 differents actors grouping :
- 1) MAI with DOC and
- 2) seperatly MAI with the device ordering programmer (DOP)
Both, because in the barcode med administration world, it's not uncommon for a nurse to have a device ordering programmer for the pharmaceutical order.
- In all cases, the MAI is the nurse system, then it's the bridge to the PCD domain.
- Stay to manage a sufficient content between the 2 domains. Manage Order ID.
- Content of DOC has to be sufficient to populate the PHARM-H4 message.
DEC might be to wide - should IPEC instead. First, speak about the Actors not the specific transactions.
IPEC is very well constrained for infusion pumps. A more constraint version of DEC ? Yes, It's tailored for infusion pumps. DEC is a framework profile for all kind of monitoring systems.
Must get enough information from PHARM-H3.
- Note from Jacqueline : a "mistake" in the dose definition on the top of the slide : it's 'multiply' not 'and'.
- Update the graphics in the next days, It will before the F2F Meeting next week in the PCD domain.
- Thierry and Marc propose to investigate further the requirements of the content of messages.
- Marc and Jürgen will review together the slide.
Below is the output :
