Design

Information about the design phase for an Vocera Communications EMDAN product implementation.

Design

The following sections define the Key Tasks required to design the solution for implementation.

Clinical Workflow Assessments

Workflow assessments will be conducted to understand the level of impact to the current workflow that this solution will have. In the SOW there will be a paragraph identifying clinical involvement for the project. A Vocera Communications Clinical Consultant will be directly involved with an assessment under the following circumstances:

Patient monitoring integrations

Based on the scope of the project, this could be a rather lengthy process. The Vocera Clinical Consultant will lead the effort of mapping out the desired workflow of the affected departments. During the clinical assessment the Vocera Clinical Consultant will conduct a walkthrough of all units that will be part of the scope of the project in order to understand the clinical workflow for each unit. The Vocera Clinical Consultant will document, with the assistance of your department representatives, whether the existing workflows are unit based or hospital wide. The Vocera Clinical Consultant will incorporate this information into the recommended Vocera Clinical Workflow. This workflow will be documented such that your department representatives can formally sign off on the new workflows. It is important that your department representatives go through the new workflow very thoroughly prior to granting approval to prevent having to reconfigure the application.

Warning: Engage Medical Device Alarm Notification data is designed to manage and notify using a subset of the patient data that is available from the medical device data aggregator and related central station displays. Do not solely use Engage Medical Device Alarm Notification data for patient monitoring.

Warning: Do not rely solely on Engage Medical Device Alarm Notification to indicate medical device alerts. Always continue to monitor patients at primary patient monitors and central station (if applicable) and respond to patient monitor equipment alerts. In these specific examples, Engage Medical Device Alarm Notification may not deliver clinical alert notifications:

A clinician is not assigned to the location.
The mobile device is turned off or the battery is depleted.
The assigned clinician has exited the Unit.
The assigned clinician is logged out of the Vocera application.
The mobile device is not communicating with the Vocera appliance.
The medical device or medical device aggregator is not communicating with the Vocera appliance.
The patient monitor is not communicating with the medical device aggregator.
The patient is disconnected from the patient monitor.

Customize Project Workbook to Accommodate for Unique Customer Needs

Based on your desired workflow, a detailed project plan will be created laying out the necessary tasks to configure the application to meet your needs. The details in the plan for the Vocera Project Manager to consider at this point include: number of alert types, escalation paths per alert type, ring tones, priorities, etc.

Finalize Project Workbook with Timeline

With a detailed project plan in place, the plan will be approved by the key Vocera and Client stakeholders and considered the finalized plan. Any changes to the plan at this point will require additional sign off by your representatives.

Pre-Installation Checklist

The Pre-Installation Checklist will be reviewed with you during the design phase. The importance of gathering the information for each tab of pre-installation checklist is of the utmost importance. The information that is provided in the pre-installation checklist will be used to configure the VM for the site. It will be your responsibility, as the client, to gather and provide the required information to the Vocera Project Manager. The Vocera Project Manager will then review the data with the Vocera Implementation Specialist prior to publishing it.

Remote Access

Remote access to your facility will be provided by your IT department prior to moving to the deployment phase. Some type of remote access must be provided in order for the Vocera Implementation Specialist to access the appliance, finish configuring the server, and prepare for User Acceptance Testing, (UAT). Remote access must also be established for the Vocera Support Department to have a means of accessing the VM to provide technical support once the deployment has gone live.