This manual provides information on installation and setup of Vital Sync™ virtual patient monitoring platform and informatics manager software components, as well as other software required
for their installation and use, including prerequisites, installation procedures, and configuration
details.
Note:
Before installation, carefully read this manual, any necessary system documentation, and precautionary
information and specifications.
1.2 Conventions
Text and terminology conventions used in this manual include the following:
•Button names, menu options, and field names generally appear in boldface text.
•The term “click” refers to the action activating buttons and menus in an application’s user interface. If
using a touchscreen monitor or mobile device, substitute “touch” for “click” where it appears in the text.
•The terms “platform”, “components”, “software”, and “software components” generally refer to part or all
of the Vital Sync™ virtual patient monitoring platform, the Vital Sync™ informatics manager, or both.
1.3 Labeling Symbols
This section contains definitions for the symbols used on the product labeling.
Table1-1.Labeling Symbol Definitions
SymbolDefinition
Federal (U.S.A.) law restricts the use of the application to sale by or on the order of a physician.
Consult instructions for use.
Manufacturer.
1-1
Introduction
Applicable Version
1.4
This manual applies to installing version 2.7 of the Vital Sync™ virtual patient monitoring platform
and informatics manager. Version information for supporting software is indicated in other sections
of this manual.
1.5 Safety Information
This section contains generally applicable safety information for this product.
1.5.1 Safety Symbols
SymbolDefinition
Table1-2.Safety Symbol Definitions
WARNING
Warnings alert users to potential serious outcomes (death, injury, or adverse events) to the
patient, user, or environment.
1.5.2 Warnings
WARNING:
The Vital Sync™ Virtual Patient Monitoring Platform and Informatics Manager is intended to
supplement and not to replace any part of the facility’s monitoring. Do not rely on the Vital Sync™
Virtual Patient Monitoring Platform and Informatics Manager as the sole source of alarms.
In order to assure a timely response to device alarms, a clinician (not necessarily the clinician viewing
data in the platform) must be within visual and/or audible range of the alarming device. In order to
provide medical intervention, a clinician must interact with the device at the bedside.
WARNING:
The platform is intended only as an adjunct in patient assessment. It must be used in conjunction with
clinical signs and symptoms and periodic patient observations.
Caution
Cautions alert users to exercise appropriate care for safe and effective use of the product.
Note
Notes provide additional guidelines or information.
1-2 Installation Manual
WARNING:
The dedicated bedside display unit is designed for use in conjunction with the Vital Sync™ Virtual
Patient Monitoring Platform and Informatics Manager. Do not rely on the dedicated bedside display
unit as a primary source of alarms.
WARNING:
Always follow the facility’s established patient safety protocols when using the Vital Sync™ Virtual
Patient Monitoring Platform and Informatics Manager.
WARNING:
The alarm rule functionality within the software is intended to supplement and not replace any part of
the facility’s monitoring. Do not rely on the platform as the sole source of alarms.
WARNING:
Alarm rules should adhere to facility policy, procedures, and alarm management protocols. This alarm
management protocol should address alarm safety and the potential impact of alarm fatigue in all
patient care areas within the facility.
Safety Information
WARNING:
Alarm priority normalization and ranking functionality within the software is intended to supplement
and not replace any part of the facility’s monitoring. Do not rely on the platform as the sole source of
alarms.
WARNING:
The default alarm priority is determined by the connected device, and cannot be changed on the device.
The same alarm condition may be reported with a different priority on different device models. Carefully
review the Alarm Normalization Report for default alarm priorities for each connected device model.
WARNING:
Alarm priorities in the software should not be set to be lower than those on the actual device. Use
caution if changing the priority of a device alarm in the software to a different level than is indicated on
the actual device, especially for devices that are life-sustaining.
WARNING:
Alarms from connected devices should not be set as notifications in the platform, especially for devices
that are life-sustaining. Because notifications do not audibly annunciate, setting an alarm as a
notification may cause users to not respond or delay in responding to a clinically significant event.
WARNING:
Notifications from connected devices should not be set as alarms in the platform, especially for events
not requiring clinical intervention. Setting a notification as an alarm may create nuisance audible alerts
that are not clinically significant.
Installation Manual 1-3
Introduction
WARNING:
If using audible alerts, ensure the sound volume of the PC or mobile device on which the software is
used is sufficient for alerts to be heard and recognized.
WARNING:
It is possible for the platform’s audible alert tone to be confused with audible alarm tones from
connected devices when in close physical proximity. Users should carefully attend to all audible
indicators when within audible range of connected devices.
WARNING:
When setting alarm rules and priorities in the software for any device, consult the operator’s manual for
the device in question for default priority levels of device alarms, and for a description of each device
alarm. Obtain a detailed understanding of the patient or device conditions that trigger any alarm before
creating an alarm rule or adjusting the alarm’s priority in the software.
WARNING:
Medtronic does not assume any responsibility for accuracy, reliability, or clinical relevance of userdesigned derived parameter algorithms.
1.5.3 Cautions
Caution:
Do not set alarm limits to extreme values that render the monitoring system useless. Ensure alarm limits
are appropriate for each patient.
Caution:
Connected devices report data to the platform periodically, not continuously. Because of this, as well as
delays caused by network bandwidth or hardware limitations or network loading, the true duration of
any device alarm will be longer than the delay set in this screen for that alarm.
Carefully consider these factors when choosing delay settings, and use the shortest delay settings that
are practical to reduce nuisance alarms, to avoid undue delay in response to events actually requiring
direct clinical intervention.
Caution:
Loss of patient privacy may occur if using the Vital Sync™ Virtual Patient Monitoring Platform and
Informatics Manager on unsecured or unencrypted networks. Always adhere to facility patient privacy
practices and procedures to ensure security of patient data on the facility’s network.
1-4 Installation Manual
1.5.4 Notes
Note:
Some mobile devices do not support the sounding of audible alerts from the platform due to device limitations.
Make sure to test audible alert capability on any mobile device to be used.
Note:
Audible alerts only sound to indicate alarms on devices linked to patients. Audible alerts do not sound for
notifications.
Note:
The platform has been verified on systems using Microsoft™* Windows™* and Windows™*-based software. User
experience may vary with other operating systems and hardware and software configurations.
1.6 Obtaining Technical Assistance
Obtaining Technical Assistance
1.6.1 Technical Services
For technical information and assistance, if unable to correct a problem while using the software,
contact Medtronic or a local Medtronic representative.
Medtronic Technical Services
15 Hampshire Street
Mansfield, MA 02048 USA
1 800 497 4968, or 1 925 463 4635,
or contact a local Medtronic representative
HIMSupport@Covidien.com
When calling Medtronic or a local Medtronic representative, provide the software version number,
build number and date of build, shown on the About screen.
1.6.2 Related Documents
Before installing, carefully read this manual as well as installation documentation for the supporting
software. This information is essential for understanding the installation process and information
shown during installation.
Installation Manual 1-5
Introduction
Warranty Information
1.7
The information contained in this document is subject to change without notice. Medtronic makes
no warranty of any kind with regard to this material, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. Medtronic shall not be liable for errors
contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
1.8 Licensing Information
For more details regarding software licenses, refer to the following sections.
1.8.1 Vital Sync™ and Third Party Software
Licenses obtained from Medtronic for use of the virtual patient monitoring platform (including the
informatics manager) do not include licenses for any third party software, including software identified in Chapters 2, 3, and 5 of this manual. (Refer to Prerequisites, page 2-1; Recommended Configu-
Users must obtain their own licenses for the downloading and use of such third party software.
1.8.2 Open Source Software Disclosure
This section identifies the open source software that may be separately called, executed, linked, affiliated, or otherwise utilized by this Vital Sync™ software product.
Such open source software is licensed to users subject to the terms and conditions of the separate
software license agreement for such open source software.
Use of the open source software by users of the Vital Sync™ virtual patient monitoring platform and
informatics manager shall be governed entirely by the terms and conditions of such license.
Obtain the source or object code and applicable license for any open source software at the following sites:
The Vital Sync™ Virtual Patient Monitoring Platform and Informatics Manager is a software application used in conjunction with electronic medical devices within the customer’s secure health information system. Healthcare providers using the software are expected to take appropriate security
measures to protect the confidentiality of all data created, stored or transmitted on their systems.
Although the software contains certain features to assist users in the users’ steps to protect their
data, Medtronic cannot provide any assurance that the user’s use of the software will comply with
HIPAA regulations or be otherwise in compliance with the customer’s obligations as a covered
entity.
Installation Manual 1-7
Introduction
Page Left Intentionally Blank
1-8 Installation Manual
2Product and Installation Overview
2.1 Overview
This chapter describes the requirements and general process for installation and configuration of
Vital Sync™ virtual patient monitoring platform and informatics manager software components,
as well as for supporting software.
2.2 Prerequisites
In order to install and use software components, the systems in question must meet certain hardware and operating system requirements, and must also have other supporting software installed
and configured. Instructions for installation and setup of some of the supporting software are
included in this manual.
Note:
To install software, administrative rights are required on the destination systems.
2.2.1 Minimum Requirements
See Table 2-1 and Table 2-2 for minimum hardware and software requirements.
Specific deployments may have higher minimum requirements than those listed here. Consult with Medtronic
Professional Services for more information.
External storageExternal tape or other customer-sourced
backup for data archive
Network100/1000 Mbps Ethernet
Wireless networkBandwidth (Kbps) equal to 5.7X+270Y
(X=number of active devices; Y=number of active display devices)
Table2-3.Minimum Software Requirements
RequirementServer with components installedCentral monitoring station
Operating systemMicrosoft™* Windows™* Server 2012 R2 StandardMicrosoft™* Windows™* 7 (64-bit)
Database softwareMicrosoft™* SQL Server™* 2012 Standard Edition R2
with Service Pack 4 (required only on the server hosting
the database component)
Supporting softwareMicrosoft™* Web Deploy 3.0
Internet Information Services (IIS) 8.0
Microsoft™* .NET Framework 4.6.2
None
desktop
None
Microsoft™* Internet Explorer 11
Adobe™* Reader™*
2-2 Installation Manual
2.2.2 Recommended Configuration
Note:
While all components can be installed on a single system, Medtronic recommends that the Informatics
Web and Database components should be installed on separate systems, especially if a large number of
users will be accessing and using the software, or if a large number of patients and devices will be connected
and monitored.
The Data Collection Service, Applet Manager Service (if used), and Informatics Web components should be
installed on a server separate from the Database component, so that resource-intensive functions requiring
database access (such as reporting) will not interfere with ongoing clinical operations. Refer to Distributed
Deployment, page 5-8, for more information.
See Table 2-4 for recommended software.
RequirementServers with components installedCentral monitoring station desktop
Prerequisites
Table2-4.Recommended Software
For best results when using Web browsers to access the software and perform program functions,
ensure that the display resolution is set to at least 1024 x 768 (1920 x 1080 for a central monitoring
station).
Note:
To maximize performance, and for best connectivity with remote devices, Medtronic recommends that the Vital
Sync™ virtual patient monitoring platform and informatics manager, its necessary supporting software, and
related applications (such as the Vital Sync™ early warning score application) should be the only applications
running on the systems on which they are installed.
Note:
Some mobile devices do not support sounding of audible alerts due to device limitations. Make sure to test
audible alert capability on all mobile devices to be used.
Operating systemMicrosoft™* Windows™* Server 2016 Standard
with all current updates
Database softwareMicrosoft™* SQL Server™* 2016 Standard Edition
with Service Pack 1 (required only on the system
hosting the database component)
Supporting softwareMicrosoft™* Web Deploy 3.0
Internet Information Services (IIS) 10.0
Microsoft™* .NET Framework 4.6.2)
Microsoft™* Windows™* 10 (64-bit)
None
Microsoft™* Edge (version 42) or Google™*
Chrome™* (version 67)
Adobe™* Reader™*
Installation Manual 2-3
Product and Installation Overview
Installation Process
2.3
Note:
Licenses obtained from Medtronic for installation and use of the Vital Sync™ virtual patient monitoring platform
(including the informatics manager) do not include licenses for any third party software identified in this chapter.
Users must obtain their own licenses for the downloading and use of such third party software.
2.3.1 Initial Installation
For a first-time installation of the software, the process includes the following steps:
•Ensure applicable supported updates for Microsoft™* Windows™* Server have been downloaded and
installed, as described in the release notes.
•Add IIS role services and (if necessary) message queuing. Refer to Add IIS Role Services and Install Message
Queuing (Chapter 3).
•Configure the default IIS application pool. Refer to Configure the IIS Application Pool (Chapter 3).
•Install and configure Microsoft™* SQL Server™*. Refer to Install the Database Server and Distributor Config-
uration (Chapter 3). The 2016 version of the software does not include Microsoft™* SQL Server™* Man-
agement Tools; if needed, install these separately.
•Set up database connectivity for remote users. Refer to Enable Remote Connection (Chapter 3).
•If needed to enable HL7 message and/or alarm message availability for external systems, configure the
Vital Sync HL7 Reporter Service, Vital Sync ADT In Adapter Service, and Vital Sync Alarm Reporter Service.
Refer to Connectivity to External Systems (Chapter 6).
•If needed, perform LDAP and active directory server integration. Refer to Connectivity to External Systems
(Chapter 6).
•If using a Lantronix™* gateway with the Vital Sync™ software, enable and configure unique device iden-
tification. Refer to Connectivity to External Systems (Chapter 6).
•Start database agents running to fully enable replication. Refer to Database Agent Startup (Chapter 5).
•Confirm that firewall ports are properly configured to allow the software to communicate with the
network and with devices to be monitored. Refer to Firewall Configuration (Chapter 5).
•Perform date and time synchronization on all systems. Refer to Time Synchronization (Chapter 5).
•If needed, configure reporting to connect to the Data Warehouse server. Refer to Distributed Deployment
(Chapter 5).
•For a multi-system deployment, perform additional configuration procedures as needed. For an example
of such a deployment, refer to Distributed Deployment (Chapter 5).
2-4 Installation Manual
2.3.2 Upgrade Installation
To upgrade from a previous version of the software, the process includes the following steps:
•Before installing any software, make backups of all application database files created with the previous
installation of the software, and save the backups in a safe location. The backup process prevents data
loss in the event that problems occur during installation of the current version of the software.
•Ensure supporting software is already installed on all systems to be used with the upgraded version, as
described in Chapter 3. Additional installation of supporting software should not be necessary unless the
deployment configuration has changed from that used for the previous version of the software.
•If needed, perform additional configuration procedures as described in Chapter 5 and Chapter 6. Addi-
tional steps necessary will vary depending on deployment.
Note:
If upgrading from a version of the software previous to v2.5.x, uninstall the older version before installing the
current version.
Installation Process
if upgrading from version 2.5.x of the software, to avoid potential problems with database functions, first
upgrade to version 2.6.x, then upgrade to version 2.7.0.
Installation Manual 2-5
Product and Installation Overview
Page Left Intentionally Blank
2-6 Installation Manual
3Supporting Software
3.1 Overview
This chapter provides details on installing and configuring supporting software required before
installing Vital Sync™ virtual patient monitoring platform and informatics manager software components.
The primary task is the installation of Microsoft™* SQL Server™* on the system where certain specific Vital Sync™ software components will reside.
At certain points, the following steps are also required to allow systems and software components
to communicate and properly exchange information:
•Adding Microsoft™* Windows™* Server Internet Information Services (IIS) roles and configuring the
default application
•Configuring the database servers to allow replication
•Enabling remote connection to the database servers
Note:
Licenses obtained from Medtronic for installation and use of the Vital Sync™ virtual patient monitoring
platform (including the informatics manager) do not include licenses for any third party software identified in
this chapter. Users must obtain their own licenses for the downloading and use of such third party software.
Note:
To install and configure software, administrative rights are required on destination systems.
Note:
Setup and configuration procedures in this chapter are to support the Vital Sync™ virtual patient monitoring
platform and informatics manager software,
3.2 Operating System Updates
Before performing any procedures detailed in this manual, ensure supported Microsoft™* Windows™* service packs and updates have been downloaded to and installed on the affected
system or systems. Reference the release notes for this version of the software for more information.
3-1
Supporting Software
Add IIS Role Services
3.3
After ensuring that supported operating system updates and service packs are installed, add IIS role
services.
The Add Roles wizard shows a series of screens for selection of options. If changes are required to
selections already made, click Back to go back to the previous screen, then make the change.
In any screen, if needed, click Cancel to stop configuration and exit the wizard.
Note:
Add IIS role services to the same system where the Data Collection Service and Informatics Web components
are to be installed. (Refer to Distributed Deployment, page 5-8, for details on installation in a distributed
environment.)
Note:
This manual shows screen captures for adding IIS role services using version 8.0 of IIS. Version 7.0 of IIS is also
supported. The procedure does not differ significantly between the two versions. If encountering problems
during or after adding IIS role services, contact Medtronic Professional Services.
To add IIS role services:
1.
From the Start menu, select Administrative Tools.
2.
Open the Server Manager.
Figure3-1.Server Manager
3.
In the Dashboard pane, click on Add Roles and Features to start the Add Roles and Features wizard.
3-2 Installation Manual
Add IIS Role Services
Figure3-2.IIS Add Roles and Features Wizard—Start Page
4.
Verify that tasks listed on the page have been completed, then click Next to access the Installation Type
page.
Figure3-3.IIS Add Roles and Features Wizard—Installation Type Page
5.
Click the Role-based or feature-based installation radio button if it is not already selected.
6.
Click Next to access the Destination Server Selection page.
Installation Manual 3-3
Supporting Software
7.
Click the Select a server from the server pool radio button if it is not already selected.
Figure3-4.IIS Add Roles and Features Wizard—Destination Server Selection Page
8.
In the Server Pool pane, find the desired server and click on it to select it.
9.
Click Next to access the Select Server Roles page.
Figure3-5.IIS Add Roles and Features Wizard—Select Server Roles Page
10.
Check the Web Server (IIS) check box, then click Next to access the Add Required Features page.
3-4 Installation Manual
Add IIS Role Services
Figure3-6.IIS Add Roles and Features Wizard—Add Required Features Page
11.
Ensure that the Include management tools check box is checked, then click Add Features to access
the Select Features page.
Figure3-7.IIS Add Roles and Features Wizard—Select Features Page
12.
Click the triangle next to the .NET Framework 4.6 Features check box to show available options.
Installation Manual 3-5
Supporting Software
13.
Click the triangle next to the WCF Services check box to show available options.
Figure3-8.IIS Add Roles and Features Wizard—Select Features Page (.NET Framework 4.6 fields shown)
14.
Make selections as shown in Figure 3-8, then click Next to access the Web Server Role (IIS) page.
Figure3-9.IIS Add Roles and Features Wizard—Web Server Role (IIS) Page
15.
If needed, review the text on the page, then click Next to access the Select Role Services page.
3-6 Installation Manual
Add IIS Role Services
Figure3-10.IIS Add Roles and Features Wizard—Select Role Services Page (common HTTP and health/diagnostics options)
16.
Make selections in the role services fields as shown in Figure 3-10, then scroll down in the pane.
Figure3-11.IIS Add Roles and Features Wizard—Select Role Services Page (performance and security options)
17.
Make additional selections in the role services fields as shown in Figure 3-11, then scroll down in the
pane.
Installation Manual 3-7
Supporting Software
18.
Make additional selections in the role services fields as shown in Figure 3-12, then click Next to access
the confirmation page.
Figure3-12.IIS Add Roles and Features Wizard—Select Role Services Page (application development options)
Figure3-13.IIS Add Roles and Features Wizard—Confirmation Page
19.
If desired, scroll down to view installation selections, then click Install. (Click Cancel to stop installation.)
20.
The results screen indicates whether the installation was successful, and lists role services installed. If
desired, click the Print, e-mail, or save link to print, e-mail or save the installation report, then click Close
to exit the wizard.
Note:
If installation is unsuccessful, problems that occurred will be shown in the results screen. Resolve the problems
and repeat the procedure for adding IIS role services before continuing with the other procedures in this
chapter.
3-8 Installation Manual
Install Message Queuing
3.4
After adding IIS role services, add the Microsoft™* Message Queuing feature. For details on installation, reference the technical document Installing and Managing Message Queuing, available online
at the following URL:
Installing message queuing is only necessary if configuring the Vital Sync Alarms Reporter Service. See MSMQ
Queue Configuration on page 6-6 for details.
Note:
Install message queuing on the same systems where IIS role services were just added. (Refer to Distributed
Deployment, page 5-8, for details on installation in a distributed environment.)
Install Message Queuing
3.5 Configure the IIS Application Pool
After adding IIS role services, update the default Microsoft™* Windows™* Server Internet Information Services (IIS) application pool to ensure that the Informatics Web component (when installed)
will have appropriate authority to run reports.
Note:
Configure the IIS application pool on the same systems where IIS role services are installed.
Note:
This manual shows screen captures for application pool configuration using version 10.0 of IIS. Version 8.0 of IIS
is also supported. The procedure does not differ significantly between the two versions. If encountering
problems during or after configuration, contact Medtronic Professional Services.
Installation Manual 3-9
Supporting Software
To configure the IIS application pool:
1.
Open the IIS Manager.
Figure3-14.Internet Information Services (IIS) Manager (application pools shown)
2.
Click Application Pools in the far left pane.
3.
Click on DefaultAppPool to select it, then click Advanced Settings under Edit Application Pool in the
far right pane to open the Advanced Settings dialog.
In the Identity field, click the ... button to open the Application Pool Identity dialog.
3-10 Installation Manual
Configure the IIS Application Pool
Figure3-16.Application Pool Identity Dialog
5.
Click the Custom account radio button, then click Set to open the Set Credentials dialog.
Figure3-17.Set Credentials Dialog
6.
User name—Enter the user name for an appropriate administrative user with authority to run reports.
Often, the same user will also be set up as the administrator when Microsoft™* SQL Server™* is installed.
Refer to Install the Database Server, page 3-12.
7.
Password—Enter the password for the specified administrative user.
8.
Confirm password—Enter the password just entered in the Password field.
9.
Click OK to save and return to the Application Pool Identity dialog.
10.
Click OK to save application pool identity settings and return to the Advanced Settings dialog.
11.
Click OK to save advanced settings for the default application pool and return to the IIS Manager.
12.
Exit the IIS Manager.
Installation Manual 3-11
Supporting Software
Install the Database Server
3.6
After configuring the IIS application pool, install and configure the database server software.
The installation wizard shows a series of screens for selection of application options. needing to
change a selection already made, click Back to go back to the previous screen, then make the
change.
In any screen, if needed, click Cancel to stop the installation and exit the wizard.
Note:
Install the database server software on the system where the Database component is to be installed. If using a
distributed deployment with separate Online Transaction Processing (OLTP) and Data Warehouse systems,
install the database server software on both systems.
To access the installation program:
1.
Find and right-click on the icon for the computer on the desktop, then click Explore, or navigate to the
computer in Windows Explorer™*.
2.
Double-click on the directory containing the installation files to open the directory.
3.
Note:
Refer to Distributed Deployment, page 5-8, for details on additional installation and setup steps for distributing
database operations across multiple systems.
Note:
This manual shows the installer for Microsoft™* SQL Server™* 2016. Microsoft™* SQL Server™* 2012 is also
supported. The installation procedure for Microsoft™* SQL Server™* 2012 does not differ significantly; refer to its
installation documentation for more detailed information. If encountering problems during or after installing
Microsoft™* SQL Server™*, contact Medtronic Professional Services.
To install Microsoft SQL Server:
1.
2.
Find Setup.exe.
Double-click Setup.exe to run the installer.
If a user account control dialog appears asking for confirmation that changes should be made to this
computer, click Yes to continue. The Installation Center screen will appear, allowing selection of the type
of installation to perform.
3-12 Installation Manual
Figure3-18.Microsoft™* SQL Server™* Installation Center
Install the Database Server
3.
Click Installation in the left panel.
4.
Click New SQL Server stand-alone installation or add features to an existing installation to open
the setup wizard and access the Product Key page.
Click the Enter the product key radio button to access the product key field, then (if needed) enter the
25-character product key provided with Microsoft™* SQL Server™*. Click Next to proceed to the License
Terms page.
Installation Manual 3-13
Supporting Software
Note:
If the software was downloaded directly from the manufacturer, the product key may automatically appear on
this page.
End-user license agreement (EULA) terms are shown in the License Terms page. If desired, click Copy to
copy the EULA text to the clipboard; click Print to print the EULA.
7.
To continue with the installation, click the I accept the license terms check box (and the Send feature
usage data check box if desired), then click Next to proceed.
8.
The installer will check for problems that could arise from installing support files. A progress bar shows
the level of completion of the check.
Users must resolve the underlying cause of any operation indicated as having failed before the installation can
proceed.
Users should check the underlying cause of any operation indicated as having a warning, but operations with
warnings do not prevent the installation from continuing.
9.
Click Show Details to view a list of items checked; click Hide Details to hide the list. If the check indicates
problems, resolve them, then click Re-run.
The installer will automatically check for any updates, and will automatically download and extract the
updates if any are available.
When the update check is complete, the wizard will proceed to the Product Updates page. If updates
are available, a list of the updates downloaded appears on the screen, including links to a document
showing more information about each update. If no updates are currently available, a message indicating this will appear. In either case, click Next to proceed to the Install Setup Files page.
The installer will automatically install setup files. The status of this operation and the product update
operations are shown in the middle of the page.
3-16 Installation Manual
12.
Note:
Users must resolve the underlying cause of any operation indicated as having failed before the installation can
proceed.
Users should check the underlying cause of any operation indicated as having a warning, but operations with
warnings do not prevent the installation from continuing.
Install the Database Server
When finished installing setup files, the wizard will proceed to the Install Rules screen and will automatically check for problems that could arise from installing support files. A progress bar shows the level of
completion of the check.
Click Show Details to view a list of items checked; click Hide Details to hide the list. If the check indicates
problems, resolve them, then click Re-run.
13.
After resolving any problems, or if no problems occur, click Next to proceed to the Feature Selection
page.
Make selections in the Instance Features and Shared Features check boxes as shown in Figure 3-25,
then click Next to proceed to the Feature Rules page.
Users must resolve the underlying cause of any operation indicated as having failed before the installation can
proceed.
Users should check the underlying cause of any operation indicated as having a warning, but operations with
warnings do not prevent the installation from continuing.
16.
The installer will again check for problems that could interfere with installation. A progress bar shows the
level of completion of the check. Click Show Details to view a list of items checked; click Hide Details
to hide the list.
If the check indicates problems, resolve them, then click Re-run.
After resolving any problems, click Next to proceed to the Instance Configuration page.
If no SQL server instances exist on the system, click the Default Instance radio button. Otherwise, click
the Named Instance radio button and enter a name for the new instance. When ready to continue, click
On the Service Accounts tab, ensure NT Service\SQLSERVERAGENT appears in the Account Name
column for SQL Server Agent, and NT Service\MSSQLSERVER appears in the Account Name column
for SQL Server Database Engine.
Installation Manual 3-19
Supporting Software
19.
In the Startup Type column, make selections from the appropriate drop-down boxes as shown in Figure
3-28.
20.
Click Next to proceed to the Database Engine Configuration page.
On the Account Provisioning tab, in the Authentication Mode area, click the Mixed mode radio button.
22.
Enter the desired authentication password in the Enter password and Confirm password fields.
23.
Below the Specify SQL Server Administrators pane, click Add Current User to add the current user as an
administrator for this SQL server instance. The username of the current user will appear in the pane.
If desired, click the check box to send error reports to Microsoft or a corporate server, then click Next to
proceed to the Feature Configuration Rules page.
Users must resolve the underlying cause of any operation indicated as having failed before the installation can
proceed.
Users should check the underlying cause of any operation indicated as having a warning, but operations with
warnings do not prevent the installation from continuing.
27.
The installer will once again check for any problems that could interfere with installation. A progress bar
shows the level of completion of the check. Click Show Details to view a list of items checked; click Hide Details to hide the list.
If the check indicates problems, resolve them, then click Re-run.
After resolving any problems, click Next to proceed to the Ready to Install page.
3-22 Installation Manual
Figure3-33.Microsoft™* SQL Server™* Setup Wizard—Ready to Install Page
Install the Database Server
28.
The Ready to Install page shows all software components to be installed on the destination machine.
Review the list if desired, then click Install.
29.
Once the installer has finished, the finish page will appear.
If no problems occurred during installation, a message indicating successful installation (denoted by a green
check mark) will appear. If any problem occurred, a descriptive message (denoted by a red octagon) will appear.
30.
After reviewing installation information, click Close to exit the installation wizard. (If problems occurred
during installation, resolve them, then repeat this procedure until installation is successful.)
31.
If desired or otherwise indicated, restart the system before continuing with the additional application
installation and configuration procedures detailed in this manual.
3.7 Distributor Configuration
After installing the database server software, configure the database server as a distributor to enable
and support replication.
The configuration wizard shows a series of screens for selection of application options. If changes
are required to selections already made, click Back to go back to the previous screen, then make
the change.
In any screen, if needed, click Cancel to stop configuration and exit the wizard.
Note:
The default configuration selections indicated here are recommended. If different selections are required,
consult with Medtronic Professional Services.
Note:
The procedure shown in this section assumes that Microsoft™* SQL Server™* 2016 is installed. If Microsoft™* SQL
Server™* 2012 is installed, the procedure does not differ significantly. If encountering problems, consult with
Medtronic Professional Services.
Note:
Server names shown in this section are for illustrative purposes only; actual server names will vary.
To configure the database server as a distributor:
1.
In the Object Explorer in Microsoft™* SQL Server™* Management Studio, find the SQL database server
installed for use with the Vital Sync™ software.
3-24 Installation Manual
Distributor Configuration
Figure3-35.Microsoft™* SQL Server™* Management Studio Object Explorer—Replication Folder Context Menu
2.
Right-click on the Replication folder icon to open a context menu, then select Configure Distribution
to launch the Configure Distribution wizard.
Figure3-36.Configure Distribution Wizard—Start Page
3.
Click Next to proceed to the Distributor page.
Installation Manual 3-25
Supporting Software
4.
Make sure the top radio button (indicating that this server will act as its own distributor) is selected, then
click Next to proceed to the SQL Snapshot Folder page.
Figure3-37.Configure Distribution Wizard—Distributor Page
Figure3-38.Configure Distribution Wizard—Snapshot Folder Page
5.
Click Next to accept the default path for the snapshot folder and proceed to the Distribution Database
page.
3-26 Installation Manual
Distributor Configuration
Figure3-39.Configure Distribution Wizard—Distribution Database Page
6.
Click Next to accept the default distribution database name and default paths for the database and database log files, and proceed to the Publishers page.
Figure3-40.Configure Distribution Wizard—Publishers Page
7.
Make sure the check box next to the database just installed is checked, then click Next to proceed to the
Wizard Actions page.
Installation Manual 3-27
Supporting Software
8.
Make sure the Configure distribution check box is checked, then click Next to proceed to the finish
page.
Figure3-41.Configure Distribution Wizard—Wizard Actions Page
Figure3-42.Configure Distribution Wizard—Finish Page
9.
Review selections, then click Finish to configure distribution.
3-28 Installation Manual
Distributor Configuration
Figure3-43.Configure Distribution Wizard—End Page
10.
A screen indicating progress will appear; green check marks indicate success of each operation. If any
problems occur during configuration, click Report to view details, then resolve any issues and rerun the
wizard.
11.
Note:
If configuration is unsuccessful, it is possible the SQL Server Agent is not set to automatically launch. Check the
status of the SQL Server Agent in the SQL Server Configuration Manager; ensure that the agent is running and
set to Automatic. Refer to Enable Remote Connection, page 3-30, for access details.
On completion of distributor configuration, a new database icon will be visible in the System Databases list in the Microsoft™* SQL Server™* Management Studio Object Explorer. This icon will have
the name selected in the distribution database setup screen (refer to step 6 of this procedure).
If no problems occur, or once problems are resolved and rerunning the wizard indicates success for all
configuration operations, click Close to exit the wizard.
Installation Manual 3-29
Supporting Software
Figure3-44.Microsoft™* SQL Server™* Management Studio Object Explorer (new database shown)
3.8
Enable Remote Connection
After installing all supporting software and application components, adjust the database configuration to enable remote users to connect to the database.
Note:
Only perform the steps listed in this section if application components are installed on multiple systems. If using
a distributed deployment with separate Online Transaction Processing (OLTP) and Data Warehouse systems,
perform the steps in this section on both systems.
Note:
The procedure shown in this section assumes that Microsoft™* SQL Server™* 2016 is installed. If Microsoft™* SQL
Server™* 2012 is installed, the procedure does not differ significantly. If encountering problems, consult with
Medtronic Professional Services.
To enable remote connection:
1.
2.
3.
Launch the SQL Server Configuration Manager.
In the left pane, click on SQL Server Services.
Right-click on SQL Server Browser (in the right pane) to open a context menu.
3-30 Installation Manual
Figure3-45.Microsoft™* SQL Server™* Configuration Manager—SQL Server Browser Context Menu
4.
Select Properties to open the Properties window.
Figure3-46.Microsoft™* SQL Server™* Configuration Manager—SQL Server Browser Properties Dialog
Enable Remote Connection
5.
Click on the Service tab to access it.
6.
Click on the drop-down box next to Start Mode and select Automatic.
7.
Click OK to exit the Properties window and return to the SQL Server Configuration Manager window. In
the right pane, the value in the State column for the SQL Server Browser should be Running.
8.
In the left pane, click on the triangle next to the SQL Server Network Configuration icon to expand the
directory, then click on Protocols for MSSQLSERVER (or the server and instance name selected for the
database during installation, if different) to show protocols in the right pane.
9.
Check the value in the Status column in the right pane for the TCP/IP protocol. If not set to Enabled,
right-click on TCP/IP to open a context menu.
10.
Select Properties to open the Properties window.
Installation Manual 3-31
Supporting Software
11.
Click on the drop-down box next to Enabled and select Yes.
Click OK to return to the SQL Server Configuration Manager window.
13.
Check the value in the Status column in the right pane for the Named Pipes protocol. If not set to
Enabled, right-click on Named Pipes to open a context menu.
Click on the drop-down box next to Enabled and select Yes.
16.
Click OK to return to the SQL Server Configuration Manager window.
3-32 Installation Manual
Enable Remote Connection
17.
In the left pane, click on the plus sign next to the SQL Native Client 11.0 Configuration (32bit) icon to
expand the directory if needed, then click on Client Protocols to show protocols in the right pane.
Ensure the value in the Enabled column both for TCP/IP and for Named Pipes is Enabled. If not, apply
steps 9 through 15 of this procedure as needed to change affected items.
19.
A warning dialog will appear indicating that the client protocol changes will be saved, but will not take
effect until affected services are restarted. Click OK to save changes and return to the SQL Services Configuration Manager window.
20.
In the left pane, click on the triangle next to the SQL Native Client 11.0 Configuration icon to expand
the directory if needed, then click on Client Protocols to show protocols in the right pane.
Ensure the value in the Enabled column both for TCP/IP and for Named Pipes is Enabled. If not, apply
steps 9 through 15 of this procedure as needed to change affected items.
22.
A warning dialog will appear indicating that the client protocol changes will be saved, but will not take
effect until affected services are restarted. Click OK to save changes and return to the SQL Services Configuration Manager window.
23.
In the left pane, click on SQL Server Services.
24.
In the right pane, the value in the State column for the SQL Server Browser should be Stopped. Rightclick on SQL Server Browser to open a context menu.
Installation Manual 3-33
Supporting Software
25.
Select Start to start the SQL Server Browser running.
26.
Right-click on SQL Server (MSSQLSERVER) (or if different, the server and instance name selected during
installation) to open a context menu.
Figure3-51.Microsoft™* SQL Server™* Configuration Manager—SQL Server Browser Start
Figure3-52.Microsoft™* SQL Server™* Configuration Manager—SQL Server Restart
27.
Select Restart to restart the SQL server service, with the configuration changes made.
28.
Right-click on SQL Server Agent (MSSQLSERVER) (or if different, the server and instance name selected
for the database during installation) to open a context menu.
3-34 Installation Manual
Figure3-53.Microsoft™* SQL Server™* Configuration Manager—SQL Server Agent Restart
29.
Select Restart to restart the SQL server agent, with the configuration changes made.
Enable Remote Connection
Installation Manual 3-35
Supporting Software
Page Left Intentionally Blank
3-36 Installation Manual
4Installing Software Components
4.1 Overview
This chapter provides information on installation of components of the Vital Sync™ virtual patient
monitoring platform and informatics manager software.
Note:
While all components can be installed on a single system, Medtronic recommends that the
Informatics Web and Database components should be installed on separate systems, especially if a
large number of users will access and use the software, or if a large number of patients and devices will be
connected and monitored. Reference hardware and software configurations in Chapter 2, or consult with
Medtronic Professional Services or with facility IT personnel for more information.
Note:
If upgrading from a previous version, make backups of all database files before installing the current version
of the software.
Note:
If upgrading from a version of the software previous to v2.5.x, uninstall the older version before installing the
current version.
If upgrading from version 2.5.x, to avoid potential problems with database functions, first upgrade to version
2.6.x before upgrading to version 2.7.0.
4.2 Installation
All components are included in the Vital Sync™ software installation package, received from
Medtronic Professional Services.
Note:
To install software, administrative rights are required on destination systems.
4-1
Installing Software Components
4.2.1 Component Constraints
Certain components must be installed on specific systems, based on the supporting software
installed on those systems.
•Install the Database component on a system where Microsoft™* SQL Server™* is already installed.
•Install the Data Collection Service, Applet Manager Service (if used), Reports, and Informatics Web com-
ponents on the same system where Microsoft™* Windows™* Server IIS role service and application pool
setup is already complete.
Reference Chapter 3 for more information on supporting software. Reference Chapter 5 for more
information on multi-system installation.
4.2.2 Access
To access the installer:
1.
Find and right-click on the icon for the computer on the desktop, then click Explore, or navigate to the
computer in Windows™* Explorer™*.
2.
Navigate to the following location in the directory where the installation files reside: Installers\Virtual
Patient Monitoring Platform
3.
Find informatics_setup.exe.
4.2.3 Component Installation
The installation wizard shows a series of screens for selection of software options. If needing to
change a selection already made, click Back to go back to the previous screen and make the
change.
In any screen, if needed, click Cancel to stop the installation and exit the wizard.
To install components:
1.
Double-click Informatics_setup.exe to run the installer.
2.
If a dialog appears asking for confirmation that changes should be made to this computer, click Yes to
continue.
3.
If Microsoft™* .NET Framework 4.6.2 is not present on the system, the Requirements page will appear.
Click Install to install the missing software, entering administrative user credentials if necessary to
confirm the installation. (Click Cancel to exit the installation wizard.)
Note:
The Microsoft™* Web Deploy utility is installed along with the Vital Sync™ software components.
4-2 Installation Manual
4.
The system may need to be rebooted before continuing. If so, log onto the system after rebooting, using
the same credentials. The installation wizard should automatically start again; if not, restart the wizard
(see Access on page 4-2).
5.
Once all necessary supporting software is installed on the system, the Welcome page will appear.
Click Next to proceed to the Feature License Information page.
Figure4-2.Informatics Installation Wizard—Feature License Information Page
7.
Serial Number—Enter the license key received from Medtronic Professional Services.
8.
License File—Enter the filename of the license file received from Medtronic, or click Browse... and navigate to the directory where the license file resides. The license file has a .lic file extension, and will typically have the license key as its filename.
Note:
The license file is provided directly by Medtronic Professional Services, separately from the other installation files.
9.
Click Next to proceed to the Destination Location page.
Installation Manual 4-3
Installing Software Components
10.
The Destination Location page shows the default destination location for installation of software components. If the components should be installed in a different location, click Browse and navigate to the
desired location. When finished, or if accepting the default location, click Next to proceed to the Select
Features page.
If installing on multiple systems, some components must be installed on specific systems. Refer to Component
Constraints, page 4-2, and Distributed Deployment, page 5-8.
Figure4-4.Informatics Installation Wizard—Select Features Page
The Select Features page shows available components, as well as the amount of disk space required to
install selected components (currently selected components are denoted by checked boxes). Click on
any component listed to show a brief description of that component in the Description pane.
Note:
Depending on the licensing status of components in the installation package, not all screens shown in this
procedure description may appear. For details on licensing of individual components, consult with Medtronic.
4-4 Installation Manual
12.
Note:
If a component is not currently licensed, its check box will be unchecked when this page first appears. The
description will still appear when clicking an unlicensed component, but will indicate that the component is
unlicensed; the component’s check box for selection will be unavailable.
Note:
The Nurse Station Client component and the Bedside Station Client component cannot be installed
simultaneously. If installing either of these components, make sure the check box for the other component is
unchecked before proceeding.
13.
Installation
Click in check boxes to check or uncheck them until all components to be installed are selected (indicated by a checked box).
Click Next to proceed to the Language Options page.
English is the only language available to be shown in the software user interface, and is already selected.
Click Next to proceed.
15.
If creating an account for a central nurse station (as chosen in step 12), the Nurse Station Account Creation page will appear. (If not creating this account, skip to step 24. If not creating a central nurse station
account or a bedside display user account, the Failover Log File page will appear; skip to step 33.)
Installation Manual 4-5
Installing Software Components
16.
Account User Name—Enter the username of the nurse station account (this can be the name of the
nurse station at which the platform is to be used).
17.
Display Name—Enter the display name for the nurse station. (This name will appear on the user function button in the platform user interface.)
Figure4-6.Informatics Installation Wizard—Nurse Station Account Creation Page
Note:
The display name should be as short as is practical; space on the user function button is limited.
18.
19.
20.
21.
22.
23. Click Next to proceed.
24.
Device Data Service Location—Enter the host name or IP address for the system on which the Device
Data Service component is to be installed.
Admin User—Accept the default value (administrator).
Admin Password—Accept the default value, or enter a password conforming to facility guidelines.
Vital Sync Web Server Location—Enter the host name or IP address for the system on which the Vital
Sync Web Server component is to be installed.
Overwrite User—Accept the default value (unchecked) to create a new account, or check the box to
overwrite an existing central nurse station account (also called a remote monitoring station account in
earlier releases of the software).
If creating an account for a bedside display user, the Bedside Monitoring Station Account Creation page
will appear. (If not creating this account, skip to step 33.)
4-6 Installation Manual
Figure4-7.Informatics Installation Wizard—Bedside Monitoring Station Account Creation Page
Installation
25. Bed Name
26. Bedside Account Name
—Enter the name of the bed at which the bedside display is to be used.
—Enter the name for the bedside account. (This name will appear in the plat-
form user interface.)
27. Device Data Service Location
—Enter the hostname or IP address for the system on which the Infor-
matics Web component is to be installed.
28. Admin User
29. Admin Password
30. Vital Sync Web Server Location
—Accept the default value (
administrator
—Accept the default value, or enter a password conforming to facility guidelines.
—Enter the hostname or IP address for the system on which the Infor-
matics Web component is to be installed.
31. Overwrite User
—Accept the default value (unchecked) to create a new account, or check the box to
overwrite an existing bedside monitoring station account.
32.
Click Next to proceed to the Failover Log File page.
The default location for the failover log file (the file in which the software will record events if the regular
event log is inaccessible) is shown. If desired, enter an alternate directory path, or click Browse and navigate to the desired directory. When finished, or if accepting the default location, click Next to proceed.
34.
If the selected destination folder for the failover log file does not exist, a dialog will appear asking if the
folder should be created. Click Yes to create the folder and proceed to the Primary (Informatics) Database Information page, or click No to return to the failover log location screen to select an existing folder,
then click Next to proceed.
Figure4-9.Informatics Installation Wizard—Primary (Informatics) Database Information Page
35.
Note:
If using distributed deployment, with a dedicated Online Transaction Processing (OLTP) system supporting
primary clinical and supervisory operations, enter information for the SQL server instance on the OLTP system
into the fields on the Operations Database Information page. Refer to Distributed Deployment, page 5-8.
Note:
Network configuration settings may require an IP address to be used instead of a server name alone. If so,
append the IP address after the server name, separating them with an @ sign (e.g., ServerName@100.12.15.88).
If needed, consult with facility IT personnel to obtain the IP address of the system where the SQL server instance
is installed.
36.
37.
Server—Enter the server name for the SQL server instance that will support primary clinical and supervisory operations. (Use the server name selected during SQL server software installation on the system
where the SQL server instance that supports operations is installed. Reference Install the Database Server,
step 17.)
Instance—If using the default instance, leave this field blank. If not using the default instance, enter the
instance name for the instance to be used.
Database File Location—If not using the default directory path, enter the desired directory path for the
database file.
38.
Log File Location—If not using the default directory path, enter the desired directory path for the log
file.
4-8 Installation Manual
39.
When finished, click Next to proceed to the Primary (Informatics) logon information page.
Figure4-10.Informatics Installation Wizard—Primary (Informatics) Logon Information Page
40.
User Name—Enter sa.
41.
Password—Enter the password set up for the SQL server instance that will support primary clinical and
supervisory operations. (Refer to Install the Database Server, step 22.)
Installation
42.
Click
Next
to proceed.
43.
If a primary operations database already exists on the system (for example, if an older version of the software was previously installed), a dialog will appear, with a warning that the existing database will be
overwritten during installation.
If backups already exist for the primary operations database file used with the earlier version of the software,
click Yes to proceed to the Replication (Informatics Data Warehouse) and DataMart page. If not, click No to
return to the previous screen, then click Cancel to exit the installation wizard. (After creating a backup of the
database file, reopen the installation wizard and repeat all previous steps in this procedure, then click Yes in
the dialog when it appears again to proceed with installation.)
Installation Manual 4-9
Installing Software Components
Figure4-12.Informatics Installation Wizard—Replication (InformaticsDataWarehouse) and DataMart Page
45.
Server—Enter the server name for the SQL server instance that will support the Informatics Data Warehouse and DataMart database.
Note:
If using distributed deployment, with a dedicated Data Warehouse system supporting reporting functions, enter
information for the SQL server instance on the Data Warehouse system into the fields on the Reporting Database
Information page. Refer to Distributed Deployment, page 5-8.
46.
Instance—Enter the instance name for the desired SQL server instance, if needed.
47.
Database File Location—If not using the default directory path, enter the desired directory path for the
database file.
48.
Log File Location—If not using the default directory path, enter the desired directory path for the log
file.
49.
When finished, click Next to proceed. If using separate instances for primary clinical and supervisory
operations and for reporting functions, the Replication (Informatics Data Warehouse) and DataMart
logon information page will appear.
4-10 Installation Manual
Figure4-13.Informatics Installation Wizard—Replication (InformaticsDataWarehouse) and DataMart Logon Information Page
Note:
If using the same instance for both primary operations and reporting functions, the Reporting Logon
Information page will not appear.
Installation
50.
User Name—Enter sa.
51.
Password—Enter the password set up for the SQL server instance that will support reporting functions.
(Refer to Installing the Database Server, step 22.)
52.
Click Next to proceed.
53.
If a database for primary functions and/or reporting is already installed, but the installation currently in
progress is not an upgrade, a confirmation dialog will appear indicating that the existing databases will
be deleted when the new databases are created. Click OK to proceed to the Enable Replication page, or
click Cancel to exit the installation wizard if the existing databases should be backed up before proceeding.
The directory path for the manual is provided by Medtronic Professional Services at the time of installation.
57.
Enter the directory path to the electronic version of this reference manual, or click Browse... and navigate to the directory where the file resides. The reference manual file has a .pdf file extension.
Click Next to proceed to the Report Server URL page.
Figure4-16.Informatics Installation Wizard—Report Server URL Page
58.
URL—The default URL for the report server is shown. If desired, enter an alternate URL. When finished,
or if accepting the default location, Enter the URL for the report server.
4-12 Installation Manual
Note:
The report server URL is provided by Medtronic Professional Services at the time of installation.
59.
60.
Installation
Click Next to proceed.
If installing the Alarms Out to SMTP component (selected in step 12), the Alarms Out Email Settings page
will appear. (If not installing this component, skip to step 68.)
Figure4-17.Informatics Installation Wizard—Alarms Out Email Settings Page
Note:
The facility must have existing email services from an appropriate provider in order to use the Alarms Out to
SMTP functionality. Obtain settings information for entry in the Alarms Out Email Settings page from facility IT
personnel.
61.
62.
63.
64.
65.
66.
67.
68.
SMTP URL—Enter the address for the email server from which system-generated email messages sent
to users of the platform should be sent.
SMTP Port—Enter the SMTP server port number to be used.
SMTP Username—Enter the appropriate username for the SMTP server.
SMTP Password—Enter the appropriate password for the SMTP server.
Return Address—Enter the address that will appear as the “From” address on email messages sent to
users of the platform.
SSL Enabled—Check the box to use Secure Socket Layer (SSL) communication with the email server. (If
not checked, messages sent to the email server will be treated as all other clear network traffic.
Click Next to proceed.
If installing the Alarms Out to SMS component (selected in step 12), the Alarms Out SMS Settings page
will appear. (If not installing this component, skip to step 75.)
Installation Manual 4-13
Installing Software Components
Note:
The facility must have existing SMS messaging services from an appropriate provider in order to use the Alarms
Out to SMS functionality. Obtain settings information for entry in the Alarms Out SMS Settings page from facility
IT personnel.
Figure4-18.Informatics Installation Wizard—Alarms Out SMS Settings Page
69.
User Name—Enter the user name for the SMS gateway via which system-generated SMS messages sent
to users of the platform should be sent.
70.
Password—Enter the appropriate password for the SMS gateway.
71.
From phone number—Enter the phone number that will appear as the “from” number on the mobile
device of the user receiving the SMS message.
72.
Server URL—Enter the appropriate SMS gateway address.
73.
Server Relative Path—Enter the appropriate path to the SMS gateway.
74.
Click Next to proceed to the Installation Summary page.
If upgrading from a version of the software previous to v2.5.x, exit the installation wizard and uninstall the older
version before installing the current version.
77.
Installation
If desired, review the list of components to be installed, as well as database configuration details. When
ready to continue, click Next.
If upgrading from a previously installed version of the software, a dialog showing version information for
the older installation will appear.
If backups already exist for all database files used with the previous version of the software, click OK to
proceed to the Confirmation page. If not, click Cancel to exit the installation wizard. After creating
backup database files, reopen the installation wizard and repeat all previous steps in this procedure, then
click OK in the dialog when it appears again to proceed with installation.
If ready to install components, click Install. If not, click Back as needed to return to earlier screens in the
wizard, make any desired changes, then return to the Confirmation page and click Install.
79.
A progress window (along with a series of command windows) will appear showing installation progress. Once the installation is complete, a dialog will appear asking whether or not to start the Data Collection Service.
Installation Manual 4-15
Installing Software Components
80.
If ready to start the Data Collection Service, click Yes. If not ready to start the Data Collection Service, click
No. (It is recommended to click No and manually start the service later once all software installation is
complete).
81.
A progress window (along with a series of command windows) will appear showing installation progress. Once the installation is complete, a dialog will appear asking whether or not to start the Data Collection Service.
Figure4-22.Informatics Installation Wizard—Data Collection Service Start Dialog
Restart the system before continuing with the remaining configuration procedures detailed in this
manual.
Note:
If installing components on multiple systems, repeat appropriate steps of the installation procedure in this
chapter for each component or set of components, until all required components have been successfully
installed on the appropriate systems.
4-16 Installation Manual
5Additional Configuration
5.1 Overview
This chapter provides information on final configuration steps before using the Vital Sync™ virtual
patient monitoring platform and informatics manager software.
Note:
To install and configure software, administrative rights are required on destination systems.
Note:
The procedures shown in this chapter assume that Microsoft™* SQL Server™* 2016 is installed. If Microsoft™*
SQL Server™* 2012 is installed, the procedures do not significantly differ. If encountering problems during or
after configuration, consult with Medtronic Professional Services.
Note:
Setup and configuration procedures in this chapter are to support the Vital Sync™ virtual patient monitoring
platform and informatics manager software,
5.2 Database Agent Startup
Once the database server software and the software components are installed and configured,
the database server is ready for replication.
To fully enable replication, start the SQL Server and Snapshot agents.
Note:
While performing the procedures in this chapter, have the name of the SQL database server installed for use
with the Vital Sync™ software readily available, to ensure the correct server is chosen.
5.2.1 SQL Server Agent
To start the SQL Server database agent:
1.
In the Microsoft™* SQL Server™* Management Studio Object Explorer, find the SQL database server
installed for use with the Vital Sync™ software.
5-1
Additional Configuration
2.
Click the plus sign next to the Replication folder to expand the directory.
3.
Click the plus sign next to the Local Publications folder to expand the directory. A publication named
[Informatics]: InformaticsReplication should be present.
Figure5-1.Microsoft™* SQL Server™* Management Studio (Informatics Replication publication shown)
4.
Right-click on the SQL Server Agent icon to open a context menu.
Figure5-2.Microsoft™* SQL Server™* Management Studio—SQL Server Agent Start
5.
Select Start.
6.
Click Yes to confirm startup of the SQL Server Agent. (Click No to abort startup.)
7.
A progress bar shows the level of completion of the startup process. If startup is successful, click Close.
5-2 Installation Manual
8.
Click the plus sign next to the SQL Server Agent icon.
Figure5-3.Microsoft™* SQL Server™* Management Studio (Job Activity Monitor icon present)
Database Agent Startup
9.
Confirm that an icon for the Job Activity Monitor is present.
Note:
Once the SQL Server Agent is running, do not stop it at any time. Stopping the SQL Server Agent prevents
database replication in the Vital Sync™ software.
5.2.2 Snapshot Agent
To start the Snapshot Agent:
1.
In the Microsoft™* SQL Server™* Management Studio Object Explorer, find the SQL database server
installed for use with the Vital Sync™ software.
2.
Right-click on the Replication icon to open a context menu.
Confirm that Running appears in the Status field for the Snapshot Agent.
Note:
Check the status of the Snapshot Agent at any time by opening the Replication Monitor and selecting Snapshot
Agent from the Agent Type drop-down box on the Agents tab.
Installation Manual 5-5
Additional Configuration
Note:
Once the Snapshot Agent is running, do not stop it at any time. Stopping the Snapshot agent prevents database
replication in the Vital Sync™ software.
5.3 Firewall Configuration
After installing components and supporting software and configuring database agent operations
and remote connection, ensure that the correct firewall ports are open to enable communications
with the wireless network and with devices to be monitored, as indicated. Also ensure correct serialto-Wi-Fi converter and device settings, to allow the software to connect and automatically reconnect as needed during normal operations.
WARNING:
Ensure that devices connected to the serial-to-Wi-Fi converter use the correct ports, so that the devices
will be available in the device inventory when connected. Please contact Medtronic Professional
Services for assistance if necessary.
See Table 5-1 for a list of ports to be opened, and on which system or systems.
Table5-1.Firewall Ports To Be Opened
PortSystem
3001System with Informatics Web and Data Collection Service installed
3002System with Informatics Web and Data Collection Service installed
3010System with Informatics Web and Data Collection Service installed
3020System with Informatics Web and Data Collection Service installed
3021System with Informatics Web and Data Collection Service installed
3050System with Informatics Web and Data Collection Service installed
4001System with Informatics Web and Data Collection Service installed
5100System with Informatics Web and Data Collection Service installed
5101System with Informatics Web and Data Collection Service installed
10001System with Informatics Web and Data Collection Service installed
80Internet Information Services (IIS) server
443IIS server (only required if SSL is enabled)
1433OLTP and Data Warehouse servers (only if using distributed deployment)
2382OLTP and Data Warehouse servers (only if using distributed deployment)
5-6 Installation Manual
Firewall Configuration
Specific Medtronic devices and protocols use certain ports to communicate with the software.
See Table 5-2.
The local port settings listed in Table 5-2, in conjunction with the IP address, enable the software to
automatically reconnect to each serial-to-Wi-Fi converter.
All devices using Ethernet or Wi-Fi require source and destination ports to establish identity and
location. Recommended source ports are listed in Table 5-3.
Table5-3.Recommended Source Ports for Device Communication
The source port settings listed in Table 5-3, in conjunction with the source IP address, enable the
software to automatically reconnect.
Note:
Medtronic recommends that each serial-to-Wi-Fi converter should be assigned a unique local port to connect
to the system on which the Data Collection Service is installed.
Medtronic also recommends that each logical connection should be assigned a unique local port to connect to
the system on which the Data Collection Service is installed, to maintain consistent status in the database.
Installation Manual 5-7
Additional Configuration
Note:
Since all Medtronic devices support multiple baud rates, ensure that the baud rate is the same on each device
as on the serial-to-Wi-Fi converter, so that the device will communicate properly.
Note:
The software is configurable to support connection with devices at different baud rates, or to allow use of
different firewall ports than those listed in this manual. Please contact Medtronic Professional Services for
assistance with POC network interface configuration.
5.4 Time Synchronization
If components are installed on multiple systems, ensure dates and times on all systems are synchronized, either via the network or by using a time server.
5.5 Distributed Deployment
For environments where there will be many users, monitored patients and/or monitored devices, a
distributed deployment of Vital Sync™ software components and supporting software can be performed to improve efficiency and performance. One such deployment configuration is detailed in
this section.
5.5.1 System Configuration
The distributed deployment described here uses four systems:
•The Online Transaction Processing (OLTP) system, also referred to as the OLTP database server, hosts the
application database and the Database component.
•The Data Warehouse system, also referred to as the Data Warehouse database server, hosts the Data
Warehouse database.
•The application system hosts the Data Collection Service, Reports, and Informatics Web components.
•The services system hosts the IPI Web Services connector component.
The OLTP database server supports primary clinician and supervisor platform functions, including
patient/device summary and detail displays, device/patient associations, and patient and area
assignment.
The Data Warehouse database server, meanwhile, supports the software’s reporting functions, and
also serves as a backup to the OLTP database server.
Reporting functions can be resource-intensive, particularly when a very large data set needs to be
generated for a particular report. Distributed deployment allows simultaneous reporting tasks and
clinical and supervisory tasks without an adverse effect on performance, as the different tasks will
not directly compete for resources on the same system.
5-8 Installation Manual
Distributed Deployment
5.5.2 Setup Process
Once components are installed on the appropriate servers as described in Chapter 4, perform
subsequent distributed development setup as follows:
•Ensure that services installed on the services system are pointed to the application database on the OLTP
server. Refer to Enable Remote Connection, page 3-30.
•Ensure that replication is configured to point to the Data Warehouse server database from the OLTP
server database. Refer to Enable Remote Connection, page 3-30.
•To enable reporting functionality for multi-server installations that use a Data Warehouse server, config-
ure the Worldwide Web Publishing Service to point to the Data Warehouse server database.
•If interfacing with an external system using HL7 messages, configure the IPI HL7 Adapter to point to the
correct system.
5.5.3 Reporting Configuration
Certain multi-server installations of the Vital Sync™ software will require changes to the Worldwide
Web Publishing Service configuration to support reporting functionality.
Installation
The Worldwide Web Publishing Service is installed with Microsoft™* Windows™* Internet Information Services (IIS).
Configuration
The Vital Sync™ software installer automatically configures the connection string for the Worldwide
Web Publishing Service during installation. This string denotes the database to which the service
should initially connect to correctly enable reporting functionality.
If installing the Vital Sync™ remote monitoring system software, no further configuration is necessary.
If installing the Vital Sync™ virtual patient monitoring platform and informatics manager software
on multiple servers including a Data Warehouse system, follow the procedure in this section.
Note:
Making changes to configuration files may adversely affect service or adapter performance. Do not make
changes other than those described in this section. Always use caution when changing configuration files.
Note:
Always make a backup copy of the configuration file before making any changes to the file.
Installation Manual 5-9
Additional Configuration
To change the connection string parameter setting:
1.
Navigate to the directory with the configuration file (typically, C:\inetpub\wwwroot\VitalSyncReportServer\Config).
2.
Open ConnectionStrings.config.
3.
Find the <ReportData> section of the file.
4.
On the connectionString line, change the Initial Catalog setting to InformaticsDataWarehouse.
5.
Save and close the configuration file.
6.
Stop the Worldwide Web Publishing Service.
7.
Restart the service to implement the new setting.
5.5.4 Subscription Configuration
After configuring report services to point to the Data Warehouse report server, set up a subscription
to replace the local subscription, so that replication will also point to the Data Warehouse server.
The wizard accessed during the subscription setup process shows a series of screens for selection
of options. If needing to change a selection already made, click Back to go back to the previous
screen and make the change.
In any screen, if needed, click Cancel to stop configuration and exit the wizard.
To configure replication to point to the Data Warehouse report server:
1.
In the Microsoft™* SQL Server™* Management Studio Object Explorer on the application system, find the
SQL database server instance installed to support the Vital Sync™ software.
2.
Click the plus sign next to the Replication folder to expand the directory.
3.
Click the plus sign next to the Local Publications folder to expand the directory. A publication named
[Informatics]: InformaticsReplication should be present.
4.
Right-click on [Informatics]: InformaticsReplication to open a context menu, then select New Subscriptions... to open the New Subscription wizard.
Click the check box next to the desired subscriber. A drop-down menu will appear in the Subscription
Database column for the subscriber selected.
9.
Click on the subscription database drop-down menu to open it, then select InformaticsDataWarehouse.
10.
Click on the Add Subscriber drop-down menu to open it, then select Add SQL Server Subscriber... to
open a connection dialog for adding the Data Warehouse report server database.
5-12 Installation Manual
Distributed Deployment
Figure5-12.Connection Dialog (for Data Warehouse server)
11.
Enter server information (server name, authentication type, username, and password) for the Data Warehouse report server.
12.
Click Connect to connect to the Data Warehouse report server.
13.
Click Next to proceed to the Distribution Agent Security screen.
Click the Run under the following Windows account radio button.
16.
Enter the login name and password of an appropriate administrative user on the system on which the
Informatics Web component is installed.
17.
In the Connect to the Subscriber fields, click the Using the following SQL Server login radio button,
then enter the SQL server user login name and password on the Data Warehouse report server. (Typically,
the account used is the system administrator account set up during database server installation on the
Data Warehouse server. Refer to Install the Database Server, step 22.)
18.
Click OK to return to the Distribution Agent Security page, then click Next to proceed to the Synchronization Schedule page.
Ensure the Agent Schedule field for the Data Warehouse report server shows Run continuously, then
click Next to proceed to the Initialize Subscriptions page.
The confirmation page shows details of the new subscription. Review the list if desired, then click Finish
to create the subscription.
23.
The wizard will indicate the level of completion of the operation on the finish page, indicating success
or failure of each step.
5-16 Installation Manual
Distributed Deployment
Figure5-19.New Subscription Wizard—Finish Page
24.
After reviewing information, click Close to exit the wizard. (If problems occurred, resolve them, then
repeat all previous steps in this procedure until creation is successful.)
25.
In the SQL Server Management Studio Object Explorer, the new subscription will appear under [Informatics]: InformaticsReplication, with the name of the Data Warehouse report server listed in brackets.
Figure5-20.Microsoft™* SQL Server™* Management Studio Object Explorer (Data Warehouse report server shown)
26.
Right-click on the local server subscription (i.e., the subscription that does not have the name of the Data
Warehouse report server) shown under [Informatics]: Informatics Replication to open a context
menu, then select Delete.
27.
A dialog box will appear for confirmation of deletion. Click Yes to delete the local subscription, or click
No to cancel and return to the Object Explorer.
28.
Right-click on the Data Warehouse server subscription to open a context menu, then select Launch Replication Monitor.
Installation Manual 5-17
Additional Configuration
29.
In the right pane, click on the Agent tab.
30.
Ensure Snapshot Agent is shown in the Agent types drop-down box.
Confirm that “Completed” shows in the Status field, then right-click on it to open a context menu, and
select Start Agent to start the Snapshot Agent running.
Note:
If the Snapshot Agent does not start properly, or an error message appears, check the credentials of the user
entered in step 16 of this procedure to ensure privileges are sufficient to run reports on the Data Warehouse
report server.
5.5.5 IPI Adapter Services Configuration
If the Vital Sync™ software is to be set up to send data to an external system (such as an Electronic
Medical Record system), changes may be necessary to the default configuration for IPI adapter services to allow proper communication between the software and the external system. Reference
Chapter 6 for details.
5-18 Installation Manual
6Connectivity to External Systems
6.1 Overview
This chapter provides information on additional installation and configuration steps to allow the
Vital Sync™ virtual patient monitoring platform and informatics manager software to interface
with certain external systems.
Note:
To install and configure software, administrative rights are required on destination systems.
Note:
Software performance and system health should be consistently monitored to allow timely detection and
resolution of problems, especially with communication of alarm messages.
A real-time listing of application events, as well as system performance reports, are available in the Vital Sync™
software. Refer to the reference manual for details.
6.2 Vital Sync HL7 Reporter Service
Users of external systems that accept HL7 messages, such as Electronic Medical Record (EMR) systems, can access device and patient data gathered by the Vital Sync™ Virtual Patient Monitoring
Platform and Informatics Manager via the Vital Sync HL7 Reporter Service. Once the service is
installed and configured, the external system can receive platform data via TCP/IP.
Note:
Users of the Vital Sync™ virtual patient monitoring platform and informatics manager software do not confirm
HL7 data sent to external systems. Clinicians will acknowledge and confirm HL7 data received into the EMR or
other external system using the appropriate software on that system.
To obtain additional information regarding support for HL7 standards, consult with Medtronic
Professional Services or with a local Medtronic representative.
Note:
The Vital Sync™ virtual patient monitoring platform and informatics manager software also supports use of a
solicited interface. For more information about how to configure the Vital Sync HL7 Reporter Service to work
with a solicited interface, consult with Medtronic Professional Services.
6-1
Connectivity to External Systems
6.2.1 Installation
The Vital Sync HL7 Reporter Service is installed with the Vital Sync HL7 Reporter Adapter component
of the Vital Sync™ software.
The service is located in the same directory with all other IPI services, and is registered on the system
as a Microsoft™* Windows™* service. In the Services Management Console, the service appears as
Vital Sync HL7 Reporter Service.
Files specific to the service are located in the AdapterPlugins subdirectory of the system’s Config
directory.
6.2.2 Additional Configuration
The Vital Sync™ software installer automatically configures the service during installation. In most
cases, the default settings require no modification.
However, depending on facility needs, changes may be necessary to configuration settings for data
output, or for connectivity to the external system or to Vital Sync™ software components.
Note:
Making changes to configuration files may adversely affect service or adapter performance. Do not make
changes other than those described in this section. Always use caution when changing configuration files.
Note:
Always make a backup copy of the configuration file before making any changes to the file.
Data-Related Settings
The scheduleInterval setting in the TimerTrigger section specifies how frequently the service
sends HL7 messages. This may require adjustment to accurately account for network or system
latency.
To change the schedule interval setting:
1.
2.
3.
4.
Navigate to the directory with the configuration file (for example, C:\Program Files\Covidien\
Informatics).
Open VitalSync.HL7ReporterService.exe.config.
Find the <TimerTrigger> section in the file.
Change the scheduleInterval setting as appropriate to facility needs. The value is specified in milliseconds. The default setting is 60000.
5.
Save and close the configuration file.
6.
Stop the Vital Sync HL7 Reporter Service.
7.
Restart the service to implement the new setting.
6-2 Installation Manual
Note:
Typically, the service will send HL7 data at approximately the frequency indicated by the scheduleInterval
setting. However, latency due to system processing or in communication between systems may cause delay. If
such a delay routinely occurs, adjust the schedule interval parameter appropriately to optimize performance.
External Connectivity-Related Settings
Multiple HL7OutputPluginWithLogging settings specify how the Vital Sync HL7 Reporter Service
connects to the external system that will receive HL7 messages. These settings may require adjustment to account for the facility’s network configuration.
•The server setting identifies the external system to which the service will attempt to connect.
•The portNumber setting specifies the TCP port to which the service will attempt to connect.
•The numberOfRetries setting specifies the number of times the service will try again to connect with
•The waitBetweenRetries setting specifies how long the service will wait after a failed connection
Vital Sync HL7 Reporter Service
the external system after failing in its initial attempt.
attempt before its next attempt to connect with the external system.
To change external connectivity settings:
1.
Navigate to the directory with the configuration file (for example, C:\Program Files\Covidien\
Informatics).
2.
Open VitalSync.HL7ReporterService.exe.config.
3.
Find the <HL7OutputPluginWithLogging> section of the file.
4.
If needed, change the server value setting to either the name or the IP address of the external system
which will be receiving HL7 messages.
5.
If needed, change the portNumber value setting to the TCP port number to which the adapter service
will attempt to connect.
6.
If needed, change the numberOfConnectRetries setting to a different value. The default setting is 5,
indicating that the adapter will make five additional connection attempts after an initial failure before
abandoning the sending of that specific HL7 message.
7.
If needed, change the waitBetweenConnectRetries setting to a different value. The default setting is
1000, indicating that the adapter will wait 1000 milliseconds before making its next connection attempt
after an initial connection failure.
8.
Save and close the configuration file.
9.
Stop the Vital Sync HL7 Reporter Service.
10.
Restart the service to implement the new settings.
Installation Manual 6-3
Connectivity to External Systems
Vital Sync ADT In Adapter Service
6.3
Users of ADT systems that send HL7 messages can send patient data to the Vital Sync™ virtual
patient monitoring platform and informatics manager software via the Vital Sync ADT In Adapter
Service. Once the service is installed and configured, the external system can send platform data via
TCP/IP.
To obtain additional information regarding support for HL7 standards, consult with Medtronic Professional Services or with a local Medtronic representative.
6.3.1 Installation
The Vital Sync ADT In Adapter Service is installed with the Vital Sync ADT In Adapter component of
the Vital Sync™ software.
The service is located in the same directory with all other IPI services, and is registered on the system
as a Microsoft™* Windows™* service. In the Services Management Console, the service appears as
Vital Sync ADT In Adapter.
Files specific to the adapter service are located in the AdapterPlugins subdirectory of the system’s
Config directory.
6.3.2 Additional Configuration
The Vital Sync™ software installer automatically configures the service during installation. In most
cases, the default settings require no modification.
However, depending on facility needs, changes may be necessary to configuration settings for data
input, or for connectivity to the external system or to Vital Sync™ software components.
Note:
Making changes to configuration files may adversely affect service or adapter performance. Do not make
changes other than those described in this section. Always use caution when changing configuration files.
Note:
Always make a backup copy of the configuration file before making any changes to the file.
Connectivity-Related Settings
The Port setting in the TcpIpInputTrigger section specifies the TCP/IP port on which the adapter
service will listen for connections from the external system.
To specify a port on which to listen:
1.
Navigate to the directory with the configuration file (for example, C:\Program Files\Covidien\
Informatics).
2.
Open VitalSync.ADTin.AdapterService.exe.config.
6-4 Installation Manual
Vital Sync Alarm Reporter Service
3.
Find the <TcpIpInputTrigger> section of the file.
4.
Change the Port value setting to the port on which the ADT In Adapter should listen for connections.
5.
Save and close the configuration file.
6.
Stop the Vital Sync ADT In Adapter Service.
7.
Restart the service to implement the new settings.
The RemoteIpValidation setting in the TcpIpInputTrigger section specifies whether the ADT
system should accept connections only from a particular remote IP address.
To enable remote IP validation:
1.
Navigate to the directory with the configuration file (for example, C:\Program Files\Covidien\
Informatics).
2.
Open VitalSync.ADTin.AdapterService.exe.config.
3.
Find the <TcpIpInputTrigger> section of the file.
4.
Change the RemoteIpValidation setting to true.
5.
Change the RemoteIp setting to the remote IP sending ADT messages.
6.
Save and close the configuration file.
7.
Stop the Vital Sync ADT In Adapter Service.
8.
Restart the service to implement the new settings.
6.4 Vital Sync Alarm Reporter Service
Users of external systems that accept alarm messages in IHE PCD-04 format, such as alarm management systems, can receive alarm data gathered by the Vital Sync™ virtual patient monitoring platform and informatics manager software via the Vital Sync Alarm Reporter Service.
To obtain additional information regarding support for IHE and HL7 standards, consult with
Medtronic Professional Services or with a local Medtronic representative.
Note:
Facility IS personnel should consistently monitor the system’s “dead letter queue” for the presence of any unsent
alarm messages. If any messages are present in the queue, investigate and resolve any issues preventing
messages from being sent.
Installation Manual 6-5
Connectivity to External Systems
6.4.1 Installation
The Vital Sync Alarm Reporter Service is installed as a component of the Vital Sync™ software.
The service is located in the same directory with all other IPI services, and is registered on the system
as a Microsoft™* Windows™* service. In the Services Management Console, the service appears as
Vital Sync Alarm Reporter Service.
Files specific to the service are located in the AdapterPlugins subdirectory of the system’s Config
directory.
6.4.2 Dependencies
The service has dependencies on three other system components: Microsoft™* Message Queuing;
the Data Collection Service component of the Vital Sync™ software; and the Applet Manager Service
component of the Vital Sync™ software.
Message queuing and the Data Collection Service should already be installed, and the Applet
Manager should also already be installed if platform-related applications or derived parameter algorithms are being used. Refer to Install Message Queuing, page 3-9, and Component Installation, page
4-2.
6.4.3 MSMQ Queue Configuration
The Data Collection Service component sends alarm events to a specific message queue. The Vital
Sync Alarm Reporter Service retrieves events from the same queue, transforms the events as appropriate for the external system accessing them, and then forwards the event data to the external
system.
To enable MSMQ functionality for alarm events:
1.
Create a queue for alarm events. Reference the Microsoft™* technical document Administering Queues,
available online at the following URL:
The preferred name for the queue is ipiCoreEvents, the default name used by the Vital Sync™ Virtual Patient
Monitoring Platform and Informatics Manager.
2.
Set security permissions so that the Vital Sync Alarm Reporter Service, Data Collection Service, and Applet
Manager Service (if used) can access the queue. The permission settings required will depend on the
accounts under which services are run, and whether the queue resides on a different machine than the
machine on which the Vital Sync Alarm Reporter Service, the Data Collection Service, or the Applet
Manager service (if used) run. Reference the Microsoft™* technical document Set Permissions for Comput-er and Queue Objects, available online at the following URL: