Difference between revisions of "Infusion Pump Event Communication"
(st) |
|||
(13 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | + | [[Category:Profiles]] | |
− | + | [[Category:PCD]] | |
− | + | [[Category:HL7v2]] | |
− | + | [[Category:PCD Pages Needing Work]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
__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== | ||
− | + | 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== | ||
− | + | 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. | |
− | + | ==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:''' | '''Actors & Transactions:''' | ||
− | + | [[Image:IPECActorDiagramSmall.jpg]] | |
==Specification== | ==Specification== | ||
'''Profile Status:''' [[Comments| Final Text]] | '''Profile Status:''' [[Comments| Final Text]] | ||
− | |||
− | '''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:''' | ||
− | |||
:* [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]] | ||
− | |||
− | |||
− | |||
− |
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