instructions for use infinity gateway suite...instructions for use – infinity® gateway suite –...

Instructions for Use

Infinity® Gateway Suite

Installation and Setup GuideSoftware VF9.n

WARNINGFor a full understanding of the performance characteristics of this software, the user should carefully read this manual before use.

Instructions for use – Infinity® Gateway Suite – Installation and Setup Guide – VF9.n 3

General Information

General Information

Repairs/Modifications

Modifications of this software should be performed by Dräger-authorized service or organizations, or properly trained technicians. Information about repairs can be obtained from Dräger or authorized service organizations.

Trademarks

The Dräger name and logo are registered trademarks of Dräger.

Infinity®, PatientWatch® (®Europe, not US), and VentWatch® are registered trademarks of Dräger.

Microsoft® Windows Time Synchronization Internet Explorer®, Microsoft®.NET Framework®, Windows®, Microsoft®, Excel®, and SQL Server® are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Safety

4 Instructions for use – Infinity® Gateway Suite – Installation and Setup Guide – VF9.n

Safety

Follow instructions for use

Definitions

Certain paragraphs within these instructions are highlighted as WARNING, CAUTION, or NOTE as follows:

Connections to IT networks

Many medical devices manufactured by Dräger use networks to transmit patient data and to notify clinical users of alarm conditions. Hospitals should refer to IEC 80001-1 before attempting to connect such medical devices to their IT networks.

WARNING

Strictly follow these instructions for use. Any use of the software requires a full understanding and strict observation of all portions of these instructions.The software is only to be used for the purpose specified under Intended Use on page 5 and in conjunction with appropriate patient monitoring. Observe all WARNING and CAUTION statements as rendered throughout this manual, and all statements on product labels.

WARNING

A WARNING statement provides important information about a potentially hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION

A CAUTION statement provides important information about a potentially hazardous situation which, if not avoided, may result in minor or moderate injury to the user or patient or in damage to the equipment or other property.

NOTE

A NOTE provides additional information intended to avoid inconvenience during operation.


Intended use

Intended use

The Infinity Gateway software applications are intended to provide clinicians with the capability of viewing patient data remotely via the Infinity network and for data exchange of select clinical and administrative information between the Infinity network and the hospital network.

Service-oriented device connectivity (SDC)


Service-oriented device connectivity (SDC)

Service-oriented device communication (SDC) defines a connectivity architecture to establish distributed systems of medical devices in clinical environments, for example, high-acuity environments. The protocol is built on the principles of service-oriented medical device architecture (SOMDA) and is modeled after ISO/IEEE 11073. SDC-enabled devices facilitate interoperability across Dräger SDC-compatible products by allowing the request of unidirectional data and/or the remote control of predetermined medical device functionality in a safe manner.


Contents

Contents

General Information . . . . . . . . . . . . . . . . . . . . 3

