Difference between revisions of "Infusion Pump Event Communication"

From IHE Wiki
Jump to navigation Jump to search
m (start)
m (a)
Line 31: Line 31:
 
==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. If possible, identify benefits that help users and vendors make the business case for the profile.>''
+
This profile permits a receiving system to track in detail the progress of an infusion, including real-time notification of changes in state of the infusion pump. It is distinct from the Alarm Communications Management (ACM); ACM is for notifications to persons of events needing human attention, IPEC sends an event stream to a system. The included events are not limited to abnormal ones.
  
 
==Details==
 
==Details==

Revision as of 15:59, 18 April 2012


Summary

The PC Infusion Pump Event Communication profile provides a means for an infusion system to report events in the course of an infusion (other than alarms which need to be routed for urgent human attention, for which see the PCD Alarm Communications Profile). This is to allow the pump to report a detailed event flow to another system which has a need to display or log the state of an infusion.

Benefits

This profile permits a receiving system to track in detail the progress of an infusion, including real-time notification of changes in state of the infusion pump. It is distinct from the Alarm Communications Management (ACM); ACM is for notifications to persons of events needing human attention, IPEC sends an event stream to a system. The included events are not limited to abnormal ones.

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

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


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:


Underlying Standards:

See Also

This page is based on the Profile Overview Template


<Delete this Category Templates line since your Profile page is no longer a template.>