Description of the Solution

The description of the Vocera Communication EMDAN product.

Description of Engage Medical Device Alarm Notification

Vocera Communication's Engage platform is a highly configurable, hospital-wide communication and workflow engine. Engage Medical Device Alarm Notification is designed to deliver event-driven communications across multi-disciplinary teams and physical boundaries.

Engage Medical Device Alarm Notification receives alarms from patient monitors and uses staff assignment information to target the delivery of secondary alert messages for critical alarms to clinician's mobile devices and desk phones (fixed devices). Engage Medical Device Alarm Notification uses admission information to augment alert messages with patient information.

Engage Medical Device Alarm Notification requires the use of a supported nurse call system for real-time staff assignment, an enterprise phone management system to deliver to mobile and fixed devices, and a medical device data aggregator to collect alarm data from patient monitors. For example, a facility may use Rauland-Borg Responder 5, Cisco Unified Communications Manager, and Philips IntelliVue Information Network Database for these respective functions. Engage Medical Device Alarm Notification requires an Admit Discharge Transfer (ADT) feed for patient information to be available with alert messages.

Linking the medical device data aggregator with the local Admissions/Discharges/Transfer (ADT) application and mobile or fixed devices enables a key benefit of the device, context aware communication. The design goal for alert notifications is to enable any user to benefit by not only receiving an alert, but by receiving as much context as feasible (contained within the alert notification message or available via one or two button operations) in order to respond in the most efficient manner to aid the delivery of care.

Clinicians can interact with alerts delivered to mobile or fixed devices through workflows that allow the user to accept, decline, or get additional contextual information for an alert. Administrators can interact with browser workflows to maintain users, devices, and other facility information in the system.

The implementation and installation process is supervised by Vocera’s Professional Service group. A structured consultative approach is used to examine both a customer’s existing workflow practices and stated goals. Any changes to workflow or process re-engineering are reviewed with the customer’s clinical management and implementation team before integrating the Vocera workflow into a customer’s operating environment.

Engage Medical Device Alarm Notification is not intended to replace any part of the patient monitoring system or patient monitoring procedures already existing for the medical devices working with Vocera's Engage Medical Device Alarm Notification.

Manufacturer’s Responsibility

Vocera is responsible for the effects of safety, reliability and performance only if:

System Components

  1. Medical Device
  2. Medical Device Data Aggregator
  3. Health Information System
  4. Vocera Workflow System
  5. Vocera Engage Medical Device Alarm Notification
  6. Smartphone
  7. Fixed Device
  8. Mobile Device
  9. Enterprise Phone Management System
  10. Staff Assignment System

Engage Medical Device Alarm Notification Configuration

All Engage Medical Device Alarm Notification configuration is completed by Vocera staff. Any adjustments must be made and validated by Vocera.

Critical alarms can be different for each unit. The customer determines the list of critical alarms to deliver as alerts.

Alerts can follow up to seven different escalation paths; two of the seven paths are designed to be used with a Monitor Technician. Each escalation path has three escalation steps; primary, secondary, and tertiary. The customer determines the path for each alarm type, the tone for each step, and the delay before the secondary and tertiary steps.

Note: If the facility uses Mirth CAN channels with the EMDAN version 1.8 solution, the 'extension-solutions-mdan-logrotate' RPM must be installed in order to create necessary permissions for a functional logrotate.