PCD Point-of-Care Infusion Verification: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
New page: ''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page. Basically this should be the same sentence that appears on t...
 
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page. Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
The Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Bedside Computer-assisted Medication Administration (BCMA) system to a general-purpose infusion pump.


''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
}}}
__TOC__
__TOC__


==Summary==
==Summary==
{{{2|''<Describe the profile in about a paragraph using user-oriented languageFocus on what it accomplishes for a user (i.e. the Use Cases)Don't get into how it works, leave that to the Details section.>''}}}
 
Point-of-Care Infusion Verification (PIV) brings infusion systems into the electronic medication administration processThe workflow provides for the electronic transmission of infusion information from a barcode-enabled medication administration system (BCMA) to an infusion pump as part of the medication administration processThis reduces the need for manual programming of the pump, and leverages the use of the pump’s onboard drug library to reduce medication errors.


''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''


''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
[http://wiki.ihe.net/index.php?title=Category:PCD_PIV Working Group wiki pages]


==Benefits==
==Benefits==


''<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>''
: Reduces or elminates errors in data entry during pump programming
: Improves patient safety by providing correct medication orders to the right patient at the right time
: Reduces errors in recording the medication administration
: Applies the five rights of medication administration electronically
 


==Details==
==Details==


''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
The goal of the proposed integration is to bring infusion systems into the electronic medication administration process. The following primary steps comprise this process:
 
: Order medication
''<If the user might be familiar with the mechanisms used by the profile, you can mention them hereE.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
: Verify order for inclusion in the eMAR
: Prepare and dispense medication
: Administer medication
While medication errors can occur at each point in this process, this proposal is concerned with the “Administer medication” step, where half of the errors made by clinicians involve infusions.  These errors usually involve a breach of one of the 5 Rights of Medication Administration:
: Right Patient
: Right Drug
: Right Dose
: Right Route
: Right Time
It is the caregiver’s responsibility to ensure that these rights are reviewed prior to administering each drug or starting each infusion.
Because manual programming of the pump may still result in administration errors, this profile was developed to support automated programming the pump, thereby closing the loop between the clinician who uses a BCMA system to verify the 5 Rights and the actual programming of the
pumpThe Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Bedside Computer-assisted Medication Administration (BCMA) system to an infusion pump. This capability will reduce errors by eliminating keystroke errors and by
increasing the use of automatic dosage checking facilitated by the onboard drug libraries in “smart pump” systems. In addition to the reduction of medication administration errors, this integration may also increase caregiver productivity and provide more contextual information regarding infusion data.


''<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.>''
==Systems Affected==
==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.>''
* Infusion Pumps
 
* Electronic Medication Administration Systems
* ''PACS systems may store, manage, and/or display Evidence Documents.''
* EMR, CIS
* ''Display systems may query, retrieve and display Evidence Documents.''
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports


'''Actors & Transactions:'''
Actors and Transasctions
* Infusion Order Programmer (IOP)
* Infusion Order Consumer (IOC)
* PCD-03: Communicate Infusion Order


''<Insert an actor-transaction diagram, and or list of Content Definitions>''
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
Line 38: Line 53:
==Specification==
==Specification==


'''Profile Status:''' [[Comments| Final Text]]
'''Profile Status:''' [[Comments| Trial Implmementation]]  
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''


'''Documents:'''  
'''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.>''
:* [http://www.ihe.net/Technical_Framework/upload/IHE_PCD_TF_Supp_PIV_2-0_TI_2009-08-10.pdf PIV Supplement v2.0 Aug 2009]
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E


'''Underlying Standards:'''
'''Underlying Standards:'''


''<list all the standards on which the profile is based; if possible with links to sources>''
:* [http://ieee.org IEEE 11073]
:* [http://dicom.nema.org DICOM]
:* [http://www.hl7.org HL7]
:* [http://www.hl7.org HL7]
:* ...
:* ...
Line 66: Line 74:
''<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.>''
''<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.''
* ''[[PCD_Profile_DEC_Overview | Device Enterprise Communication]] [DEC]
* ''[[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 [[{{{3|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 [[{{{3|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 [[{{{3|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'''
'''Reference Articles'''
Line 92: Line 85:


[[Category:Profiles]]
[[Category:Profiles]]
 
[[Category:PCD PIV]]
 
[[Category:PCD]]
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
[[Category:{{{4|Templates}}}]]

Latest revision as of 12:31, 10 December 2009

The Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Bedside Computer-assisted Medication Administration (BCMA) system to a general-purpose infusion pump.

Summary

Point-of-Care Infusion Verification (PIV) brings infusion systems into the electronic medication administration process. The workflow provides for the electronic transmission of infusion information from a barcode-enabled medication administration system (BCMA) to an infusion pump as part of the medication administration process. This reduces the need for manual programming of the pump, and leverages the use of the pump’s onboard drug library to reduce medication errors.

<Insert a simple graphic that, at a glance, visually summarizes what the profile is about. Do not use an actor/transaction diagram here. Show your graphic to someone for 5 seconds (literally) and ask them what it's about. If what they say hits the main points in your summary paragraph, you have succeeded. E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>

<See Help - Tips and Tricks for details on inserting an image/graphic.>

Working Group wiki pages

Benefits

Reduces or elminates errors in data entry during pump programming
Improves patient safety by providing correct medication orders to the right patient at the right time
Reduces errors in recording the medication administration
Applies the five rights of medication administration electronically


Details

The goal of the proposed integration is to bring infusion systems into the electronic medication administration process. The following primary steps comprise this process:

Order medication
Verify order for inclusion in the eMAR
Prepare and dispense medication
Administer medication

While medication errors can occur at each point in this process, this proposal is concerned with the “Administer medication” step, where half of the errors made by clinicians involve infusions. These errors usually involve a breach of one of the 5 Rights of Medication Administration:

Right Patient
Right Drug
Right Dose
Right Route
Right Time

It is the caregiver’s responsibility to ensure that these rights are reviewed prior to administering each drug or starting each infusion. Because manual programming of the pump may still result in administration errors, this profile was developed to support automated programming the pump, thereby closing the loop between the clinician who uses a BCMA system to verify the 5 Rights and the actual programming of the pump. The Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Bedside Computer-assisted Medication Administration (BCMA) system to an infusion pump. This capability will reduce errors by eliminating keystroke errors and by increasing the use of automatic dosage checking facilitated by the onboard drug libraries in “smart pump” systems. In addition to the reduction of medication administration errors, this integration may also increase caregiver productivity and provide more contextual information regarding infusion data.

Systems Affected

  • Infusion Pumps
  • Electronic Medication Administration Systems
  • EMR, CIS

Actors and Transasctions

  • Infusion Order Programmer (IOP)
  • Infusion Order Consumer (IOC)
  • PCD-03: Communicate Infusion Order

<Insert an actor-transaction diagram, and or list of Content Definitions>

Specification

Profile Status: Trial Implmementation

Documents:

Underlying Standards:

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.>

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 something. You might be surprised. >


This page is based on the Profile Overview Template