Moving from test to production, Assumptions, Preparation – Welch Allyn Connex CS Central Station & Server - User Manual User Manual
Page 155: Assumptions preparation
D
149
Moving from Test to Production
This process is intended to be used to re-purpose an existing hardware or software
installation of Connex CS from a test environment to a production environment. The
process is often referred to as a customer’s “go-live”. The end-goal of this process is:
•
Allow a customer to use the Connex CS system along with its other production
systems (e.g. EMR/HIS).
•
Remove test data from the Connex CS system so that test data is not mixed with
data collection from patients in a production environment.
•
Keep existing configuration and user accounts created.
•
Keep existing Corepoint Action Lists modification for the HL7 interface in place, and
only need to change endpoints.
•
The outlined process can be used in either stand-alone or client server deployments.
•
An additional step to complete the move to production involves applying a new
customer provided MSSQL Standard License Key on the Connex Server. This must be
implemented prior to go-live as the ship with license is for initial deployment testing
purposes only.
Assumptions
•
A Welch Allyn engineer (Integration or Field) is the person expected to perform this
operation.
•
There is a basic knowledge of how to navigate and use the Windows OS, how to gain
access to the OS from the Connex CS application at the central station.
•
None of the IP addresses for the connections between the Connex server or Connex
CS central station PC’s are changing.
•
This process in not being run at night when a majority of automated system
maintenance routines are being run.
•
No new Connex CS central stations are being added to the deployment during this
migration.
Preparation
1.
On one Connex CS Central Station, go into Settings > Advanced settings (if
required) > Admin Tools and make notes of the Master Bed List, Covered Area
assignments, and licensing states prior to beginning.
2.
If the customer is in a client-server deployment and has outbound ORU functionality,
refer to the Connex CS Customer Project Req. Form, Section D, to get the proper
IP information for the customer’s ORU HL7 interface.