Clinical Workflow Engine Configuration Guide

Content
Search
Index
Loading, please wait ...

Loading

  • Vocera Clinical Workflow Engine Overview
  • Installing the CWE Server
    • Vocera Clinical Workflow Engine Requirements
      • CWE Application Server Requirements
      • CWE Database Server Requirements
    • Installing the Prerequisites
    • Verifying Prerequisites
      • Verifying the SQL System Administrator Account
    • Installing CWE
    • Upgrading from CWE 3.0.1
      • Before You Upgrade
      • Upgrading CWE
    • Reinstalling CWE
    • Aborting an Upgrade
    • Working with Rollback after an Upgrade
    • Post-Installation
      • Verifying the Nurse Call Connector Configuration Folder
      • Configuring the Archive Service
      • Creating a Shared Folder for Archive Data
      • Verifying the Monitoring Service Heartbeat Interval
      • Changing the MvisumAlertsAdmin Configuration File
      • Configuring CWE for SSL
        • Enabling SSL in CWE
        • Configuring Vocera Clinical Workflow Engine Console for SSL
  • Configuring CWE Using the CWE Console
    • Configuring Vocera Clinical Workflow Engine Console for SSL
    • Logging into the CWE Console
    • Specifying the Voice Server
    • Importing Vocera Staff Assignment
      • Importing from the Vocera Voice Server
      • Site and Unit Configuration
    • Bed Configuration
      • Creating Beds From Alarms
      • Adding a Bed
      • Bed Field Details
    • Using Roles
      • Adding Roles
      • Configuring Roles
    • Assignments
      • Site Assignments
      • Unit Assignments
      • Bed Assignments
    • Workflow
      • Managing Alarm Reasons
    • Alarm Levels
      • Creating Custom Alert Tones
    • Alarm Enunciation Mapping
  • Viewing Alarms
  • Generating Reports
  • Account Settings
    • Account Settings - General
    • Account Settings - Admin Website
    • Account Settings - Miscellaneous
  • Nurse Call Configuration
    • About Nurse Call Systems and Connector Communication
    • Configuring a Nurse Call Connector
    • Configuring Multiple Nurse Call Connectors
    • Configuring Nurse Call Connector for TAP Message Splitter
    • Configuring Same Unit Name in Different Sites
    • Enabling Callback Numbers for Beds
  • Configuring Email Notifications
  • Configuring Connectors
    • Mirth Connect for Philips
      • Prerequisites
      • Installing Mirth Connect
      • Setting up the Server Manager
      • Launching the Mirth Connect Administrator
      • Configuring Mirth Channels
      • Importing an Existing Channel
      • Deploying the Channel
      • Configuring a New Alarm Reason
      • Configuring a New Alarm Level
      • Including or Excluding the Alarm Parameter
      • Default Ports
    • Mirth Connect for Mindray
      • Overview
      • Processing a Message
      • Acknowledging an Alarm
      • Message Flow
      • Mirth Channels Overview
      • Setting up Mirth Channels
      • Importing and Deploying Channels
      • Configuring a New Alarm Reason
      • Specifying Alarm Priority Levels
      • Configuring Keep Connection Options
      • Changing the Load Balancer IP
      • Changing Connector Type from LLP Sender to File Writer
      • Using Ports
      • Using Transformers
      • Installing CWE and Mirth on the Same Server
    • Mirth Connect for PeraHealth
      • Prerequisites
      • Installing Mirth Connect
      • Setting up the Server Manager
      • Launching the Mirth Connect Administrator
      • Configuring Channels for PeraHealth
      • Importing an Existing Channel
      • Deploying the Channel
      • Default Ports
      • Working of PeraHealth HL7 Alarms
  • High Availability and Load Balancer Configuration
    • Prerequisites
    • Deployment
    • Active-Active Configuration
      • Nurse call system with only one port
        • High Availability
      • Nurse call systems with multiple ports
        • High Availability
      • Applying the Batch File in a High Availability Environment
    • Configuring the NetScaler Load Balancer
      • Configuring the Servers
      • Configuring the Monitors
      • Configuring the Services
      • Creating the Virtual Servers
      • Specifying the Connection Method
      • Specifying a Persistence Configuration
      • Configuring the Nurse Call Connector File
  • Stopping and Restarting Services
  • Troubleshooting Vocera Clinical Workflow Engine
  • Appendix: CWE Configuration Files
  • Legal Notices
  • Download PDF Documentation
  • aborting
    • an upgrade [1]
  • account settings [1]
  • Alarm acknowledging
    • Mindray [1]
  • alarm level
    • specifying [1]
  • alarms
    • creating beds from [1]
    • enunciation mapping [1]
    • escalation tree [1]
    • levels [1]
    • reasons [1] [2]
    • viewing [1]
  • archive data
    • shared folder [1] [2]
  • assignment [1]
  • beds
    • adding [1]
    • adding manually [1]
    • assigning nurses [1]
    • creating from alarms [1]
    • enabling callback numbers [1]
    • field details [1]
  • callback numbers
    • enabling [1]
  • configuration
    • Clinical Workflow Engine [1]
    • nurse call connectors [1] [2]
    • tap splitter [1]
    • unit name [1]
  • connector type
    • changing [1]
  • connectors
    • configuring nurse call [1] [2]
  • console
    • login [1]
    • settings [1]
    • SSL [1]
    • using SSL [1]
  • CWE and Mirth in same server
    • configuring [1]
  • default ports
    • using [1]
  • escalation of alarms [1]
  • groups
    • assignment [1]
    • importing from Vocera Voice server [1]
  • hardware requirements [1]
  • high availability [1] [2] [3]
    • Active-Active mode [1]
    • example [1]
    • NetScaler [1]
      • connection method [1]
      • monitors [1]
      • persistence configuration [1]
      • servers [1]
      • services [1]
      • virtual servers [1]
    • nurse call configuration [1]
    • prerequisites [1]
  • importing from Vocera Voice server [1] [2]
  • integration
    • nurse call [1]
    • patient monitor [1]
  • keep connection option
    • configuring [1]
  • load balancer ip
    • changing [1]
  • logging into the console [1]
  • Message flow
    • Mindray [1]
  • Message processing
    • Mindray [1]
  • Mindray Mirth Connect
    • overview [1]
  • Mirth channels
    • deploying [1]
    • importing [1]
    • Mindray [1]
    • settings [1]
  • Mirth Connect
    • deploying channel [1]
    • importing channel [1]
    • installation [1]
    • launching Administrator [1]
    • prerequisites [1] [2]
    • Server Manager setup [1]
  • MvisumAlertsAdmin [1]
  • new alarm reason
    • configuring [1]
  • normalizer
    • configuring unit name [1]
  • nurse call
    • configuring connector [1]
    • configuring multiple connectors [1]
    • configuring same unit name normalizer [1]
    • integration [1]
  • nurse call system
    • communication protocol [1]
    • multiple ports [1]
    • single port [1]
  • nurses
    • assigning to beds [1]
  • options [1]
  • prerequisites [1]
  • reports
    • generating [1]
  • requirements [1]
    • Vocera Clinical Workflow Engine [1]
  • roles [1]
    • adding or deleting [1]
    • assigning [1]
    • site [1]
    • unit [1]
  • rollback
    • an upgrade [1]
  • service
    • shutdown order [1]
  • settings [1]
    • console [1]
    • general [1]
    • miscellaneous [1]
  • shared folder
    • for archive data [1] [2]
  • shutting down services [1]
  • site
    • configuration [1]
    • roles [1]
  • splitter
    • configuring tap message splitter [1]
  • SQL
    • verifying administrator account [1]
  • SSL
    • enabling [1]
  • staff assignment
    • importing from Vocera Voice server [1]
  • staff members
    • assigning to beds [1]
  • tap message splitter
    • configuring [1]
  • transformers
    • using [1]
  • unit
    • configuration [1]
    • roles [1]
  • Upgrade
    • aborting [1]
    • rollback [1]
  • users
    • importing from Vocera Voice server [1]
  • viewing alarms [1]
  • Vocera Clinical Workflow Engine
    • requirements [1]
  • Vocera Voice server
    • importing from [1] [2]
    • specification [1]
  • workflow configuration [1]