Welch Allyn Connex CS Install Manual
Welch Allyn Connex CS Install Manual

Welch Allyn Connex CS Install Manual

Hide thumbs Also See for Connex CS:
Table of Contents

Advertisement

Welch Allyn Connex
CS
®
Server
Install Guide
Platform or Virtual Server

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Connex CS and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Welch Allyn Connex CS

  • Page 1 Welch Allyn Connex ® Server Install Guide Platform or Virtual Server...
  • Page 2 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.
  • Page 3: Table Of Contents

    Confirm Connex Server operational state ........ 19 Confirm communication with central stations ......21 HL7 Interface Configuration .......... 22 Confirm Connex CS Admin tools configuration ......22 Importing a customer specific Corepoint NIX file ......24 Commit and activate NIX file changes ........ 28 Configure IP address and ports for EMR connections .....
  • Page 4 Late ADT settings ..........57 Final Steps ............59 Final Steps ............59 Backup Connex CS users and configuration ......59 Backup Corepoint configuration - create a NIX file ......61 Backup Corepoint HL7 License ........64 Disconnect peripherals ..........65 Troubleshooting ...........
  • Page 5 Party Alarm Server Changes ..... 122 If IP Address of the 3 Kiosk deployment ..........124 If the IP address of the Server changes ......124 Connex Proview Installation ......... 125 If the IP address of the Service Changes ......125 Printer, Date &...
  • Page 6 Welch Allyn Connex CS Server Install Guide...
  • Page 7: Quick Reference Guide

    Quick Reference Guide The quick reference guide provides a high level sequence overview to the process of installing a Connex CS system and milestone checklist to measure progress. Complete details can be referenced within this document as needed. Overall Sequence 1.
  • Page 8: Install Connex Server

    Connect customer provided terminal/KVM cabling (If applicable). Connect network cables. No. Skip this Note: LAN #1 designated for comms with Connex CS systems and patient step. monitors. Note: LAN #2 designated for comms with facility EMR application (if applicable).
  • Page 10: Introduction

    Introduction About this manual This Connex CS Server Install Guide provides information needed to plan and perform the installation of the Connex server and it’s peripheral components. The Connex server is an accessory to the Connex CS Central Station. This information describes how to: ...
  • Page 11: Related Documents

    Connex CS Customer Project Req. Form 80018045 Connex CS Pre-Install Checklist 80018210 Connex CS Central Station & Server Admin Guide Symbols used in this manual WARNING Warning statements identify conditions or practices that could result in personal injury. CAUTION Caution statements identify conditions or practices that could result in damage to the equipment or property.
  • Page 12: Definitions

    POST functions and error reporting. Client-Server A topology in Connex CS with a central station PC (client) and a Connex server (hardware or virtual server). In the client-server model, data is replicated between the client and the server via the Welch Allyn Connex Data Synchronization Service.
  • Page 13 Upgrade On-site service activity to enhance or add functionality to a device or system. An upgrade can be accomplished with changes to hardware, software, configuration, or combinations of all three. Uninterruptable Power Supply, a unit which provides battery back-up power for connected devices. Virtual Connex Server A server instance which has been virtualized to an appliance form (includes Operating System, Connex Applications, and Database)
  • Page 14: Overview And Planning

    The Connex CS system consists of a central station that receives and displays information from connected devices. In this configuration, continuous and episodic devices communicate over the network to the central station.
  • Page 15: Planning For The Install

    Connex CS Customer Project Req. Form detailing the planned implementation. Install system components as described within the Connex CS Customer Project Req. Form. Note The most current information for a customer specific project will be located in the...
  • Page 16: Site Preparation And Inspection

    DO NOT MISPLACE THESE DOCUMENTS. Make working copies for reference. Confirm that all items have been completed per the Connex CS Pre-Install Checklist, if applicable, including installation of all electrical service, data cabling, and fixture installations (e.g.
  • Page 17  Data cables 6. Provide the media containing the Virtual Connex server to the IT staff of the facility if applicable. 7. For hardware Connex server installations, review Figure 2-2: “Hardware Connex server front panel features and connectors”, Figure 2-3: “Hardware Connex server front panel controls”, and Figure 2-4: “Hardware Connex server rear panel connectors”.
  • Page 18 Overview and Planning Reset Button HDD LED Figure 2-4: Hardware Connex server rear panel connectors AC Power inlet (100 - 240 PCI Express slot VAC) Serial port A Video connector Service Mgmt network USB Ports interface (BMC) NIC 1 Connector USB Ports (10/100/1000 Mb) NIC 2 Connector...
  • Page 20: General Setup

    Those with four posts or data cabinets should use the slide rails, while the two post relay rack must use the shelf mounting option. Consult with the Welch Allyn project manager for your install project for assistance if needed.
  • Page 21: General Setup, Hardware

    In general LAN1 is used for the CS application interface. Refer to the Connex CS Customer Project Req. Form, Section B as needed. b. If needed, attach an RJ45 type network cable from the server LAN2 port to the customer designated switch jack.
  • Page 22: Connex Server Startup

    Connex server, hardware or virtual, be started first. Central stations, including a warm spare should be started after the Connex server is running. Refer to the Connex CS Central Station Install Guide for additional information and startup behavior for a Warm Spare system.
  • Page 23: Server Boot Up Screens

    5. The Virtual drive is configured as Online. This is the normal state. Note A virtual drive being reported with a status of Degraded indicates a potential problem with one of the hard disk drive. Contact Welch Allyn technical support for additional assistance.
  • Page 24 Connex Server Startup Figure 4-2: Embedded Server RAID with status display 6. After approximately 7 seconds, the display updates to the Intel Server Board screen. An example is shown in Figure 4-3: “System startup display with blue Intel logo”. Figure 4-3: System startup display with blue Intel logo 7.
  • Page 25: Confirm Connex Server Operational State

    . The Connex CS Admin Tools function launches. a. If the icon is not present, go to Start > All Programs > Welch Allyn > Connex > Admin Tools Launcher > (version number) to locate the program. Right-click on Welch Allyn Admin Tools Launcher and select Send to >...
  • Page 26 Connex Server Startup 4. Click on Settings > Connections. The Services windows displays the state of all of the core services running which make up the Connex Server application. An example is shown below in Figure 4-5: “Administrator Tools setting connections window”. 5.
  • Page 27: Confirm Communication With Central Stations

    2. On the Connex Server, open a command tool and ping each host by its assigned IP address. Refer to the Connex CS Customer Project Req. Form, Section B information as needed. 3. On the server, open the Admin Tools again.
  • Page 28: Hl7 Interface Configuration

    1. On the desktop, double-click on . The Connex CS Admin Tools function launches. a. If the icon is not present, go to Start > All Programs > Welch Allyn > Connex > Admin Tools Launcher > (version number) to locate the program.
  • Page 29 Figure 5-1: Administrator Tools HL7 ADT configuration window 5. If the site is configured to support continuous outbound ORU data, from the Admin Tools, select HL7 > Continuous Measurement Configuration. See Figure 5-2: “Administrator Tools HL7 continuous measurement configuration window” for an example. Figure 5-2: Administrator Tools HL7 continuous measurement configuration window...
  • Page 30: Importing A Customer Specific Corepoint Nix File

    10. The HL7 engine IP address is the IP address of the Connex server’s interface which communicates with the facilities HIS / EMR application. Refer to the Connex CS Customer Project Req. Form, Section D document as needed for this information.
  • Page 31 To import the customer specific Corepoint NIX file: 1. Download the NIX file from the Welch Allyn project data repository (PDR). Consult with the project manager and/or applications engineer if needed. 2. Collect a copy of the NIX file and transfer to the desktop of the Connex server.
  • Page 32 HL7 Interface Configuration Figure 5-5: Browse to a file example window 6. The package information page appears. The package contents displays what files are Different, and what are Identical. An example is shown below in Figure 5-6: “Import selected components window example”. Identical items will not be imported. Note In some cases it may be desirable to deselect certain items that are already configured for the customer specific environment, so as not to be overwritten.
  • Page 33 Figure 5-6: Import selected components window example At the bottom of the window, select Import. The confirm file replacement window appears. An example is shown in Figure 5-7: “Confirm replace file window example” below. 8. Click Yes to all. Figure 5-7: Confirm replace file window example 9.
  • Page 34: Commit And Activate Nix File Changes

    HL7 Interface Configuration Figure 5-8: Import file status window example 10. Click OK to complete the import of the NIX file. Commit and activate NIX file changes Near the bottom of the Corepoint administration console window, click on the Workspace Changes* tab.
  • Page 35 Figure 5-11: Commit changes comments window example 4. Add text to the Comments section briefly describing the changes being applied, as shown above in Figure 5-11: “Commit changes comments window example”. 5. When complete, click on Commit and Activate at the bottom of the window. The Start/ Connections window appears.
  • Page 36: Configure Ip Address And Ports For Emr Connections

    HL7 Interface Configuration Figure 5-12: Start/ connections window example 6. Click OK to all connections and finish the activation process Configure IP address and ports for EMR connections Depending on the features ordered and customer EMR applications, up to 3 connections may require configuration to communicate properly.
  • Page 37 3. Make changes to the basic configuration for the Server Port number as needed. Refer to the Connex CS Customer Project Req. Form, Section D for input to these fields. Caution Do not make changes to the Client or Server radio buttons in the Basic Configuration area.
  • Page 38 HL7 Interface Configuration 5. In the edit receiver connection window, click on the button in the upper-left corner. 6. Select the Save and Close option to save all changes. The edit window closes. Figure 5-16: Save changes window example To configure the ORU outbound data connections: 1.
  • Page 39: Restart Connections After Changes

    3. Make changes to the basic configuration for Server name / address (IP address) and Server Port number as needed. Refer to the Connex CS Customer Project Req. Form, Section D for input to these fields. Caution Do not make changes to the Client or Server radio buttons in the Basic Configuration area.
  • Page 40 HL7 Interface Configuration Figure 5-20: Commit all changes window example 3. The Commit Changes window appears, see Figure 5-21: “Commit changes comments window example” for an example. Figure 5-21: Commit changes comments window example 4. Add text to the Comments section briefly describing the changes being applied. 5.
  • Page 41 Figure 5-22: Start/ connections window example 6. Click OK to all connections and finish the process.
  • Page 42: Corepoint Service

    HL7 Interface Configuration Corepoint service In some cases the entire Corepoint service may need to be restarted also. Open the Corepoint Administration tool, which opens in an Internet Explorer browser session. To Corepoint service: 1. Click the Stop button in the bottom section of the screen. 2.
  • Page 43: Confirm Communication With Emr

    If the server is configured for interface with the facility’s EMR application, via HL7 messaging, perform these checks. Refer to the Connex CS Customer Project Req. Form and sales order for confirmation purchase of HL7 messaging options for ADT inbound and ORU outbound workflows.
  • Page 44 HL7 Interface Configuration g. An updated view example is shown in Figure 5-26: “Corepoint administration console connections updated view” below. h. The next time the administration console is accessed, it will retain the last know view. Figure 5-26: Corepoint administration console connections updated view 5.
  • Page 45 7. A new connection will remain in a yellow state until data is received from the connection. 8. Connection names are related to the functions they serve. An example general list is described in Table 5-2: “Connection names and functions”. Table 5-2: Connection names and functions WA_ADT_IB Inbound ADT between facility HIS and Corepoint (External)
  • Page 46: General Connex Cs Configuration

    1. On the desktop, double-click on . The Connex CS Admin Tools function launches. a. If the icon is not present, go to Start > All Programs > Welch Allyn > Connex > Admin Tools Launcher > (version number) to locate the program.
  • Page 47: Configure Ags Input / Output Connections

    The output type AGS is used on the central station, not the Connex server. b. Confirm the IP address and Port number of the facilities Alarm Server is properly listed in the output fields. Refer to the Connex CS Customer Project Req. Form, Appendix B1 as needed.
  • Page 48: Configure Ags Priority Filter

    Figure 6-2: Alarm gateway priority filter window example 2. Confirm settings for All covered areas match those desired by the facility. Refer to the Connex CS Customer Project Req. Form as needed. 3. Use the drop-down arrow to view available settings and change values if needed.
  • Page 49: Configure Clinician Authentication

    By default, each covered area will inherit the global setting applied to all covered areas. b. In some situations, an individual covered area may require different settings from the default value. Refer to the Connex CS Customer Project Req. Form as needed for additional input data.
  • Page 50: Multiple Security Providers

    General Connex CS Configuration Figure 6-4: Basic workflow to configure Device Clinician Authentication Multiple Security Providers The admin tool supports creation of multiple security providers of type ConnexDatabase and Microsoft Active Directory service. View Clinician Authentication settings 1. From the Server’s Admin Tools application, navigate to the Admin Tools tab > Device Clinician Authentication.
  • Page 51 Figure 6-5: Device Clinician Authentication main screen example 2. The authentication providers area includes a list of providers. 3. A Provider Name listed with a “check” in the Status column indicates that it is currently in use.
  • Page 52: Configure For Use With Connex Database

    General Connex CS Configuration Configure for use with Connex Database 1. Select ConnexDatabase to authenticate against the Connex CS Database This is the default setting. See Figure 6-6: “ConnexDatabase default settings example”. 2. Settings may be modified as described in sections below.
  • Page 53 1. Check each group that applies. 2. Key in additional group names as needed and press the Add button. 3. Each new group must already exist in the Connex CS database Figure 6-8: Configure Group membership details, Connex CS Database example...
  • Page 54 EMR ID is mapped to clinician middle name. But, not all clinicians have a middle name. the Connex CS security provider returns an empty EMR ID to the device when that clinician authenticates at the device. The uploads will not be successfully transmitted to the EMR because the clinician ID is not valid.
  • Page 55: Configure For Use With Active Directory

    Enter the IP address of the active directory domain controller. b. Do not enter a domain name. An IP address is required. c. Refer to the Connex CS Customer Project Req. Form, Appendix B1 as needed for this information.
  • Page 56 General Connex CS Configuration b. This is the account name which will be used by the Connex CS system to make the connection to the facility’s active directory service. Refer to the Connex CS Customer Project Req. Form, Appendix B1 as needed for this information.
  • Page 57 Identifier with test vitals and outbound ORU messages to the EMR. 1. Select the clinician identifier for use as the EMR identifier. Refer to the Connex CS Customer Project Req. Form, Appendix B1 as needed for input data in these fields.
  • Page 58 The admin tool supports capture of other attribute and custom attribute usage. See Figure 6-14: “Add a Custom active directory example” below. Refer to the Connex CS Customer Project Req. Form, Appendix B1 as needed for input data in these fields.
  • Page 59: Order The Security Providers

    Figure 6-14: Add a Custom active directory example When changes are complete 1. Click on the Save button at the bottom of the working window. 2. Restart ECS for all changes to take effect. Order the security providers The admin tool provides the capability to reorder the security providers. 1.
  • Page 60: Configure Auto Discharge Settings

    General Connex CS Configuration providers” area instead. Configure auto discharge settings The Welch Allyn ADT Task Scheduler Service provides a configurable service that runs automatically in the background to assist in managing the Patient List contents and remove old entries.
  • Page 61: Adt Auto Discharge Settings

    6. Refer to the Welch Allyn Connex CS Directions for Use, section titled “Automatic discharge” for general clinical information about this feature. 7. Make changes as needed. 8. Click Save when changes are complete. ADT auto discharge settings 1. Settings starting with “ADTAUTODISCHARGE” controls automatic discharge behavior for patients which have received an ADT message.
  • Page 62: Auto Discharge Settings For Confirmed Patients

    General Connex CS Configuration Auto discharge settings for confirmed patients 1. Settings starting with “AUTODISCHARGE” control automatic discharge behavior for confirmed patients. Figure 6-18: Confirmed patients auto discharge related settings 2. The following table describes the function of each setting.
  • Page 63: Late Adt Settings

    Late ADT settings 1. Settings starting with “LATEADT” control automatic discharge behavior for patients which have been under Continuous Monitoring or Spot Vitals taken, but the ADT message arrived late or after the fact. Some addition settings also control behavior related to late ADT settings.
  • Page 64 General Connex CS Configuration Caution Do not change settings for EXECUTION SEQUENCE unless directed by Welch Allyn Engineering.
  • Page 65: Final Steps

    Before placing the any parts of the system (Central Station or Server) into use by clinicians, the system installation must be verified. Confirm proper configuration and operation by completing “Related Documents” steps detailed in the Connex CS Install Verification Guide. See additional information. Backup Connex CS users and configuration The Administration Tool has functionality to backup and restore configuration information for the system and users.
  • Page 66 Final Steps Figure 7-1: Administrator Tools export settings users and configuration window 5. Select Export data. 6. Navigate to the USB flash drive. Choose a folder location for the backup. 7. Chose a file name for the saved file. By default, the file will be called WAConfigurationSettings.xml, but should be changed to the following format for consistency: ...
  • Page 67: Backup Corepoint Configuration - Create A Nix File

    Backup Corepoint configuration - create a NIX file Create a backup of the current Corepoint configuration which may be needed in the case of a replacing the system hardware in the event of failure. Note These steps only apply if the Connex server is licensed and configured to support HL7 interfaces, including ADT and/or ORU connections.
  • Page 68 Final Steps Figure 7-3: Right-click on the root to open 5. Click on Export. The export options window appears. Figure 7-4: Corepoint export options window 6. Click on the option for Export all derivatives. Then click OK. the progress window appears momentarily.
  • Page 69 7. After a short while, the export selected components window appears. Figure 7-6: Corepoint export select components window example 8. Leave all settings in the above window at default, with all items selected. Click OK to proceed. The save file window appears.
  • Page 70: Backup Corepoint Hl7 License

    Final Steps Figure 7-7: Save file window example 9. Click on Desktop to place the backup file directly on the desktop, making the backup easy to locate if needed later. 10. Type a File name for the backup. 11. Chose a file name for the saved file. Follow the recommended naming schema below to maintain consistency: ...
  • Page 71: Disconnect Peripherals

    2. Navigate to C:\Program Files (x86)\Corepoint Health\Corepoint Integration Engine\License. 3. Make a copy of the license file CorepointEngine.lic and place it in backup folder at: C:\ProgramData\Welchallyn\@Config.Backup. Disconnect peripherals 1. Logout of the administrator account before disconnecting peripheral items from the server. 2.
  • Page 72 Final Steps...
  • Page 73: Troubleshooting

    Troubleshooting The following steps are intended to provide frontline troubleshooting and diagnostic information. If problems cannot be corrected, contact Technical Support for additional information. Front Panel LED information The hardware Connex server included LEDs on the front panel that can aid in troubleshooting the system.
  • Page 74: Server Startup

    Final Steps Reset Button HDD LED Server Startup Problem Diagnostic Steps / Causes / Corrections Power On LED is not on. Make sure that the AC power cord is firmly attached to the CPU and to the outlet. CPU is not running. Ensure that the UPS and/or AC power outlet is “live”.
  • Page 75: Connex Database Restore

    3. Restart services, scheduled tasks, and open the Connex CS Application on the central station. For Client-Server deployment: 1. Stop services, scheduled tasks, and close the Connex CS Application on server and all central stations. 2. Restore the database from backup on the server.
  • Page 76: Restore The Database From Backup

    Final Steps Restore the database from backup 1. Open the Microsoft SQL Server Management Suite (SSMS) tool, and under Object Explorer and expand the Databases node. Figure A-2: SSMS Object explorer with WADB example 2. If there is a WADB database, right-click on the WADB database node and select Tasks>Restore>Database.
  • Page 77 Figure A-3: Restore Database Source selection example 4. Click on the “…” button to browse to the backup folder and select the backup file. Remove any locations listed in the Backup location box. Click the Add button and browse to the folder that contains the backup file.
  • Page 78 Final Steps Figure A-5: Location the backup file example 6. Click the Restore check box to select the backup.
  • Page 79 Figure A-6: Restore database selected example 7. Click the Options tab and check the “Overwrite the existing database (WITH REPLACE)”. Figure A-7: Overwrite the existing database example 8. Click OK to complete the restore. 9. For Standalone deployment skip to “Restart Services, Scheduled Tasks, and Open the CS Application.
  • Page 80: De-Provision The Restored Database

    1. Logon to the computer that hosts the restored database OR logon to a computer that is connected to the host via the windows network. 2. Open a command window and navigate to the directory where the Connex CS Provisioning utility has been deployed. (To locate the deployment folder, search for the program “WelchAllyn.Connex.ProvisioningUtility.exe”...
  • Page 81 Figure A-8: Right-click on WADB example 4. Once delete is clicked, following dialog will be shown. Figure A-9: Select WADB object to delete example...
  • Page 82 Message Box Default Reply is enabled. In Windows 7 embedded, this feature is enabled by default. So on Connex CS central stations the message box will not be displayed. But a message in the windows event log will be added confirming the success of the installation.
  • Page 83: Restart Services, Scheduled Tasks, And Open The Cs Application

    Restart Services, Scheduled Tasks, and Open the CS Application. 1. Restart the services and scheduled tasks that were shutdown previously 2. Start the Connex CS Application. Special circumstances... In some cases over the course of use, it may be necessary to disconnect a client Central Station from the network for an extended period of time, such as construction projects.
  • Page 84: Connex Database Re-Installation

    Final Steps Connex database re-installation There are some situations when this may become necessary, such as moving a client station from one network to a different network. Information from the old network must be removed prior to connection to the new network or the database will become corrupted with incorrect settings and location information.
  • Page 85 Figure A-11: Right-click on WADB example 5. Once delete is clicked, following dialog will be shown.
  • Page 86 7. The dialog will be closed once the WADB is deleted. 8. Open the windows explorer and navigate to following path: C:\Program Files (x86)\Welch Allyn\Connex\Server\<version>\DataBaseInstaller. Note The path may be different depending upon the location of the Program files folder.
  • Page 87 12. If there are any new machines added then activate the license for those machines. 13. Start all the services on all of the central stations. Do NOT start the Connex CS application yet.
  • Page 88 Final Steps...
  • Page 89: Updating Bios

    CAUTION Consult with the clinical staff responsible for monitoring patients to obtain permission to proceed prior to beginning the update. During the update process, ADT data will not update the patient list functions on Connex CS Central Station and devices. Additionally, ORU data will not be shared with the facilities EMR application if applicable..
  • Page 90: Update Bios Installation

    Final Steps end of the procedure. Insert the USB flash drive or similar media containing the BIOS files into one of the open USB ports on the front bezel of the hardware Connex server. 6. In the BIOS setup screens, use the right arrow to navigate to Save & Exit. Navigate down to Discard Changes and Exit and press <Enter>.
  • Page 91 Figure B-2: Update menu example, press <Enter> here to update all functions 6. Various update screens and status messages are displayed during the update process. 7. Progress may appear paused, waiting for user input, but updates will proceed automatically after a short countdown of 3 to 5 seconds. 8.
  • Page 92: Post Update Bios Settings Changes

    Final Steps Post update BIOS settings changes A number of changes may be required after upgrading BIOS. During server boot up a number of screens appear. When the blues screen with the Intel logo and Intel Server Board heading occur, as shown in “Figure 4-3: System startup display with blue Intel logo”, press <F2>...
  • Page 93 To set the BIOS date and time: 1. From the main screen, use the left and right arrow to navigate to the Main tab. 2. Use the up and down arrow to navigate to System Date, highlighted in yellow in Figure B-5: BIOS set date and time.
  • Page 94 Final Steps Figure B-6: BIOS enable both network interfaces (part 1) 4. Navigate to Onboard NIC1, and press <Space> to change to Enabled state if needed. See “Figure B-7: BIOS enable both network interfaces (part 2)” with highlighted examples. 5. Repeat for Onboard NIC2 if needed to set to Enabled state. 6.
  • Page 95 Figure B-7: BIOS enable both network interfaces (part 2) To enable USB support: 1. From the main screen, navigate to the Advanced tab. 2. Navigate to PCI Configuration menu, as shown in “Figure B-8: BIOS enable USB support (part 1)”. 3.
  • Page 96 Final Steps Figure B-8: BIOS enable USB support (part 1) 4. Navigate to USB Controller, and press <Space> to change to Enabled state if needed. See “Figure B-9: BIOS enable USB support (part 2)” with highlighted examples. 5. Repeat for USB Legacy Support if needed to set to Enabled state. 6.
  • Page 97 Figure B-9: BIOS enable USB support (part 2) To set system altitude (fan control): 1. From the main screen, navigate to the Advanced tab. 2. Navigate to System Acoustic and Performance Configuration menu. 3. To set the Altitude press the <Space> bar to step through the choices. 4.
  • Page 98 Final Steps Table B-1: Boot Priority preferred settings Boot Option Primary choice Alternate choice Embedded Raid Controller (ACHI) Identity of the Hard Drive Embedded Raid CD/DVD-ROM Identity of the Optical Drive IBA GE Slot Identity of the network interface NIC1 Internal EFI Shell 6.
  • Page 99: Troubleshooting Bios Updates

    Troubleshooting BIOS updates The table below may assist in identifying problems that you could encounter during the BIOS update process along with potential solutions. Problem Cause / Solution Unable to get into BIOS setup utility by Confirm keyboard is properly attached to one of the USB pressing <F2>...
  • Page 100: Bios Recovery Process

    Final Steps Problem Cause / Solution Acuity and Performance Configuration menu. Adjust Altitude setting to proper value. This is the only setting which will allow for control of fan speed. System returns to EFI shell again after The USB flash drive is most likely still installed after successfully updated BIOS settings.
  • Page 101: Clearing The Bios Password

    Figure B-TS1: Configuration jumper settings 3. Insert the bootable BIOS Recovery media containing the new BIOS image files. A BIOS recovery can be accomplished from SATA CD and USB Mass Storage device. Please note this platform does not support recovery from a USB floppy. The recovery media must contain the following files under the root directory: ...
  • Page 102: Clearing The Bios Cmos

    Final Steps 1. Power down the system and disconnect the AC power. 2. Open the server chassis. 3. Move the jumper from the normal operation position, Password Clear Protect, at pins 1 and 2 to the Password Clear Erase position, covering pins 2 and 3. 4.
  • Page 103: Hardware Server Mounting Solutions

    Hardware Server Mounting Solutions There are several installation options for the hardware Connex server, dependent on the location and space is availability. The preferred option is to install the server within a four post data cabinet using the included slide rail mounting kit. An optional mounting method is detailed for a sites with a two post relay rack configuration, using a shelve mount kit.
  • Page 104 Final Steps Figure C-1: Remove inner member from slides and identify components Front bracket Inner slide member Outer slide member Safety locking pin Rear bracket Release button (blue) 4. Align outer member slide rail into the desired position in the equipment rack. See “Figure C-2: Install slide rails to rack”...
  • Page 105: Attach Inner Slide Member To Server Chassis

    Figure C-2: Install slide rails to rack Figure C-3: Examples with different fastening hardware Attach inner slide member to server chassis 1. Identify left and right inner members. 2. Align each inner member keyholes to the standoffs on the server chassis. “Figure C- 3.
  • Page 106: Insert Server Into Cabinet Using The Slide Rails

    Final Steps Figure C-4: Install inner member to server chassis Insert server into cabinet using the slide rails 1. Carefully raise the server so the that read end of the inner slide rail members are aligned with the slide rail assemblies that are mounting in the equipment cabinet. 2.
  • Page 107: To Remove Server Installed With Slide Rails

    4. Install cables to rear connections as needed. Ensure that there is adequate slack in cables to fully extend the server to the front of the cabinet. Use of customer supplied cables hangers are recommended. 5. Make sure the server slides along the rails with no binding. Adjust slides if necessary. 6.
  • Page 108: Install Server With Shelf Kit Into A Two Post Relay Rack

    Final Steps Install server with shelf kit into a two post relay rack To install a server with shelf kit, tasks include:  Install mounting flanges onto shelf  Attach shelf to rack posts  Install server onto shelf Install mounting flanges onto shelf 1.
  • Page 109: Attach Shelf To Rack Posts

    Attach shelf to rack posts 1. Identify desired location to mount the shelf onto the relay rack. 2. Line up 2 holes in each attachment flange and bolt to rack in desires positions using the 10- 32 or 12-24 pan head screws. See “Figure C-9: Installing shelf mounting flanges”...
  • Page 110: Install Server Onto Shelf

    Final Steps 4. Attach the safety strap onto the shelf. See “Figure C-11: Install safety strap” for an example. Figure C-11: Install safety strap Install server onto shelf 1. Carefully place the server into position onto the shelf. 2. Tighten the safety strap until snug. Ensure that the server is held securely in place on the shelf.
  • Page 111: Install A Replacement Disk Drive

    Install a Replacement Disk Drive It may become necessary to replace a Hard Disk Drive (HDD) at the customer site. As the server is configured with RAID drives which are hot swappable, the process is fairly easy. Follow these steps to install a replacement HDD. 1.
  • Page 112: Install A Hard Disk Drive

    Final Steps Install a hard disk drive 1. With the replacement drive circuit-side down, position the connector end of the drive so it is facing the read of the drive carrier. 2. Align the holes in the drive to the holes in the carrier. 3.
  • Page 113: Connect To Server Via Bmc Console

    Note Any additions, deletions, or changes to be made to executables on this system requires appropriate use of the Solidifier system. Please consult the Connex CS Central Station & Server Admin Guide for guidance. To connect to the server BMC console: 1.
  • Page 114 Final Steps 3. Login to the BMC console with the Username “root” and Password per the Window’s server administrator account. 4. Upon success, the System Information screen appears. An example is show below in “Figure E-2: BMC system information page example”.
  • Page 115 “Figure E-5: Example server console window with Connex CS Admin Tools open” Figure E-5: Example server console window with Connex CS Admin Tools open 11. Note console system commands are controlled by Macro buttons located in the upper right corner of the window.
  • Page 116 Final Steps 12. When finished, close the connection by clicking in the control menu under Video > Exit. The session automatically closes. a. Alternately, click on the windows X button in the upper right corner.
  • Page 117: Network Change And Configuration

    Network change and configuration Network IP change overview The change in the IP Address of one or more systems involved in Connex CS network will cause many components to break. This requires updating the specific configurations in the system used by such components.
  • Page 118: Client Server Deployment

    Final Steps Client Server deployment If the IP address of the Connex server changes This scenario should be handled as summarized below.  Follow the instructions to perform the “EMR-side changes” before changing the server’s network interface. This needs to be communicated to administrator managing EMR at customer site.
  • Page 119 Figure F-1: Changing IP address of the HL7 engine Update the Server NRS Configuration 1. Launch the “Admin Tools Launcher” and navigate to Stations > Network rendezvous services screen. “Services to be resolved by DCP” 2. Delete the existing host entry under group by using Delete button.
  • Page 120 Final Steps Figure F-2: Server IP address changes in NRS configuration 4. Similarly, update ALL host entries for “Services will be resolved by DCP network rendezvous as shown in the example above. Include entries for: a. Ordinal 8 using port 281, for Episodic data. b.
  • Page 121 3. Ensure Host address through Admin Tools a. Launch Admin Tools and navigate to Connections screen. b. Expand the configuration details for “Welch Allyn Connex Episodic Connectivity Service” by clicking the expander button. c. Ensure that the configuration value for the Host Address is either set to “localhost” or new IP address of the server as shown below in Figure F-3: Server IP address changes in Connections ECS settings.
  • Page 122 1. On the central station, navigate to Settings > Advance Settings (if needed) > Admin Tools > Connections screen. 2. Expand the configuration details for “Welch Allyn Connex License Service” by clicking the expander button as shown in the screenshot below in...
  • Page 123: If Ip Address Of The Connex Workstation Changes

    Figure F-4: Central Station Connections License service change details 5. Reboot the workstation. After reboot, it will be connected to sever. 6. Repeat steps 1 - 5 at each Central Station on the network, and the Warm Spare station if included.
  • Page 124 Final Steps 5. Click OK button. Close the connection details. Figure F-5: Server Corepoint ORU confirmed connection updates 6. Similarly, find the connection “WA_ORU_OB_UNCONFIRMED” under Objects. Double-click on the connection and then its “TCP/IP Configuration” to open the connection details as shown in the screenshot below in Figure F-6: Server Corepoint ORU unconfirmed connection updates...
  • Page 125: If Ip Address Of The 3Rd Party Alarm Server Changes

    Figure F-6: Server Corepoint ORU unconfirmed connection updates 9. Navigate to and select the “Workspace Changes” tab. See Figure F-7: Server Corepoint Workspace changes to commit all updates for an example. 10. Click the Commit All button to apply the changes of both connections. It will prompt with confirmation message.
  • Page 126 Final Steps 2. Navigate to Alarm Gateway > Input/Output screen. 3. Delete the existing IP Address/Port entry by using Delete button. See Figure F-8: Server Alarm Gate Service change details for an example. 4. Add new IP Address/Port entry by entering new the IP Address of 3rd Party Alarm Server in the textbox highlighted below and click Add.
  • Page 127 Figure F-8: Server Alarm Gate Service change details...
  • Page 128: Standalone Deployment

    Figure F-9: Central Station NRS change details 4. Similarly, update all host entries for “Services will be resolved by DCP network rendezvous” if defined. 5. Click “Save” to save the changes. 6. Navigate to Connections screen and restart “Welch Allyn Network Rendezvous Service”.
  • Page 129: If Ip Address Of The 3 Rd Party Alarm Server Changes

    2. Ensure Host address through Admin Tools a. Launch Admin Tools and navigate to Connections screen. Expand the configuration details for “Welch Allyn Connex Episodic Connectivity Service” by clicking the expander button. An example is shown below in Figure F-10: Server ECS Connections settings details for IP address changes.
  • Page 130 Final Steps 4. Click “Save” to save the changes. A message appears asking the user to also restart the Alarm Gateway Service. 5. Navigate to Connections screen and Restart the Alarm Gateway Service. Figure F-11: Central Station Alarm Gateway output changes detail...
  • Page 131: Kiosk Deployment

    1. Launch the “Admin Tools Launcher” from Kiosk. 2. Navigate to the Connections screen. 3. Expand the configuration details for “Welch Allyn Connex Episodic Connectivity Service” by clicking the expander button as shown in the screenshot below. 4. Change the configuration value for the Host Address with the new IP address of the server as highlighted in the screenshot below in Figure F-12: Kiosk changes to ECS service details.
  • Page 132: Connex Proview Installation

    Server IP address. 1. Use standard Windows explorer tool to navigate to the location: “C:\Program Files (x86)\Welch Allyn\Connex\ProView\1.0”. 2. Open file “ConnexProView.exe.config” in any text editor 3. Search for the setting with a key “LicenseLocal”.
  • Page 133: Printer, Date & Time Configuration

    If print capability is desired from the Connex server, consult with the facility IT staff to identify the network printer and obtain a driver compatible with Windows 7 - 64 bit. Refer to the Connex CS Customer Project Req. Form, Section B for additional information.
  • Page 134: Change Date And Time

    Final Steps 2. Click on the printer, and then select Next. 3. Change the name of the printer as desired and select Next. 4. For printer sharing, select an option and then select Next. 5. Select Print a test page. and then select Finish. 6.
  • Page 135 7. Check the box for “Automatically adjust for Daylight Saving Time” to enable for the local as needed. This is on by default. 8. Select the Internet Time tab. a. Click on Change settings. b. Click on Synchronize with an Internet time server. c.
  • Page 136 Final Steps...
  • Page 137: Moving From Test To Production

    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. ...
  • Page 138: Create A Database Restore Point

    Final Steps 6. On the server, use the Windows Services tool to shut down Welch Allyn Connex CS services on the Connex server. Shut down services in the following order:  Process Monitor Service (if present)  Network Rendezvous Service ...
  • Page 139: Clearing Test Data From The Wadb Database

    Clearing test data from the WADB database Test data needs to be removed from the system acting as the server for deployment model.  For the client-server deployment, perform these steps on the Connex server.  For the stand-alone deployment, perform these steps on the central station PC. To remove test data: 1.
  • Page 140 Final Steps Figure H-2: Studio management navigation startup window 6. The Object Explorer should be visible on the left side menu. a. If you cannot see the object explorer, shown on the left side of the screen, click on View >...
  • Page 141 Figure H-4: CustomerPurge script contents in working window example 9. Click on or press the F5 key to run the script. After a few moments, the script output appears in a grid view table near the bottom of the working window. Note The amount of time it takes for the script to complete will vary slightly depending on how much test data is present in the database.
  • Page 142 Final Steps Figure H-5: Purge script output to screen example 10. Confirm that the yellow status bar at the bottom of the working window displays “Query executed successfully”. 11. Click on the Open File icon. Figure H-6: Open file icon on SSMS toolbar 12.
  • Page 143: Configure Hl7 Connections, If Required

    Figure H-7: Purge verification script output to screen example 14. Confirm that the yellow status bar at the bottom of the working window displays “Query executed successfully”. 15. Confirm that all counts appear as zeros. 16. Close the SSMS application. 17.
  • Page 144: Confirm Connex Server Operation, Client-Server Only

    Synchronize central stations, client-server only 1. At each central station, including and Warm Spare station, use the Windows Services tool to start all Welch Allyn Connex CS services on the central station PC. Start services in the following order:...
  • Page 145 3. Verify that each central station has synchronized with the Connex server database. This can be verified by performing any of the following on each central station: a. Within the Connex CS Application, navigate to the Patient list > Search tab and perform a patient search. The resulting list should return zero (0) records.
  • Page 146 Final Steps Figure H-9: Purge verification script output to screen example c. Using Windows explorer, navigate to C:\ProgramData\Welch Allyn\Welch Allyn Connex Data Synchronization Service 1.0 and check the sync logs on the central station for any errors.
  • Page 147: Restart After Synchronization Is Complete

    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.
  • Page 148: Troubleshooting Test To Production Issues

    Final Steps Troubleshooting test to production issues If problems arise in the process of moving from a test to production environment, at least two things can be done: “Connex database restore”, on the 1. Perform the database restore operation as outlined in the backup that was taken in the Create a database restore point section.
  • Page 149: Virtual Connex Server Field Installation

    6. Browse to the data store and folder using the client data store browser. 7. Right Click on the .vmx file in the folder. 8. Select “Add to Inventory”. This will launch a wizard to create the Connex CS Server virtual machine. 9. Confirm the name of the virtual machine.

Table of Contents