Infusion Pump Event Communication: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Jrhoads (talk | contribs)
editor
1,861 edits
st
 
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<noinclude>
[[Category:Profiles]]
'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''
[[Category:PCD]]
 
[[Category:HL7v2]]
 
[[Category:PCD Pages Needing Work]]
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''


''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
''<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>''
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
</noinclude>
__TOC__
__TOC__


==Summary==
==Summary==
<!--
''<Describe the profile in about a paragraph using user-oriented language.  Focus 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.>''
''<Describe the profile in about a paragraph using user-oriented language.  Focus 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.>''


Line 20: Line 13:


''<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.>''
-->
The PCD 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 Profile Alarm Communication Management Overview | PCD Alarm Communications Profile]]). This allows the pump to report a detailed event flow to another system which needs to display or log the state of an infusion.


==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 Alert 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==


''<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 events are communicated using a controlled vocabulary (see [[RTM | Rosetta Terminology Mapping]]), in a form similar to other device data observation reporting (cf. PCD-01). Data identifying the event itself are typically accompanied by supporting metric information detailed in the Profile description, such as volume infused.


''<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==


''<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.>''
* ''Pump controllers or other data intermediaries with connected infusion pumps may originate IPEC reports''
* ''Electronic medical record systems or specialized device control systems may receive IPEC data streams.''
==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:'''
'''Actors & Transactions:'''


''<Insert an actor-transaction diagram, and or list of Content Definitions>''
[[Image:IPECActorDiagramSmall.jpg]]


==Specification==
==Specification==


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


'''Documents:'''  
'''Documents:'''
* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol1.pdf Volume 1]
* [https://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol2.pdf Volume 2]


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


Line 57: Line 50:
:* [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-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
:* [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://www.hl7.org HL7]
:* [http://www.hl7.org HL7]


==See Also==
==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.>''
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''


Line 92: Line 86:


''<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. >''
''<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]]
This page is based on the [[Profile Overview Template]]
[[Category:Profiles]]
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>

Latest revision as of 16:35, 13 December 2019


Summary

The PCD 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 allows the pump to report a detailed event flow to another system which needs 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 Alert 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

The events are communicated using a controlled vocabulary (see Rosetta Terminology Mapping), in a form similar to other device data observation reporting (cf. PCD-01). Data identifying the event itself are typically accompanied by supporting metric information detailed in the Profile description, such as volume infused.

Systems Affected

  • Pump controllers or other data intermediaries with connected infusion pumps may originate IPEC reports
  • Electronic medical record systems or specialized device control systems may receive IPEC data streams.


Actors & Transactions:

Specification

Profile Status: Final Text

Documents:


Underlying Standards:

See Also

This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=Infusion_Pump_Event_Communication&oldid=119257"