Philips Intellivue Information Center Configuration

Transcription

1 Philips Intellivue Information Center Configuration This page describes the Phillips IIC and Vocera Alarm Notification adapter configuration for a Vocera Communications EMDAN product implementation. Philips Intellivue Information Center Configuration Philips Intellivue Wizard Options Purchased Options and Support Information Local General Configuration Settings Network Configuration Vocera Configuration for Philips Intellivue Alarm Notification Adapter Configuration AlarmNotification Adapter General Settings Outbound Connection Inbound Connection Preprocessing Rules Message Definitions Philips Alarms ORU-R01 Philips Alarms Invalid Bed ORU-R01 Regular Expressions for Message Definitions Philips Alarms ORU_R01 Messages Philips Alarms Invalid Bed ORU_R01 Messages Conclusion Philips Intellivue Information Center Configuration These instructions assume an existing working configuration for Philips Intellivue Information Center (IIC) with an existing network interface connection on the same LAN as Vocera. For detailed instructions on the configuration of the IIC, refer to the Philips Information Center System Installation and Service Manual. To enable the IIC to send HL7 information to the Vocera appliance, run the Configuration Wizard as referenced in the Information Center System Installation and Service Manual and step through the wizard making updates only in the following areas. Philips Intellivue Wizard Options Follow the instructions below to enable the correct features within the Philips Intellivue Wizard. Purchased Options and Support Information Open the IIC wizard and check the HL7 Export (C14) radio button. Page 1

2 Local General Configuration Settings Open the Local General Configuration Settings tab. Select the HL7 Export Configuration button and follow the instructions below. Network Configuration The Network Configuration screen helps the server identify devices on the LAN. You can add, edit, and remove HL7 devices in the List of Network Devices section of this screen. Page 2

3 Add a new HL7 Export adapter for Vocera with the site-assigned device name and IP address of the Vocera host. Select Next at the bottom of the screen. Select Next. Page 3

4 Equipment Setup Select the Vocera address as the HL7 Target Client from the drop down menu. For the Vocera HL7 Target, select the following Sending Options: Periodic Parameter Type: Select the radio button next to Current. (Philips default parameter is Averaged) Message Type: Select the radio button next to MDIL Coding. Enhanced Fields: Select the radio button next to Production. Send time Messages: Check this box. Post HL7 Disconnect Messages: Check this box. Click Auto Unsolicited, Set Auto Unsolicited On: Check this box. Sending Interval: Select 5. IP Port for Query: This must match the IP port configured for the HL7 AlarmNotification adapter configuration; the default port for the first system in the adapter is If more than one system is configured, then the additional ports for monitors must be configured in the adapter. If you are assigning beds, select the beds in the right column, labeled Available Beds, and select the Assign button. To unassign beds, select beds from the left column, labeled T arget Client(s), and select the Unassign button. Once you have finished assigning the beds, select the OK b utton. Page 4

5 Vocera Configuration for Philips Intellivue These instructions assume an existing working configuration for Philips Intellivue with a network interface connection on the same LAN as Vocera. The Alarm Notification adapter in the Admin Console is configured for a Philips patient monitor system integration by default. The Alarm Notification adapter uses message types to translate the Philips HL7 messages into data that can be combined with available contextual information, such as the patient's name and medical record number, and presented in a message for the caregiver. Enable the Alarm Notification adapter to handle the HL7 messages sent from a Philips monitoring system. See HL7 for additional details about HL7 adapter settings mentioned in this page. To enable the Philips patient monitor to send HL7 information to the Vocera appliance, complete the required setup described below. Alarm Notification Adapter Configuration Navigate to the Alarm Notification adapter and select Edit to update the required configuration information. The default settings for the Alarm Notification adapter are listed below. Page 5

6 AlarmNotification Adapter Reference Name: AlarmNotification Component Name: HL7 Enabled: true General Settings Time Zone: Enter a time zone in order to process dates and times without a time zone. By default, Vocera uses an internal system for this setting. Message Timeout: Enter the amount of time in minutes allowed to elapse between messages. By default, the setting is configured to 1 minute. Report Non-Matching Messages as Audit Events: Check this box to send messages to the audit log. This option can be very useful when troubleshooting, but it is not recommended to be permanently enabled. Outbound Connection Not selected by default. Check this box and complete the settings as required. See the HL7 adapter page. Inbound Connection A configuration is required for the inbound connections to AlarmNotification to be established including an open port and message format. Message Format: ER7 is the default. Select XML if needed. Port: Default is 8000 for Philips (Port 7000 is configured for the Capsule adapter.) Select the desired port number. Acknowledgements on a different port: Check this box if needed and provide the port. See the HL7 adapter page. Process Sequentially: Check this box if messages should be processed one at a time. Page 6

7 Preprocessing Rules One preprocessing rule is defined and enabled by default for NMD messages. While these messages are not used, they are expected to be ill-formed. If NMD messages are not preprocessed and changed, then an audit error message will be generated for each message received. Message Definitions Expand the message definitions to view the configured segments and fields for Philips alarms. All message definitions start from the Clinicals dataset. Philips Alarms ORU-R01 The Philips Alarms ORU-R01 message definition has four default segment definitions: a PV1, an OBR, and two OBX definitions. The dataset mappings of each segment definition are listed in the matrix below. The PV1 segment contains the patient information associated with an alarm. If a PV1 segment is not present in a received HL7 message, it is then matched by the Philips Alarms Invalid Bed ORU-R01 message definition. The OBR segment contains the current time of a received alarm. The two OBX segments contain contextual information of a received alarm. One segment, which is required, contains alarm details. The other segment is not required and contains clinical details. Page 7

8 Philips Alarms Invalid Bed ORU-R01 The Philips Alarms Invalid Bed ORU-R01 message definition has three default segment definitions: an OBR, and two OBX definitions. These segment definitions are identical to the Philips Alarms ORU-R01 definitions and are implemented to catch incoming HL7 messages that do not have a PV1 segment. The dataset mappings of each segment definition are listed in the matrix below. The OBR segment contains the current time of a received alarm. The two OBX segments contain contextual information of a received alarm. One segment, which is required, contains alarm details. The other segment contains clinical details and is not required. Page 8

9 Regular Expressions for Message Definitions The message definitions required for Philips to be configured in the Alarm Notification adapter are shown in the table below. Note that the '^' character in each regex is treated as a literal by the HL7 adapter. Though it would normally have to be escaped, the HL7 adapter will split the string based on the '^' character rather than treating it as the negation of the character class '(.*)' or '(.+)' or anchoring the regex to match the beginning of the string. In the example below, the PV1.3 segment definition is expanded in the adapter's message definition. Page 9

10 Philips Alarms ORU_R01 Messages Page 10

11 Starting dataset: Clinicals Message Location Regular Expression Attribute Mappings Datasets PV1.3 (.*)^(.*)^(.*) bed.room.unit.name=$1 bed.unit.name=$1 bed.room.room_number=$2 bed.bed_number=$3 PV1.39 (.+) bed.room.facility.name=$1 bed.unit.facility.name=$1 bed.room.unit.facility.name=$1 Units Units Rooms Beds Facilities OBR.7 (.+) alarm_time=$1 Clinicals OBX.2 TX OBX.3 (.+)^(.*)^MDIL-ALERT priority_number=$1 alert_type[0]=$1:$2 priority=$2 accepted=no Alerts Clinicals OBX.5 (.+) alert_type[1]=:$1 Alerts OBX.2 (not required) NM OBX.3 (not required).*^(.+) detail_type=$1 ClinicalDetails OBX.5 (not required) (.+) value=$1 ClinicalDetails OBX.6 (not required).*^(.+) uom=$1 ClinicalDetails OBX.14 (not required) (.+) detail_time=$1 ClinicalDetails Philips Alarms Invalid Bed ORU_R01 Messages Starting dataset: Clinicals Message Location Regular Expression Attribute Mappings Datasets OBR.7 (.+) alarm_time=$1 Clinicals OBX.2 TX OBX.3 (.+)^(.*)^MDIL-ALERT priority_number=$1 alert_type[0]=$1:$2 priority=$2 accepted=no Alerts Clinicals OBX.5 (.+) alert_type[1]=:$1 Alerts OBX.2 (not required) NM OBX.3 (not required).*^(.+) detail_type=$1 ClinicalDetails OBX.5 (not required) (.+) value=$1 ClinicalDetails OBX.6 (not required).*^(.+) uom=$1 ClinicalDetails OBX.14 (not required) (.+) detail_time=$1 ClinicalDetails Conclusion This completes the instructions for configuring Philips IIC for an Engage solution. Page 11