PCD Profile Alarm Communication Management Overview: Difference between revisions
Jump to navigation
Jump to search
m start |
1 |
||
| Line 1: | Line 1: | ||
''Alarm Communications Management (ACM) allows a patient care device to send a notification of an alert or alarm condition to a portable device such as a smart phone''. | |||
''Alarm Communications Management (ACM) allows a patient care device to send a notification of an alert or alarm condition to a portable device such as a smart phone'' | |||
__TOC__ | __TOC__ | ||
==Summary== | ==Summary== | ||
The Alarm Communications Management profile defines an HL7 V2 message for communicating detailed information about an alarm from a patient care device to an information system which then causes a message to be transmitted to a portable device | |||
<!-- | |||
''<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.>'' | ||
--> | |||
==Benefits== | |||
:*Provides a secondary means additional to the primary alarm mechanisms provided by the device itself for notifying the appropriate person of a condition needing timely human intervention. | |||
:*Defines the interfaces needed to mediate between a patient care device and a smart phone or other portable device | |||
<!-- | |||
''<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>'' | ''<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>'' | ||
--> | |||
==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.>'' | ''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>'' | ||
| Line 22: | Line 28: | ||
''<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.>'' | ''<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.>'' | ''<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.>'' | ||
| Line 29: | Line 38: | ||
* ''Display systems may query, retrieve and 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 | * ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports | ||
--> | |||
'''Actors & Transactions:''' | '''Actors & Transactions:''' | ||
| Line 36: | Line 46: | ||
==Specification== | ==Specification== | ||
'''Profile Status:''' [[ | '''Profile Status:''' [[Trial Implementation]] | ||
'''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.>'' | ''<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 47: | Line 57: | ||
:* [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] | ||
:* WCTP | |||
:* ... | :* ... | ||
==See Also== | ==See Also== | ||
| Line 63: | Line 72: | ||
* ''[[Device Enterprise Communications]] [DEC] can transmit the same kinds of notifications to an information system rather than a portable device'' | * ''[[Device Enterprise Communications]] [DEC] can transmit the same kinds of notifications to an information system rather than a portable device'' | ||
<!-- | |||
'''Consumer Information''' | '''Consumer Information''' | ||
| Line 70: | Line 79: | ||
The [[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>'' | The [[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''' | '''Implementer Information''' | ||
The [[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>'' | The [[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''' | ||
''<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]] | [[Category:Profiles]] | ||
Revision as of 21:03, 5 April 2011
Alarm Communications Management (ACM) allows a patient care device to send a notification of an alert or alarm condition to a portable device such as a smart phone.
Summary
The Alarm Communications Management profile defines an HL7 V2 message for communicating detailed information about an alarm from a patient care device to an information system which then causes a message to be transmitted to a portable device
Benefits
- Provides a secondary means additional to the primary alarm mechanisms provided by the device itself for notifying the appropriate person of a condition needing timely human intervention.
- Defines the interfaces needed to mediate between a patient care device and a smart phone or other portable device
Details
Systems Affected
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Trial Implementation
Documents:
Underlying Standards:
- HL7
- WCTP
- ...
See Also
Related Profiles
- Device Enterprise Communications [DEC] can transmit the same kinds of notifications to an information system rather than a portable device
This page is based on the Profile Overview Template