Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software

Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
®
Connex Device Integration
Suite (CDIS)
Network Connectivity Engine
(NCE) software
-
CP 100™ and CP 200™
electrocardiographs
Spot Vital Signs® LXi™
vital signs device
Connex Vital Signs
Monitor® 6000 series
Best practices guide
CP 50™
electrocardiograph
CP 150™
electrocardiograph
Connex® Spot Monitor
ii
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
© 2015 Welch Allyn. All rights are reserved. To support the intended use of the product described in this publication, the purchaser of
the product is permitted to copy this publication, for internal distribution only, from the media provided by Welch Allyn. No other use,
reproduction, or distribution of this publication, or any part of it, is permitted without written permission from Welch Allyn.
Welch Allyn assumes no responsibility for any injury to anyone, or for any illegal or improper use of the product, that may result from
failure to use this product in accordance with the instructions, cautions, warnings, or statement of intended use published in this
manual.
Welch Allyn, CSM, CVSM, Connex, and Spot Vital Signs are registered trademarks of Welch Allyn. CP 50, CP 100, CP 150, CP 200,
CardioPerfect, and SpiroPerfect are trademarks of Welch Allyn.
For information about any Welch Allyn product, contact Welch Allyn Technical Support:
http://www.welchallyn.com/about/company/locations.htm
Revision Date:2015-03
DIR 80020208 Ver. A
Welch Allyn, Inc.
4341 State Street Road
Skaneateles Falls, NY 13153 USA
www.welchallyn.com
iii
Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Devices supported and workflow choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Supported workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Scalability - Vitals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Data flow diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
NCE Server address changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
EMR Server address changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
iv
Contents
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
1
Overview
Introduction
The intent of this document is to describe the usage and integration of best practices for
the CDIS-NCE connectivity software.
The Welch Allyn CDIS-NCE software is intended to provide bi-directional connectivity
between Welch Allyn medical devices and various Welch Allyn and non-Welch Allyn data
management systems.
The CDIS-NCE software supports the device initiated network workflow where the device
is sending data to a server. The device initiated network workflow occurs when the device
initiates communication with the server (for example verifying a patient ID, clinician ID, or
sending vitals or ECG data).
The CDIS-NCE software does not honor requests for data from the server.
Intended audience
The intended audiences of this document include:
•
Customer site IT professionals
•
Integrators (integrators or EMR developers)
•
Welch Allyn Field Engineers
•
Welch Allyn Technical Support personnel
Personnel providing integration of devices into EMR systems will need to know the
components included in the software solution (e.g. DCP, NCE, CPSAPI, FileImporter):
•
Site IT professionals will need to understand the TCP/IP Ports used in the
solution.
•
Site IT professionals may need to know basic troubleshooting.
•
Welch Allyn service personnel will need to know basic and advanced
troubleshooting.
References
•
80019821 CDIS-NCE Software Installation Guide
•
60059617 SRS-IDS CDIS-NCE HL7 EMR Interface
•
60067493 SRS-IDS CDIS-NCE HL7 WebServices EMR Interface
2
Overview
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Definitions
Term
Definition
WACP
Welch Allyn Communication Protocol
CPWS
CardioPerfect Workstation - A comprehensive cardiopulmonary
data management system that transforms any computer into an
efficient diagnostic solution. Enables you to easily acquire,
analyze, store and transmit data from all your cardiopulmonary
testing modalities, from resting and stress ECGs, to spirometry
and ambulatory blood pressure, all in one comprehensive
patient record. A bidirectional interface to major leading EHRs
helps you reduce error and expedite report reviewing.
CDIS
Connex Device Integration Suite – A suite of software to enable
connecting medical devices to host systems (e.g. EMR
software).
HL7
Health Level Seven (HL7) is a standard for exchanging
information between medical applications. This standard
defines a format for the transmission of health-related
information.
NCE
Network Connectivity Engine – Part of CDIS to support device
initiated connectivity workflow.
NRS
Network Rendezvous Service – NRS is used to assist devices in
finding the server(s) for specific device functions (e.g. sending
vitals, remote service, etc.).
Devices supported and workflow choices
Supported Devices
CPWS
HL7
CP 100
D
N/A
CP 200
D, P, C
N/A
CP 50
D, P, C, O
N/A
CP 150
D, P, C, O
N/A
Spot Vital Signs LXi
N/A
P, C
Connex Vital Signs Monitor (CVSM)
N/A
P, C, O
Connex Spot Monitor (CSM)
N/A
P, C
D = Disconnected (Flash Drive Workflow)
P = Partially Connected (Batch Workflow) *Not a best practice workflow
C = Connected (Network Workflow)
O = Orders (or Patient Lists)
Best practices guide
Overview
Supported workflows
Vitals
Device Initiated Network Workflow
Device Initiated Patient List Workflow
3
4
Overview
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Interfaces supported
Combinations of the following interfaces are supported:
Interface examples:
Standard solutions
Welch Allyn supports a standard IHE compliant HL7 solution (see “60059617 SRS-IDS
CDIS-NCE HL7 EMR Interface” on page 1). This solution communicates non-encoded
HL7 data over TCP/IP. This solution is compatible with any EMR that can receive HL7 data
over a TCP/IP socket.
Custom data
For information on custom data modifiers and custom scores please contact your Welch
Allyn sales representative.
Best practices guide
Overview
5
Cardio (ECG / Spirometry)
Support for connecting CP 50 / 150 ECG devices to CPWS and then to the EMR.
Device Initiated Network Workflow
Device Initiated Patient List (Orders) Workflow
Interfaces supported
All CP 50 and CP 150 data is sent to CPWS where the data is stored and then made
available to the EMR integration by means available within the CPWS integration methods
(FileLink PDF, embedded into the EMR, HL7, etc.) Data is not sent from the CP 50 or
CP 150 devices directly into the EMR.
6
Overview
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Scalability - Vitals
Depending on network performance, a given installation may be able to handle up to 400
devices on a single instance of CDIS-NCE. When the installation requires more devices to
be connected (or the solution is not performing as needed due to network bandwidth,
network, or server performance) it is a best practice to scale up the solution by using load
balance software or hardware between the devices and the CDIS-NCE servers.
Best practices guide
Overview
Data flow diagrams
Vitals device with scan patient and send workflow (using NRS IP)
Configuring the device to use NRS IP is the best practice so that the device can take
advantage of sending vital data and it also supports the remote service features. The
diagram shows the sequence of data transactions.
7
8
Overview
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Vitals device with scan patient and send workflow (using VM IP or Host IP)
The devices can also be configured to point directly to the NCE software. Using this
option will only allow for sending vitals, this configuration will not allow the system to take
advantage of the remote service features. The diagram shows the sequence of data
transactions.
Best practices guide
Overview
Vitals device with patient list workflow (using NRS IP)
Configuring the device to use NRS IP is the best practice so the device can take
advantage of sending vital data and it also supports the remote service features. The
diagram shows the sequence of data transactions.
9
10
Overview
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
CP 50 and/or CP 150 device network workflow
The diagram shows the sequence of data transactions.
11
Site Maintenance Activities
The following actions may be needed to maintain the system.
NCE Server address changed
The NCE Server address change can happen for a few reasons:
•
Moving from a test environment to a production environment. The facility may have
NCE on a test server and the facility does not want to use that same server for
production.
•
The failure of a server and the resulting need to put in place a new server with a new
IP address.
•
Server software has been split across multiple servers.
To change the NCE Server address:
•
Reconfigure the DCP ordinal settings to point to the correct server(s).
•
The DCP settings are stored in the registry at:
“+.(<B/2&$/B0$&+,1(?6<67(0?&XUUHQW&RQWURO6HW?6HUYLFHV?'&3?3DUDPHWHUV”.
The configuration of DCP is set at install time, however if configuration setting
changes are needed, they can be done through the computer’s Registry.
Note The DCP Windows service (only the Windows service, not server) requires a
restart after any configuration change.
EMR Server address changed
The EMR Server address change can happen for a few reasons:
•
Moving from a test environment to a production environment, where the NCE
configuration needs to be updated to point to the EMR’s production server.
•
EMR server failure and the resulting need to put in place a new server with a new IP
address.
•
EMR server software has been split across multiple servers.
To change the EMR Server address:
1. Open the NCE Configuration Interface. See the
icon in the system tray.
2. Select “Information Network” in the Settings menu on the left column.
12
Site Maintenance Activities
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
For an ORU Outbound Configuration:
a.
Select Host Index representing the ORU outbound data.
b. Update the Host Address to the proper IP address.
c.
Press the “Save Settings” button on the bottom right of the configuration
interface.
4. Close the NCE configuration interface.
13
Troubleshooting
This section describes issue that could potentially cause a failure condition and steps to
diagnose the issue. Some of the topics have a drawing containing a red indication of the
interface or component that may be at fault.
Device cannot access the network
1. Ensure that the device is within range of an access point.
2. Verify the wireless settings match the network settings:
a.
SSID
b. Radio band
c.
Authentication
d. Passphrase (if needed)
e. Security protocol
3. If you are still having trouble connecting the device to a wireless network, try
connecting the device via Ethernet to determine whether the wireless network is the
issue.
14
Troubleshooting
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Server test failed
NCE
1. Check that the Welch Allyn Vitals Gateway Server IP address matches the IP address
setting on the device’s “NRS IP” setting.
2. Check the DCP configuration to make sure it is pointing to the correct Welch Allyn
Vitals Gateway Server IP address – Ordinal 8.
3. Check Windows Services to make sure “NCE” and “DCP” are running.
Best practices guide
Troubleshooting
15
PartnerConnect – “Sync with server” failed
This section assumes that the Server test has passed before arriving to this stage.
1. Check that the Welch Allyn Vitals Gateway Server IP address matches the IP address
setting on the device’s “NRS IP” setting.
2. Check the DCP configuration to make sure it is pointing to the correct Welch Allyn
Vitals Gateway Server IP address – Ordinal 10.
3. Check Windows Services to make sure “WelchAllyn.ServiceMonitor” is running.
16
Troubleshooting
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Retrieve list failed (if applicable)
This section assumes that the Server test has passed before arriving to this stage.
NCE
The NCE configuration may not be pointing to the correct EMR server configured in
the NCE web interface – Information Network screen – Host x.
Best practices guide
Troubleshooting
17
Vitals send failed
This section assumes that the Server test has passed before arriving to this stage.
NCE
The NCE configuration may not be pointing to the correct EMR server configured in
the NCE web interface – Information Network screen – Host x.
Vitals sent but date-time stamp is wrong
1. Check device’s configuration:
a.
Ensure that the device’s “Time zone” is set to the correct time zone.
b. Ensure that “Emulate Spot Vital Signs LXi” is disabled.
2. Check Server’s configuration:
Ensure that the server’s time zone setting is the time zone corresponding to the
time zone of the devices connected to this server.
Collecting log files and saved or failed files
Log files can be found in the folder &?3URJUDP)LOHV[?:HOFK$OO\Q?1&(. There may
be up to two log files named 1&('HEXJ/RJW[W and 1&('HEXJ/RJW[W. These files are
critical to determine the root causes of issues. Both of these files will need to be
collected when issues arise.
If enabled, a history of the transactions can be found in the SavedCopies folder within the
path &?3URJUDP)LOHV[?:HOFK$OO\Q?1&(. When this feature is enabled in the NCE
18
Troubleshooting
Welch Allyn Connex® Device Integration Suite (CDIS) Network Connectivity Engine (NCE) software
Configuration, it will save data coming in from the device (DeviceToNCE); messages going
to the host (NCEToHost) containing the exact message that NCE sent to the host; and
responses received from the host (HostToNCE) containing the exact message the host
sent back to the NCE engine. This data is very helpful to diagnose formatting or other
application issues.
If enabled, any failed transactions can be found in the FailedCopies folder within the path
&?3URJUDP)LOHV[?:HOFK$OO\Q?1&(. When this feature is enabled in the NCE
Configuration, it will save data coming in from the device when a failure happens. This is
helpful to see what data was sent from the device that may have caused a failure to
happen.
Limitations
1. CDIS-NCE cannot push a file to a remote server.
If file output is desired, the files must be stored locally on the server NCE is running
within the NCE folder.
2. CDIS-NCE is supported only on Windows OS platforms.
3. Thin client (Citrix or RDP) is not supported. The CDIS-NCE solution is intended to be a
server software solution where the device(s) will connect to CDIS-NCE via a network
connection.
4. CDIS-NCE does not support a Bluetooth connection.
5. CDIS-NCE does not support ADT. CDIS-NCE only supports query-response of patient
or clinician information.
6. Sending of data (e.g. HL7 ORU) is initiated by the device only. A host system cannot
query for data from the CDIS-NCE software or directly from the device.
7. Batch workflow is not a preferred workflow since not all EMR systems can properly
handle sending a bulk set of data.
8. When a test send fails, the test data is saved on the device. The device will attempt to
resend the test data from a failed send when the device sends another (new) test. If
there is something wrong with the test data (as opposed to a wireless connectivity
issue) that caused it to fail a send on the first attempt, it will also fail on the second
attempt. To avoid an abundance of errors in the EMR, remove records from the device
that failed to send.
9. Modifications of the solution configuration (transforms or EMR data mapping) need to
be done by Welch Allyn personnel.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement