Restart after synchronization is complete, Finalizing the environment – Welch Allyn Connex CS Central Station & Server - User Manual User Manual

Page 165

Advertising
background image

Connex CS Admin Guide

Moving from Test to Production

159

Restart after synchronization is complete

1.

In a client-server deployment, restart the Connex Server. After the server restarts is
complete, restart each central station or Warm Spare station.

2.

In a stand-alone deployment, just restart the central station.

Restarting the provides the easiest way to restart all services in the proper order
after all synchronization activity is complete.

Finalizing the Environment

Once the test data has been cleared and the Connex Server and or Connex CS central
stations have been rebooted, there may be a few additional steps:

1.

On one of the Connex CS central station, go into the administration tools within the
CS Application and confirm that the Master Bed List, Covered Areas and licensing are
all setup appropriately. Compare the current state with notes collected during the
preparation phase as appropriate.

2.

In a client-server deployment where there is an HL7 ADT interface configured with
the customer’s HIS/EMR system, perform the following. Otherwise, skip this step.

a.

Have the customer start sending HL7 ADT messages from the HIS/EMR.

b.

Wait for 2-5 minutes and then go to one of the Connex CS central station and go
to the Search screen to see that patients are showing up when a search is
executed. If no patients are showing up, then work with the HL7 Interface
programmer to resolve HL7 interface problems as necessary.

3.

Turn on and start using the Welch Allyn devices. The devices should be able to do
patient list and patient look up activities and the Connex CS central station(s) should
start displaying tiles with data as patients are either monitored or episodic readings
are taken on the patients.

4.

In a client-server deployment where the customer has an HL7 ORU outbound
workflow, perform the following. Otherwise, skip this step.

a.

Work the with customer’s HL7 Interface Developer to confirm that any episodic
data captured since step 3 of this section have been published to the customer’s
HIS/EMR.

b.

If no episodic readings have been taken on a patient since step 3, work with the
customer to get an episodic reading taken to verify that the readings are making it
from the device to the Connex Server to the customer’s HIS/EMR.

c.

Work the with customer’s HL7 Interface Developer to confirm that any
continuous data captured since step 3 of this section have been published to the
customer’s HIS/EMR.

d.

If no patients have been continuously monitored since step 3, work with the
customer to get start continuously monitoring a patient to verify that the
continuous data is making it from the device to the Connex CS central station to
the customer’s HIS/EMR.

Note

Advertising