Repairs/Modifications . . . . . . . . . . . . . . . . . . . . 3Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Follow instructions for use . . . . . . . . . . . . . . . . 4Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Connections to IT networks . . . . . . . . . . . . 4

Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Service-oriented device connectivity (SDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing Infinity Gateway . . . . . . . . . . . . . . . 10

Redundant server . . . . . . . . . . . . . . . . . . . . . . . 10Hosts file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11System requirements . . . . . . . . . . . . . . . . . . . . 12Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Password protection . . . . . . . . . . . . . . . . . . 14Managing user access with group assignments . . . . . . . . . . . . . . . . . . . . . . . . 15DBExport . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Infinity Gateway setup . . . . . . . . . . . . . . . . . . . 16Administrative password. . . . . . . . . . . . . . . 16Configure Alarm History Database . . . . . . . 24

Configuring SDC networks . . . . . . . . . . . . . . . . 26

Supported languages. . . . . . . . . . . . . . . . . . . 29

PatientWatch client applications . . . . . . . . . 29

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 30Patient confidentiality . . . . . . . . . . . . . . . . . 30VentWatch respiratory view . . . . . . . . . . . . 30Auto log on . . . . . . . . . . . . . . . . . . . . . . . . . 31

Client installation . . . . . . . . . . . . . . . . . . . . . . . 31Limiting access to patient data . . . . . . . . . . . . . 31Customizing PatientWatch . . . . . . . . . . . . . . . . 32

Pager access interface. . . . . . . . . . . . . . . . . . 34

Configuring pager access. . . . . . . . . . . . . . . . . 34

Contents


Alarm level settings allowed . . . . . . . . . . . . 38Settings by alarm grade . . . . . . . . . . . . . . . 38Supported paging systems . . . . . . . . . . . . . 40Limiting access to pager control . . . . . . . . . 40

Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Pager control . . . . . . . . . . . . . . . . . . . . . . . . . . 41

System alerts . . . . . . . . . . . . . . . . . . . . . . . 41Page message text. . . . . . . . . . . . . . . . . . . . . . 42

Message formats . . . . . . . . . . . . . . . . . . . . 42Page level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Escalation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Configuring Timing Master . . . . . . . . . . . . . . 46

WinAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 48WvAPI.DLL. . . . . . . . . . . . . . . . . . . . . . . . . . . . 48WvAPITest sample application . . . . . . . . . . . . . 50

Alarm History Database . . . . . . . . . . . . . . . . . 51

File access . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Configuring File Access . . . . . . . . . . . . . . . . . . 53

Protocol handbook. . . . . . . . . . . . . . . . . . . . . 54


Overview

Overview

The Infinity Gateway Server takes advantage of a variety of the Microsoft® Windows® resources. It uses the security features from Local Users and Groups. It outputs errors and information to the Event Viewer Application log. Because it consists of a variety of Windows® services, it automatically restarts on a power cycle even before any user logs into the system. It also uses the Windows® Registry to store configuration data.

Before installing the Gateway Suite, see "Infinity Gateway setup" on page 16. The following applications and interfaces are supported on the Infinity Gateway platform. See "Performance" on page 13 for the limitations on applications that can be enabled on one Infinity Gateway Server.

Application/Interface Description

Infinity Gateway setup An application used to configure the Infinity Gateway Server.

Options program An application used to enable and disable license options in the dongle.

PatientWatch® A browser application used to remotely view patient data (See "PatientWatch client applications" on page 29).

WinAccess A developer's toolkit used to develop custom applications using a variety of data from the Infinity Network.

File access An interface that provides alarm information in text files.

HL7 Vital Signs Export For the Infinity network only. An HL7 interface that exports vital signs information to a clinical information system (CIS).

HL7 Lab Export An HL7 interface that exports laboratory data obtained from a point-of-care laboratory device connected to a patient monitor, to a laboratory information system (LIS).

HL7 Lab Import An HL7 interface that imports laboratory data from a laboratory information system (LIS) and forwards the data to the appropriate patient monitor.

HL7 Alarm Communication Management

An HL7 interface that exports alarm information to a clinical information system (CIS).

ASTM Stat Lab Import Imports laboratory data from a stat lab device. This is connected through a direct serial connection (STAT-Lab serial port connected to Gateway server serial port) or a serial to ethernet connection (STAT-Lab serial port connected to ethernet terminal server, which is then connected to Gateway server ethernet).

Pager access interface For the Infinity network only. A feature that transfers alarm data from a patient monitor to a paging system.

Configuring Timing Master An application that synchronizes the system clocks on all Infinity Network devices to the Infinity Gateway Server clock.

Alarm History Database A group of applications that collects and stores alarm data from all visible beds on an Infinity Gateway Server. Users can create reports of collected alarm data that is accessed by a web page.

SDC Defines a communication architecture to establish distributed systems of medical devices in clinical environments; for example, high-acuity environments.

Installing Infinity Gateway



1 Ensure that the network is properly set up and review the Hosts file. Micronet entry is automatic.

2 Review "System requirements" on page 12 and "Performance" on page 13.

3 Set up users and groups on the Gateway PC. See "Managing user access with group assignments" on page 15.

4 Optionally, ensure the terminal server is set up according to device documentation in order to connect to remote Stat Labs for ASTM HL7 Lab Import interface.

5 Optionally, setup a web server to use PatientWatch.

6 Run setup.exe from the Gateway. This installs all of the Gateway features, including the server, PatientWatch, etc. and opens "Infinity Gateway Setup" (see page 16).

7 If you purchased PatientWatch user licenses, set up a user group (see "Managing user access with group assignments" on page 15) for each care unit on the Infinity network for which you want to limit access. See "Limiting access to patient data" on page 31 for more information.

8 If you purchased WinAccess and have a custom application that uses WvAPI.DLL, rebuild your application using the latest h-files.

9 If you purchased Alarm History Database, set up a user group to allow users to login to the Alarm History Database web application. See "Group Assignments" (see page 15).

10 Dräger has tested compatibility of the Infinity Gateway Suite with McAfee Virus Scan Enterprise 8.8.

11 Prior to installing any Microsoft Hot Fixes and Microsoft product service packs, please contact your local Service Representative to ensure compatibility with Dräger IT products.

Redundant server

Gateway supports the use of an optional redundant server. This is a licensed option. It allows a separate server to be configured in advance which can temporarily replace a failed Gateway server. An administrator performs the switchover manually by powering up or enabling the Gateway service on the redundant server.

To configure the redundant server:

1 Duplicate the installation of Gateway on 2 systems.

2 Enable the Temporary Software License option on the redundant system.

CAUTION

Dräger strongly recommends the use of an anti-virus program. The use of an anti-virus program is recommended for the Infinity Gateway Server and all client PCs.



3 Remove the dongle from the redundant system and turn the Gateway services off or power down the system until needed.

4 Reconnect the dongle to the primary Gateway server.

Hosts file

The Infinity Gateway Server PC requires a micronet entry in the Windows Hosts file. In conjunction with an existing network, this entry is created automatically.

If a network has not been setup prior to installation, the micronet entry must be configured manually. Additionally, if the IP address is modified, you must update the Hosts file.

Microsoft typically places the Hosts file located in the subdirectory:

C:\Windows\system32\drivers\etc\hosts

Open the Hosts file and add the following entry:

<IP ADDRESS> micronet where <IP ADDRESS> represents the IP address of the network card in the Infinity Gateway Server PC that is connected to the Infinity network.

NOTE

After powering-up or enabling the Gateway service on the redundant server, the enabled options will operate for a maximum of 72 hours without the dongle connected.

NOTE

In order to save the Alarm History, HL7 ADT, and HL7 Lab databases, you can set up a remote SQL database with both Gateway servers pointing at it.



System requirements

PC system requirements

Infinity Gateway Server PatientWatch and Alarm History Database

Operating system Windows Server 2016 Standard, Microsoft.NET Framework 2.0 or Microsoft.NET 3.5, and SQL Server 2017 Express or Standard, with the latest service pack

Windows Server 2016 Standard or Windows 10 64-bit, with the latest service pack

CPU Intel Xeon or better, 3.00 GHz or better 2.00 GHz or better

Storage 500 GB, minimum 250 GB, minimum

Memory 16 GB RAM, minimum 4 GB RAM, minimum

Video 1024 x 768 or better, 256 colors minimum 1024 x 768 or better, 256 or more colors

USB Ports 4 x USB 2.0 ports minimum (one dedicated for Dräger S/W license key)

Not applicable

Ethernet – Type: Ethernet 1000Base-T, Ethernet 100Base-TX

– Recommended Data Transfer Rate :1 Gbps (Needed for SDC)

– Compliant Standards :IEEE 802.3

PCI bus

CD-ROM drive or DVD ± R drive

Any available type Not applicable

Uninterruptible power supply (UPS) (optional)

Recommended to ensure continuous operation during power loss, and to protect the system from power line disturbances

Not applicable

PatientWatch runs in a browser and requires Internet Explorer11. Internet Explorer must be configured on each client to download signed ActiveX controls and run ActiveX controls and plug-ins. To configure, go to Control Panel>Internet Options>Security.

Requires a Windows-based web server on which the application can be installed. See the Gateway installation instructions for details about installing a web server on the Infinity Gateway Server PC.

NOTE

Client devices using an upgrade from Microsoft from Windows 7 to Windows 10 have been found to have some technical issues with Patient Watch. We recommend using a complete Windows 10 installation to support the Patient Watch feature of Infinity Gateway.



Performance

With the minimum system requirements, the Gateway Server can support up to 128 Infinity patient monitors in up to 16 monitoring units, or up to 64 SDC devices, or a combination of Infinity and SDC devices that does not exceed 256 or Usage points as defined below:

Sample configuration

In this example, an Infinity Gateway Server is connected to an Infinity Network with 90 patient monitors. Using these parameters, you can configure:

Application/Interface Usage points

PatientWatch One per concurrent connection (maximum 96 devices/points)

File Access Two per source device

HL7 ADT interface Two for solicited, eight for unsolicited

HL7 Vital Signs Export (interval of one minute or more)

Two per Infinity deviceThree per SDC device (Max 64 SDC devices)

HL7 Vital Signs Export (interval of less than one minute)

Six per source device (Max 32 SDC devices)

HL7 ACM Three per SDC device (Max 64 SDC devices)

HL7 Lab Export Two

HL7 Lab Import Two

ASTM Stat Lab Two

WinAccess API Two per Infinity device

Three per SDC device (Max 64 SDC devices)

Pager Access Two per Infinity device (maximum 32 devices/64 points)

Alarm History Database Four per Infinity device

Service Connect Ten

Component Qty Usage points each

Total usage points

PatientWatch client connections 64 1 64

HL7 Lab Import 1 2 2

HL7 ADT interface-unsolicited 1 8 8

ASTM Stat Lab interface 1 2 2

HL7 vital signs interface(1minute or more interval with Infinity devices only)

90 2 180

Total Usage Points 256



Security

The Infinity Gateway suite uses the following mechanisms to protect its applications:

Standard password protection of various applications.

See "Managing user access with group assignments" on page 15 to further limit accessibility within applications.

See "Administrative password" on page 16 to protect the Infinity Gateway Setup application.

A configurable session timeout and associated browser message for the Alarm History Database client (see page 24) to support US government requirements for security hardening.

A configurable US Information System Disclaimer screen at login for a hardened Gateway server and Alarm History Database client (see page 24) to support US government requirements for security hardening.

Password protection

When an Infinity Gateway application prompts the user for a username, password, and domain, the credentials are validated on the Infinity Gateway server PC.

Any user name, password, and domain combination that is known by the Infinity Gateway server PC is considered valid, regardless of the attached privilege level, except when using Auto Log On, which requires all users to be members of the Windows User group.

All client applications and the Pager Control Configuration screen are password-protected using standard Windows mechanisms.

CAUTION

If your application requirements exceed the allowed 256 points, you may notice a decrease in performance, and you may need to install a second Infinity Gateway.

NOTE

– Although the Infinity Gateway Setup Application is password-protected, it uses a proprietary non-Windows password validation (as does the DBView tool).

– When Auto Log On is enabled, the user is not prompted for user name, password, and domain name as long as the useris logged on to the client PC with a domain user name; instead, the credentials used to log on to the client PC are automatically sent to the server PC for authentication. See "Auto log on" on page 31.



Managing user access with group assignments

About creating groups and assigning users

Creating user groups and assigning users to these groups is a way to manage user access, as permitted in a Windows environment, Infinity Gateway applications use the groups to to determine if a user has access privileges to certain environments.

Groups used by Infinity are local groups; however local groups can contain domain groups. Using a domain group, a domain administrator can grant access to all Infinity Gateways on the network simultaneously. For example:

A site has 3 Infinity Gateway PCs with Pager Access enabled.

A domain group called Pager was created. On each server, the locally defined PagerConfig groups contain the domain group Pager. Adding a user to the Pager domain group is the equivalent of adding a user to the PagerConfig group on all of the Gateway servers.

Managing user access

Client access

The Infinity Gateway supports 3 levels of limited access to patient data for the client applications. To configure access restrictions, see:

"Limiting access by care unit" on page 31

"Limiting access to patient names" on page 32

"Limiting access to demographic data" on page 32

Member access

Members of certain groups have access to certain environments, while non-members do not have access. This rule applies to the groups:

PagerConfig- members have access to Pager Control Configuration

AlarmHistory- members have access to the Alarm History Database

CAUTION

Only users with administrative privileges can create groups and assign users to them. For more information, see the Windows online help.

CAUTION

Groups are read at system startup and refreshed once per hour. Group changes may take up to one hour to take effect.



DBExport

The DB Export utility is standard with the Infinity Gateway. It exports the contents of all Gateway database tables while stripping various pieces of demographic data from the tables. The utility is for customers who need troubleshooting assistance and need to send data to Dräger for analysis.

Infinity Gateway setup

The Infinity Gateway Setup program lets you:

Configure Infinity network monitoring units (see page 21)

Configure SDC network locations to monitor (see page 26)

Configure network information (see page 23)

Select, enable/disable, and configure options

Administrative password

After installing Infinity Gateway Setup, you are required to create a password.

To change your password, right-click on the main title bar, select Change Password and follow the prompts

If you forgot your password, contact your local Dräger-authorized service representative for more information.

NOTE

DBExport does not remove the contents of Patient identifier fields.

CAUTION

If you forget the password, you will not be able to run the Infinity Gateway Setup application.



Dräger Infinity Gateway setup menu



In the setup dialog, options that are not yet enabled in the USB key are inactive. The following options are available:

Option License required

Description

User Licenses Yes Licenses for PatientWatch Client Applications are sold individually (see page 29).

Patient Confidentiality No When enabled, limits access to patient data in any client application (at least 1 PatientWatch enabled license is required) See "Limiting access to patient data" on page 31.

VentWatch® Respiratory View Yes Enables access to the VentWatch screen in PatientWatch; see "PatientWatch client applications" on page 29 (at least 1 PatientWatch-enabled license is required).

Auto log on No Configures the PatientWatch client to attempt to automatically log the user on to the Gateway server using the credentials entered when the user logged on to the client PC.

Configure WinAccess Yes Configures third-party applications to connect to the Infinity Gateway Server using WvAPI.DLL or using socket messages.

Configure File Access Yes Configures Vital Sign Output.

Configure HL7/ASTM Interfaces

Yes Configures HL7/ASTM Interface Options.

Configure ASTM Interface Yes Configures the ASTM Stat Lab Interface.

Configure Pager Access Yes Configures the Pager access (see page 34).

Configure Timing Master Yes Controls system time synchronization either once or twice per day at configurable times with minute-resolution.

Configure Alarm History Database

Yes Provides the configuration settings for the Alarm History Database (see page 24).

Configure SDC Yes Provides the configuration settings for SDC (see page 26).

Event log ePHI No Forces all services to obfuscate ePHI data (Electronic Protected Health Information) in the application event log entries written into Event Viewer.



Selecting and enabling license options

USB key

To run the Infinity Gateway Server, a USB key is inserted into the Infinity Gateway Server PC. Each USB key maintains information about which license options are enabled and has a unique Option Device Serial Number that displays on the Dräger Infinity Gateway Setup screen. Licensed options are activated using passwords provided to the customer when the option is ordered.

License options are stored permanently in the USB key, unless they are manually disabled by the user. The USB key makes it easy to transfer valid license options from one PC to another, if necessary.

If a Temporary Software License is enabled, and a license key is connected to a server, then all enabled options on that key will be stored. After removing the key, the enabled options will have a maximum of 72 hours run time.

Enter monitoring unit ID(s) to listen to

N/A This field contains a comma separated list of monitoring units that the Gateway listens to. See "The above field describes which monitoring unit(s) the Infinity Gateway Server PC listens to. Monitoring units are specified by numeric IDs." on page 21.

Advertise across monitoring units

N/A When enabled, the Gateway can be configured to be seen by patient monitors in monitoring units outside of its own, even when the bedside monitor is not attached to a Central Station. See "When the Gateway listens to a monitoring unit, it is aware of all Infinity patient monitors that are configured in that monitoring unit, and it allows for the availability of this data for the Gateway applications." on page 21.

Configure Monitoring Units N/A This button is available only when Advertise across monitoring units is enabled and lets the user configure the details of the advertisement.

Enter network information for this Gateway

N/A See "Network Information" on page 23.

Configure Database User N/A Sets database username, domain, password, and SQL database named instance.

CAUTION

Only one dongle can be used on an Infinity Gateway Server at a time. When ordering a new license option, the serial number of the USB key must be supplied. Each option password applies to one USB key.



On the USB key, PatientWatch licenses are sold individually or in variable size groups. A customer can order six, for example, and one password enables access to all six. Later the customer can decide to buy three more and another password is provided for access to the additional three.

Options program

Licenses are activated in the Options program, which is available from the menu in the title bar of the main dialog of the Infinity Gateway Setup.

Infinity network

NOTE

The Gateway only supports the green (HASP HL) USB key.

NOTE

The program is also available from the Start menu; however, any options enabled while the Infinity Gateway Setup is running are not detected by that program unless the Options program is accessed directly from the menu on the Infinity Gateway setup.



The above field describes which monitoring unit(s) the Infinity Gateway Server PC listens to. Monitoring units are specified by numeric IDs.

When the Gateway listens to a monitoring unit, it is aware of all Infinity patient monitors that are configured in that monitoring unit, and it allows for the availability of this data for the Gateway applications.

More than one Infinity Gateway Server can reside on an Infinity Network. For example, if monitoring units one, two, three, and four are on an Infinity network, an Infinity Gateway could be set up to listen to monitoring units one and two, and another one to listen to monitoring units three and four. See "Performance" on page 13" for more information."

Advertise across monitoring units

Every device on the Infinity network advertises itself in its own monitoring unit using a proprietary multi-cast (UDP) protocol. These advertisements are the basis of the Infinity network and allow devices to know of the existence of other devices in a monitoring unit by listening to these advertisements. Each advertisement must include an Infinity domain name which is comprised of the following:

Host label

Care unit label

Monitoring unit label

Hospital label



Some Dräger devices, such as the Gateway and the Central Station, listen to more than one monitoring unit. Patient monitors, however, only listen to their own monitoring unit.

To support the Get From HIS functionality, a patient monitor or Central Station must know of a Gateway that supports ADT. Since the patient monitor cannot see outside of its own monitoring unit directly, a mechanism was developed where a patient monitor could request this information from a Central Station. However, some patient monitors have no Central Station to request this information from.

Advertise across monitoring units allows the Gateway to be configured such that it advertises in various monitoring units, in turn allowing patient monitors that do not have access to a Central Station to have the Get From HIS functionality.

The LAB Export functionality at the patient monitor uses the same mechanisms as Get From HIS and so this feature also makes that functionality more easily available at patient monitors.Configure Monitoring Units

From the Infinity Gateway Setup screen, click Configure Monitoring Units to access the Define Monitoring Unit Labels dialog.

Column Description

Unit# The monitoring unit number.

Listen A check mark indicates whether the monitoring unit should be listened to.

Label Contains the monitoring unit label to be used in the advertisement. All other components of the Infinity domain name used in the advertisement are identical to those defined in the Network Information section of the main screen. This field is grayed out if the Advert check box is not enabled.

Advert A check mark indicates that the Gateway should advertise in that monitoring unit.



Network Information

This section of the Infinity Gateway Setup screen contains information that the Infinity Gateway Server PC uses to advertise itself on the Infinity Network.

NOTE

– The Gateway must advertise in at least one monitoring unit (the primary unit defined in "Network Information" on page 23).

– A default monitoring unit label is automatically supplied when the user checks the Advert check box for any entry, but that monitoring unit label can be changed by clicking in the appropriate column for that entry. The monitoring unit label must match the monitoring unit label that other devices in the same monitoring unit use.

– Making changes to this dialog may change the contents of the Enter monitoring unit ID(s) to listen to setting in the main dialog.

Option Description

Monitoring unit ID: Identifies the monitoring unit that the Infinity Gateway Server resides on

Host label: Name of host machine

Care unit label: Identifies the care unit label that the Infinity Gateway Server resides on

Monitoring unit label: Identifies monitoring unit label for the Infinity Gateway Server

The monitoring unit ID label must match the monitoring unit label that other devices in the same monitoring unit use. When Advertise across multiple monitoring Units is enabled, this field is grayed out and is controlled via the Configure Monitoring Unit button.

Hospital label: Location of Infinity Gateway Server



Configure timing master

When the Act as Infinity Network Timing Master box is checked, the Gateway controls system time and sends a time synchronization message to the Infinity network to set the time of all Infinity monitoring devices to the Gateway time. Synchronization messages can be sent up to twice per day.

Event log ePHI

This setting causes all services that write log entries into the Event Viewer Application log to mask or obfuscate all ePHI (Electronic Protected Health Information) data in much that same manner as PatientWatch does for a user that is a member of the Hide Demographics group. See "Limiting access to demographic data" on page 32.

Configure Alarm History Database

NOTE

The Alarm History Database applies only to devices on the Infinity network.



The following table discusses settings that apply to Alarm History data and USG security hardening requirements:

Setup Validation

The Infinity Gateway Setup checks extensively for errors, including:

Ensuring that there are no port conflicts among configurations.

Verifying that required directories have been created.

Verifying that settings without default values have been configured.

Error-checks are performed when OK is clicked on any of the dialogs.

Option Settings Description

Save Alarm History for 0-52 weeks

(default: 28 weeks)

Allows the collection of alarm data from the Infinity network for configured monitoring units

Certificate thumbprint default: blank Sets the Alarm History server’s certificate identifier ("thumbprint") used for service authentication

For information regarding how to obtain this identifier, see the Gateway Software Installation Instructions, "Configure Alarm History GUI for SSL."

Timeout session after 0-60 minutes

(default: 0 which disables the timeout feature)

Sets the time the user is logged off the client session due to inactivity.

This timeout feature applies to the Alarm History Database application. See the Alarm History Database instructions for use.

Warn after 0-59 minutes

(default: 0 which indicates disabled)

Sets the time a warning message displays to the user at the bottom of the client browser before the session timeout occurs.

This warning message applies to the Alarm History Database application.

Enable USG IS Disclaimer

Default: unchecked Sets the display of a US Government Information System Disclaimer window at logon.

This feature applies to the Alarm History Database application. For more information about this window, seethe Alarm History Database instructions for use, "For US government users".



For example, if the File Access directory specification references a non-existent directory, when you click OK on the main screen of the Infinity Gateway Setup, a notification appears indicating the File Access settings must be checked. After you enter that dialog and click OK, the directory is created.

Clicking OK at any dialog causes the system to validate all settings and notify the user of any invalid settings. Clicking cancel, however, discards all setting changes and does not validate existing settings.

Settings are not saved until OK is clicked on the Main dialog.

Configuring SDC networks

The SDC interface lets you listen to devices over the SDC network. This interface is installed automatically during Infinity Gateway installation, but the option must be purchased, enabled and configured via the Options program.

To configure SDC:

1 Open the "Dräger Infinity Gateway setup menu" on page 18.

2 Click the SDC checkbox to enable SDC.

3 Click Configure SDC.

4 Refer to "Configure SDC settings" on page 28 to fill out the Configure SDC dialog.

NOTE

The user is encouraged to click OK even when no settings have been changed in order to validate the settings.



NOTE

The NTP Server can be activated on the Operating System where the product is deployed.



Configure SDC settings

NTP Server Name The name of the NTP server to use for time synchronization for SDC devices.

Address The IP address of the NTP server entered in the name field.

Enable time configuration Master

Controls whether or not the Infinity Gateway sets the NTP information on visible SDC devices.

SDC Network Network Card The friendly names of the available network cards are available in the drop down. The network card selected will be the one used for SDC communication on the Infinity Gateway.

Infinity Gateway Server Name The name of the Infinity Gateway Server.

Configured locations Facility The facility that the Infinity Gateway will be configured to listen to.

Point of care The Point of Care unit that the Infinity Gateway will be configured to listen to. If this is left blank then all Point of Care units will be listened to under configured facility.

Bed label The bed label that the Infinity Gateway will be configured to listen to. If this is left blank then all bed labels will be listened to under configured point of care, or facility.

Certificate Handling Certificate Storage

The location where the Infinity Gateway certificate secure storage shall be stored.

Export CSR Generates a Certificate Signing Request in the configured location.

Import Certificate Once a certificates is created from the CSR the certificate will be imported using the Import Certificate button.

Show Certificates Displays the issue date and time and the expire date and time of the current certificate.

Process data meant for informational purposes only

Enables the processing of data marked at informational class. By default data marked as informational is ignored when received from an SDC device.


Supported languages

Supported languages

The Infinity Gateway supports the following languages for the PatientWatch, PagerControl, and Alarm History Database applications.

Danish

Dutch

English

Finnish

French

German

Italian

Norwegian

Polish

Portuguese (Brazilian)

Russian

Spanish

Swedish

PatientWatch client applications

PatientWatch is a password-protected client application that lets the user view data available at the Infinity patient monitor from a remote platform. The PatientWatch applications are available at an additional cost. License and standard options allowing up to 96 simultaneous client connections per server are available. However, only four clients can be run simultaneously from one PC. See "Selecting and enabling license options" on page 19.

See "System requirements" on page 12 and "Client installation" on page 31 for more information on the platform and installation requirements of the different types of client applications.

PatientWatch Features

Running waveforms

Parameter values

Trends (tabular and graphical) (Infinity only)

Trend export to a file that can be easily imported into Microsoft Excel (for users that are not members of the Hide Demographics group)



Ventilator loops, parameters and settings (with VentWatch option)

Dynamic window resizing capabilities

Modem access with remote networking

Password protection of patient data (see "Limiting access to patient data" on page 31)

Supports Gateway Patient Confidentiality option (see "Limiting access to patient data" on page 31)

Supports multiple Infinity Gateway servers

Visual alarm indication (Infinity only)

Limiting Access to Demographic Data

Automatic "Client installation" on page 31

Can be interfaced to hospital application (see "Customizing PatientWatch" on page 32). For more information, see the PatientWatch online help.

Configuration

Patient confidentiality

This setting enables or disables the ability to display patient names in PatientWatch.

VentWatch respiratory view

This license option is available when at least one PatientWatch client license option has been purchased. See "Selecting and enabling license options" on page 19 for more information. When enabled, this setting causes PatientWatch to display a Vent tab when the patient monitor being viewed has a ventilator connected.

NOTE

Patient Watch only needs to be installed on one ONE IIS server, regardless of how many Infinity Gateways are installed in the hospital with PatientWatch enabled. During installation, the user is prompted to enter the IP addresses for all Gateway servers, including redundant servers. Once configured, all of the servers are accessible through the one PatientWatch IIS installation.

NOTE

Dräger does not supply Microsoft licenses for server or client PC systems used with Dräger products. Consult your IT department and Microsoft to determine what licenses you should use.



Auto log on

This feature lets the PatientWatch client automatically log-on to the Gateway using the Windows user name, password and domain name of the client PC. Auto Log On succeeds if:

The setting is enabled

The user has logged on to the client PC using a domain user name

The domain user name is a member of the user group on the Gateway server PC

If the 3 criteria above are met, the user on a client PC starting PatientWatch is not prompted to log on and a patient selection dialog appears immediately.

Client installation

PatientWatch is a browser enabled application that is installed on one Windows web server PC. The application consists of ASP pages, an ActiveX control, and a server-side component. When the appropriate URL is accessed by the client, the signed ActiveX control is automatically downloaded (as needed) to the client PC. It requires Internet Explorer version 11, as well as a web server. PatientWatch can be installed on an existing Windows-based hospital web server, or a new web server can be installed on the Infinity Gateway PC.

Limiting access to patient data

Limiting access by care unit

Before a PatientWatch user is granted access to patient data, the user's credentials must be authenticated on the Gateway Server (see "Password protection" on page 14).

The user is then presented with a directory of all patient monitors in all of the care units that the user has access to. A user has access to a care unit if:

A group with the same name as the care unit does not exist.

A group with the same name as the care unit exists, and the user is a member of that group; see "Managing user access with group assignments" on page 15.

NOTE

Whenever the Infinity Gateway software is upgraded, all PatientWatch or WinAccess clients must be re-installed with a matching software version.



Example:

The network consists of the following care units:

CU1,CU2,CU3

Group CU1 is defined and has users Jones, Smith and White assigned. Group CU3 is defined and has users McGrath and Smith assigned. Group CU2 is undefined.

When user Jones logs on to the server from a client, the list of devices includes all patient monitorsand therapy devices in care units CU1 and CU2. User Smith, however, has access to all devices on the network.

Limiting access to patient names

If "Patient confidentiality" on page 30 is enabled on the Infinity Gateway Setup screen, all PatientWatch applications accessing the server disable the display of patient names on the main screen. Also, the patient directory displayed at the client will contain only patient identifiers to identify the patients that are admitted to the patient monitors.

Limiting access to demographic data

If a particular user is a member of a special group called Hide Demographics (see "Managing user access with group assignments" on page 15), PatientWatch also limits access of the user to all demographic data.

When a user that is a member of this group logs on to PatientWatch, the directory presented to the user contain obfuscated patient names and identifiers. For example, if the patient John Smith has an identifier of 123456789, that patient's name appears in the directory as "J*** S***" and his identifier as "***789".

Customizing PatientWatch

The standard PatientWatch installation requires a user to log on to the server and select a patient. Access to patients can be limited on a care unit-by-care unit basis. Customize PatientWatch to:

Tie PatientWatch into an existing hospital web page

Achieve single sign-on

Limit access to patients within a care unit

When PatientWatch is installed on the web server PC, the user is prompted to install an index page on the web server. This index page, if installed, invokes the main PatientWatch asp page, with no arguments:

C:\INETPUB\WWWROOT\WEBVIEWER\GATEWAY\FRAMESET.ASP

To customize PatientWatch, create a default page rather than installing a default page.There are three types of PatientWatch installed on your system:



C:\INETPUB\WWWROOT\WEBVIEWER\GATEWAY\FRAMESET.ASPThis page is used by the standard PatientWatch installation. It supports dynamic window resizing. It can display one patient's data at a time.

C:\INETPUB\WWWROOT\WEBVIEWER\EXPLORER\FRAMESET.ASPThis page is used by the Infinity Explorer when 1 x 1 panel is configured. It does not support window resizing. It can display one patient's data at a time.

C:\INETPUB\WWWROOT\WEBVIEWER\EXPLORER\FRAMESET4.ASPThis page is used by the Infinity Explorer when 2x2 panel is configured. It does not support window resizing. It can display four patient's data at a time.

The installation includes several files to assist in customizing PatientWatch:

The C:\INETPUB\WWWROOT\WEBVIEWER directory contains sample pages that prompt the user for login information and then redirect the page, using arguments to the WebViewer.asp pages. Some of the samples use the Gateway page above, while others use the Explorer pages. Some of the samples show external patient selection, while others invoke the PatientWatch pages without patient context, letting the user select the page through the standard dialog.

PatientWatch is installed with a component called Map2Server.dll. This component provides a mechanism by which your page can access PatientWatch by specifying a patient identifier and login information. The page finds the patient across multiple servers and logs you on to the appropriate Infinity Gateway server for the desired patient. The sample web pages mentioned above show how this component can be used within your page.

See "Protocol handbook" on page 54 for more details.

Pager access interface



The Gateway Pager Interface (Infinity only) is an application that can be configured so that a page is sent to a care provider when a patient monitor goes into alarm (includes telemetry).

Configuring pager access

To configure Pager Access:

1 Open "Infinity Gateway setup" on page 16.

2 Enable the Pager Access check box.

3 Click Configure Pager Access. The following dialog appears:

Option Description

Configuration A Gateway Setup screen that configures settings relating to communication with the paging system, policies, and global settings for the Pager feature.

Pager Service A Windows service that listens to the network and sends pages to configured pagers for configured patient monitors in alarm. The Pager Service also makes entries in the event log.

Pager control A Windows application that provides status feedback for the Pager Access Interface as well as the ability to configure beds and pagers.



Option Description

Infinity Gateway

Server Name Name of the Infinity Gateway server

PagerControl Service Port Service port used to communicate with the Pager Control application

Identify Patient by

Identifier or Name Controls how the patient is identified within PagerControl

Protocol

ESPA or TAP Identifies the protocol used to communicate with the paging systemThe Infinity Gateway supports both ESPA 4.4.4 and TAP 1.7

Pager Communication

Serial or TCP/IP Identifies the pager communication type.

TCP/IP Communications Settings

Pager System IP Address Pager IP Address

Pager System Service Port Service Port number

Serial Communication Settings

Serial Port: Serial port number to be used

Baud Rate Baud rate for the connection (settings vary from 300 to 19200 baud)

Start Bits Number of start bits (1 or 2)

Data Bits Number of data bits (7 or 8)

Stop Bits Number of stop bits (1 or 2)

Parity Mark, None, Even, Odd, or Space

Retry Number of retry attempts when communication fails

Character mapping

Enable Mapping Causes the outgoing pager message to be transformed using the defined character mapping before it is sent to the paging system. Refer to the Character Mapping section in the HL7 Reference guide for more information.

Selected Map The name of the character mapping to be applied. This is a read-only field; the character map is defined using the Edit/Select map button

First Code to Map This is a read-only field that indicates the minimum value of the Unicode character code that can be mapped on this interface.



Default Value Defines the replacement single-byte string that should be used for all Unicode characters in the page message that are not defined in the character map.

Edit/Select map Displays the Character Mapping Editor dialog.

Global Settings

Page Message Format Format of the output message

Maximum message size Maximum number of characters in message sent to the pager system

Alarm Level Settings Allowed Controls which Page Level settings are available on the Pager Control application

Delay Setting Allowed Controls whether a delay can be configured

Escalation Pager Number Pager number to use when escalation occurs

Escalation Count Number of consecutive pages, without intervening non-alarm states, before escalation occurs for any patient monitor

Include All Vent Alarms Enables/disables use of ventilator alarms

Settings by alarm grade

(settings vary) Various settings on an alarm grade basis

Miscellaneous

Set Default Values Resets all settings to default values for current protocol

CAUTION

When a serial port is used, it should be configured using standard Windows tools to disable any kind of flow control. If, for example, XON/XOFF flow control is enabled on the serial port, then some pages may never reach the paging system due to the presence of the XON or XOFF characters in the message.



Alarm level settings allowed

The care provider sets the "Page level" on page 44 for each patient monitor on the Pager Control main screen. The Alarm Level Settings Allowed setting on the Configure Pager Access dialog determines the choices that are given to the care provider, as follows:

Settings by alarm grade

Alarm Level Settings Allowed

Page Level Settings Available on Pager Control

ADV Advisory: All alarms will be paged

ADV, SER Advisory: All alarms will be paged

Serious: All alarms will be paged

ADV, SER, LT Advisory: All alarms will be paged

Serious: All alarms except advisory alarms will be paged

Life threatening: Only life-threatening alarms will be paged

ADV, SER, LT, OFF Advisory: All alarms will be paged

Serious: All alarms except advisory alarms will be paged

Life threatening: Only life-threatening alarms will be paged

OFF: No alarms will be paged

NOTE

Some settings are not available with the Telocator Alpha-numeric (TAP) pager protocol.



The following settings can be configured for each alarm grade:

Time between pages

It is essential that the values for the Time Between Pages settings are chosen carefully. A value that is too small may generate too many pages, potentially flooding the pager system; a value that is too large may generate too few pages.

Consider the following when setting the Time Between Pages value:

What is the throughput of the your pager system? How many pages can it handle per minute?

What is a reasonable time for one to respond to alarms of each alarm grade?

How many patient monitors are on the network? How often do alarms of different grades occur?

Example:

A pager system can handle 5 messages per minute and Time Between Pages is set to 10 seconds for an Advisory alarm.

If a clinician takes longer than 1 minute to respond to this alarm, subsequent generated pages occurring every 10 seconds exceed the pager system capacity (5 messages per minute).

Settings Range Supported by TAP Description

Display String N/A X Text string used to denote alarm grade in page messages (when applicable) and on Pager Control screens.

Beep Coding 0 - 14 Page System setting indicating which tone or series of tones are used to alert the pager owner.

Priority Coding 1 - 3 Setting that indicates to the pager system how to prioritize a page with respect to other pages. This setting is used to determine which page should be sent first.

Time between pages 10-120 X Number of seconds between subsequent generated pages for the same alarm grade at the same patient monitor. Care should be taken when assigning this setting. See "Time between pages" on page 39.



Supported paging systems

The Infinity Gateway Paging Interface can be used with any paging system that supports the following protocols:

TAP: Telocator Alpha-Numeric Protocol, Rev. 1.7

ESPA: European Selective Paging Application Protocol Rev. 4.4.4.

Pager Requirements:

The Infinity Gateway Paging Interface can be used with any pager that has a minimum text output of 8 characters per page.

Limiting access to pager control

When the Pager Control configuration screen is invoked, the user is prompted to enter a user name, password, and domain name (see "Password protection" on page 14). The values entered must correspond to a user known to the Infinity Gateway server PC, otherwise the user is denied access to the configuration application. In addition, the user name must be a member of the PagerConfig group on the Infinity Gateway PC.

Event log

The Pager Service makes an entry in the Windows Application log in the following situations:

A page is queued or sent to the paging system.

A configuration change is received from the Pager Control application.

A patient monitor goes online or offline.

CAUTION

A pager must not be programmed for Sequential Lockout. This pager feature can prevent multiple identical pages from being received within a short period of time.



Pager control

Pager Control is an application that is part of the "Pager access interface" on page 34. It consists of a Main Screen that provides the care givers with immediate feedback indicating the status of the Pager Interface, including a variety of "System alerts" on page 41. The Pager Control main screen also provides the ability for the care providers to configure the "Delay" on page 45 and "Page level" on page 44 settings, according to hospital policy, for all patient monitors configured for the interface.

The Pager Control application also has a password-protected configuration screen that allows certain privileged users to configure pagers and patient monitors into the application, assign pagers to caregivers and send test pages.

See the Pager Control application's on-line help for more details.

System alerts

The pager control application alerts the user to specific catastrophic conditions that prohibit the pager Interface from working. Alerts are reported for the following conditions:

Pager service disconnected

Lost communication with the pager system

Lost communication with the Gateway service

Alarm timeout

Duplicate bed label

An alert remains on the screen until the condition has been corrected. For example:

CAUTION

The Pager Control application is intended to be on the screen at all times while the Pager Interface is running.

The Pager Control application must be run on the Infinity Gateway Server PC. Only one copy of the application can be run at a time.



Page message text

Message formats

<Bed Label>The page message consists of the label of the patient monitor in alarm.

<Alarm Severity>@<BedLabel>The page message consists of the Display String configured for the alarm grade of the alarm being paged, followed by the '@' character, followed by the label of the bedside monitor in alarm.

<Alarm Message>@<BedLabel>The page message consists of the Alarm Message displayed on the patient monitor (in the language of the patient monitor), followed by the '@' character, followed by the label of the patient monitor in alarm.

<Alarm Severity>^<Patient Name>@<BedLabel> The page message consists of the Display String configured for the alarm grade of the alarm being paged, followed by the '^' character, followed by the patient name, followed by the '@' character, followed by the label of the patient monitor in alarm.

<Patient Name>^<Alarm Message>@<BedLabel> The page message consists of the patient name followed by the '^' character, followed by the Alarm Message displayed on the patient monitor (in the language of the bedside monitor), followed by the '@' character, followed by the label of the patient monitor in alarm.

<Patient ID>^<Patient Name>^<Bed Label>^<Alarm Grade>^<Alarm Message>^<Care Unit>^<Param ID>^<Reserved>^<Julian Time> The page message consists of the Patient ID followed by the '^' character, followed by the Patient Name, Bed Label, Alarm Grade, Alarm Message displayed on the patient monitor (in the language of the patient monitor), Care Unit, Param ID, and the Julian Time.

Maximum message size

Some pagers have maximum message sizes. To support these pagers, the Dräger Pager Interface lets the user configure a maximum message text size to be sent to the pager. If a message is sent to the paging system, which exceeds the maximum message size, it is truncated (see "Message truncation" on page 43).

NOTE

The Reserved field contains codes planned for use in a future Gateway release.



Each message format has a default and supported range of values for the Maximum Message Size, as follows:

Message truncation

Message are truncated as follows to meet the configured maximum message size:

First, it is truncated to the right of the <Alarm Severity> or <Alarm Message>, if they exist.

Second, the <PatientName> is truncated from the right, if it exists.

Third, the <BedLabel> is truncated from the right

Examples of Page Message Truncation

Message Format Default Maximum Length Range

<Bed Label> 10 4 - 10

<Alarm Severity>@<BedLabel> 14 6 - 31

<Alarm Message>@<BedLabel> 26 26 - 61

<Alarm Severity>^<Patient Name>@<BedLabel> 40 22 - 57

<Patient Name>^<Alarm Message>@<BedLabel> 65 42 - 87

<PatientID>^<PatientName>^<BedLabel>^<Alarm Grade>^<Alarm Msg>^<Care Unit>^<Param ID>^<Reserved>^<JulianTime>

180 180 - 180

NOTE

Whenever a component is truncated (i.e. <Alarm Severity>, <Alarm Message>, <Patient Name>, or <BedLabel>) a '?' character is inserted to indicate that truncation has occurred. If the component is removed completely, no '?' is used.

Generated Message Maximum Message Size Message Sent to Paging System

YELLOW@BED100B 12 YEL?@BED100B

6 BED10?

YELLOW^Washington George@BED100B

25 ^Washington Geor?@BED100B

NOTE

Truncation occurs before the page message is translated using the currently configured character mapping.



Page level

Once configured into the pager access interface, each patient monitor is assigned a page level that controls when a pageis sent for the individual patient monitor. Available settings vary depending on the hospital's setting for Alarm Level Settings Allowed.

Escalation

If a patient monitor remains in alarm long enough for a predefined number of pages to be sent for that patient monitor, then escalation occurs and all subsequent alarms are sent to the escalation pager instead of being sent to the primary pager for that patient.

The predefined number of sequential pages that must be sent, without an intervening non-alarm state, before escalation occurs, is called the escalation count.

Whenever the patient monitor goes out of alarm or has an alarm that is not a qualifying alarm (i.e. non-alarm state), escalation is no longer in effect and the escalation count is started over.

The Escalation Pager Number and Escalation Count are set in "Supported languages" on page 29 and in "Infinity Gateway setup" on page 16, and applies to all patient monitors.

Page Level Settings Alarm Grades Paged

OFF None

ADV AdvisorySeriousLife threatening

SER SeriousLife threatening

LT Life threatening



Delay

In the Pager Control application you can set a time period (delay) for which an alarm must exist before a page is actually generated. This delay must range between 0 and 30 seconds and can be configured individually for each patient monitor.

This delay only applies to the initial onset of a qualifying alarm. If another alarm occurs, without an intervening non-alarm state, the delay does not apply.

Whenever the patient monitor goes out of alarm or has an alarm that is not a qualifying alarm (i.e., non-alarm state), the delay is applied to the next alarm that occurs.

NOTE

The ability to configure a Delay Setting Allowed is a hospital policy that can be enabled or disabled in the Pager Setup of the Infinity Gateway Setup application.

Configuring Timing Master


Configuring Timing Master

Time Master is a standard option of the Infinity Gateway Server and can be enabled during "Infinity Gateway setup" on page 16. It synchronizes all the clocks on the Infinity Network to the internal clock on the Infinity Gateway Server.

The clocks in the Infinity devices are synchronized to the server's internal clock:

At Infinity Gateway server startup

Up to two configurable times per day

Whenever the Infinity Gateway Server clock is changed by 30 seconds or more.

Gateway generates a synchronization message at a user configured time, with the option to configure a second synchronization message. A user may specify the hour and minute that a message is sent. Synchronization messages are sent within one minute of the specified time.

CAUTION

For the Infinity Gateway to synchronize the entire Infinity Network, it must be configured for all monitoring units on the Infinity Network.

Gateway Time Master reads time only from the Server's internal clock. To ensure this matches hospital time, the Server's clock must be separately controlled by a standard tool such as Microsoft Windows Time Synchronization.


WinAccess

WinAccess

The WinAccess API Developer Tool is a license option that lets you develop custom Windows applications that retrieve data from the Infinity and SDC networks. It is distributed on the Infinity Gateway distribution CD in the WinAccess Option folder.

It includes:

A DLL (dynamic linked library) called "WvAPI.DLL" on page 48.

Interface definition files, WvAPI.h and WvAPI.lib, that define all of the methods included in the interface and all associated structures needed to use the interface.

A WvAPITest sample application

TCP/IP Interface definition file, ForeignDataService.h, that defines all of the TCP/IP messages and responses that can be used by a non-Windows application to exercise the functionality of WvAPI.DLL.

A test DLL, RemTst.DLL, which can be used with the WvPITest program to emulate and test the TCP/IP interface.

esiFormat.h that defines the layout of the 12-lead rest ECG file output by Tunnel

A custom Windows application can dynamically link to the WvAPI DLL; other applications can use the functionality of the DLL via the use of the TCP/IP interface.

When WinAccess is enabled, 12 Lead Output is available. This feature outputs Rest ECG report data to a file, which can also be used by custom applications.

WinAccess


Configuration

WvAPI.DLL

The WvAPI Application Programming Interface (API) is described in detail in the "Protocol handbook" on page 54. It can:

List the patient monitors currently connected to the Infinity Gateway Server, provided that a valid user name and password are supplied.

Select a patient monitor from the list of devices currently connected to the Infinity Gateway.

List all the parameters available on devices on the Infinity and SDC networks, including a variety of Ventilator parameters. This includes patient monitor calculator outputs and ventilator settings.

Make available via TCP/IP For developers writing an application on a custom, non-Windows platform. Win Access functionality is made available via sockets. There is a new service called Infinity Export Server (infExp.exe) that listens on the socket for messages from the custom application. It calls the WVAPI.dll and sends return information back to the application via the socket.

Byte swap When enabled, message bytes are placed in network order (big endian).

Service Port The service port that the Infinity Export Server listens to and the custom application connects to.

12 Lead Output 12-Lead output data for use by custom applications.


WinAccess

Gather information about the parameters as available.This information includes: Parameter label, current value, current value time stamp, unit of measure, lower alarm limit, upper alarm limit, alarm enable setting, alarm state, alarm grade, alarm limit, and time of alarm. Alarm information is only available on parameters for which an alarm can be set on the device from which the parameter originates.

Retrieve the selected device’s current highest grade alarm information, including alarm state, alarm grade, alarm message, and time of alarm.

Retrieve the selected Infinity monitor's current highest grade ventilator alarm information (if available), including alarm state, alarm grade, alarm message, and time of alarm.

Retrieve all the alarm information for all alarms (state, grade, alarm message and time of alarm) from any SDC device.

List all the waveforms available at the selected device.

Collect waveform data for any or all of the waveforms.

List all trends available at the selected Infinity patient monitor.

Retrieve up to 24 hours of trend data for any available trend.

Retrieve demographic data for the selected Infinity patient monitor, including patient name, patient identifier, birth date, physician, sex, race, patient category, admit date, height, and weight.

Set demographic data on the selected Infinity patient monitor with some restrictions. See the "Protocol handbook" on page 54 for more details.

CAUTION

Continuous parameters are updated every one second via the Infinity network, and every five seconds via SDC, with the exception of ventilator settings and patient monitor outputs which are updated every minute. Applications which receive this data must remain connected to the bedside monitor longer than one minute.

WinAccess


WvAPITest sample application

This sample application exercises all the functionality implemented in the WvAPI.DLL.

The installation of WinAccess includes all of the C++ source code for this application. The project can be built in single-byte string mode or in Unicode mode and it can also be built for local or remote (TCP/IP) access.

NOTE

Due to the 32 bit File Redirection in Microsoft 64 bit operating systems, the output locations of the generated files for WvGetVitalSignsReport and WvGetVentSettings are incorrect. The file is located at%windir%\SysWow64.


Alarm History Database

Alarm History Database

The Alarm History Database is a web-based application that provides alarm information for patient monitors on the Infinity network. The Alarm History Database captures the last 28 weeks (default, with a minimum of 1 week, maximum of 52 weeks) of patient monitor alarm history, and maintains this information in the Alarm History report during a selected time period for the selected monitoring units.

After a successful login, the following dialog appears:

See the Alarm History Database Instructions for Use for additional information.

Setting Description

Start date Earliest date from which recorded alarms are included in the report.

End date Latest date from which recorded alarms are included in the report.

Collect all available monitoring units A monitoring unit is a grouping of patient monitors. Your biomed can help identify what monitoring unit covers the beds you are responsible for.

Collect only selected monitoring units

Do not export alarms that have no alarm grade.

When a Gamma patient monitor is used, it is possible to get false alarms with an alarm grade of None. This option removes these alarms from the exported report.

File access


File access

Vital Signs File Output (not for SDC devices) is available through File Access. It is an interface that provides parameter and alarm information (in file format) for every patient monitor on the Infinity network. This interface is installed automatically during Infinity Gateway installation, but the option must be purchased, enabled, and configured via the Options program.

The interface outputs a Patient Directory file, which contains a list of current Patient Names and their Patient IDs, Bed Labels, Care Units, and the corresponding Vital Signs File Name. It also produces a Vital Signs File for each Infinity monitor. This file contains the latest parameter and alarm data for the patient.

The Patient Directory and Vital Signs Files are files with variable size fields, with field delimiters that allow simple methods of file navigation and parsing. The file formats are specified in detail in the Protocol handbook.

The Infinity Gateway Setup program lets you specify the directory in which these files are created, and the frequency at which they updated (between 15 and 6000 seconds).

NOTE

The Patient Directory and Vital Signs files are now UTF-16 bytes, whereas prior to VF6, they were ANSI files.


File access

Configuring File Access

To Configure the File Access Option:

1 Open "Infinity Gateway setup" on page 16.

2 Click the check box to enable File Access.

3 Click Configure File Access.The following dialog box appears:

Update Interval (seconds):

Specifies how often the vital signs file information is written to disk (15-6000 seconds.)

CAUTION: If the Infinity Gateway Server is monitoring more than 32 patient monitors this interval must be greater than 60. Depending on various factors (i.e. CPU speed, disk speed, memory), performance may not be adequate at a smaller interval.

Server: Server name or IP address of the Infinity Gateway Server PCBy default this value is set to “localhost” (i.e. the local PC).

Output directory:

Directory where vital signs files will be written.

Protocol handbook


Protocol handbook

The Protocol Handbook contains a detailed description of all data transfer protocols, file formats, and the PatientWatch ActiveX control (the ActiveX control used in the PatientWatch application).

During installation, the Protocol Handbook text is copied on the PC in the following location:

< installation directory >\Handbook\handbook.pdf

These Instructions for Use only apply toInfinity® Gateway Suite Installation and Setup Guide VF9.nwith the Serial No.:If no Serial No. has been filled in by Dräger, these Instructions for Use are provided for gen-eral information only and are not intended for use with any specific machine or unit.This document is provided for customer informa-tion only, and will not be updated or exchanged without customer request.

Directive 93/42/EECconcerning Medical Devices

Draeger Medical Systems, Inc.3135 Quarry RoadTelford, PA 18969-1042U.S.A.(215) 721-5400(800) 4DRAGER(800 437-2437)

FAX (215) 723-5935http://www.draeger.com

Distributed in US by

Draeger, Inc.3135 Quarry RoadTelford, PA 18969-1042U.S.A.(215) 721-5400(800) 4DRAGER(800 437-2437)

FAX (215) 723-5935http://www.draeger.com

In Europe, Middle East, Africa, Latin America, Asia Pacific distributed by

Drägerwerk AG & Co. KGaAMoislinger Allee 53 – 55D-23542 LübeckGermany+49 451 8 82-0

FAX +49 451 8 82-20 80http://www.draeger.com

3703521 – RI 03 en© Drägerwerk AG & Co. KGaAEdition: 1 – 2019-03

Dräger reserves the right to make modifications to the equipment without prior notice.

instructions for use infinity gateway suite...instructions for use – infinity® gateway suite –...

Documents