Virtual Patient Monitoring Platform and Informatics Manager
Reference Manual
U.S. patents: www.medtronic.com/patents
Medtronic and Medtronic logo are trademarks of Medtronic. ™* brands are trademarks of their respective owner.
Other brands are trademarks of a Medtronic company.
Symbols
Federal (U.S.A.) law restricts the use of the application to sale by or on the order of a physician.
This manual provides instructions for the Vital Sync™ virtual patient monitoring platform
and informatics manager software. It includes functionality descriptions for users acting in
a clinical, supervisory, or link management role, as well as for system and clinical
administrators.
1.2. Conventions
Text and terminology conventions used in this manual include the following:
■
Warnings alert users to potential serious outcomes (death, injury, or adverse events) to
the patient, user, or environment.
■
Cautions alert users to exercise appropriate care for safe and effective use of the
product.
■
Notes provide additional guidelines or information.
■
“Clinician” generally refers to nurses, physicians, respiratory care professionals, and
other caregivers.
■
“Platform” and “platform component” generally refer to functional areas of the
software accessible to users acting as clinicians, supervisors, and link managers.
■
“Software” generally refers to functional areas accessible to users acting as
administrators and clinical administrators, and also to the product as a whole.
1
■
Button names, menu options, field names, and report field names appear in boldface
text.
■
“Click” refers to the action activating buttons and menus in the software user interface.
If using a touchscreen monitor or mobile device, substitute “touch” for “click” where it
appears in the text.
■
“Drag and drop” refers to clicking on or touching a user interface element, moving it
over another user interface element, then letting go of the mouse button or breaking
contact with the touchscreen.
■
Unless otherwise specified, “device” refers to patient devices (for example, pulse
oximeters, ventilators, or capnography monitors), not to mobile devices (for example,
tablets or smartphones) or to optional dedicated bedside display units used to access
and perform functions in the software.
■
“Priority” and “severity” are used interchangeably to refer to events.
■
“Event” refers both to alarms and notifications from devices and algorithms.
Note: The terms “clinician”, “supervisor”, “administrator”, “clinical administrator”, “link
manager”, and “external services user”, as used in this manual, refer only to types of users
and to roles fulfilled when using the software. These terms do not necessarily correspond
to similar titles used for employees of any particular facility, nor to functions those
employees perform at that facility.
Reference Manual English 9
Note: Names of persons and facilities used as examples in this document are fictitious, and
are intended for illustrative and instructional purposes only. Any similarity to actual names
of persons or facilities is coincidental.
1.3. Applicable Version
This manual applies to version 2.8 of the Vital Sync™ virtual patient monitoring platform
and informatics manager.
Users can view specific version information for their installation by accessing the Version
Information (“About”) dialog in the software.
1.4. Safety Information
This section contains generally applicable safety information for this product.
1.4.1. 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.
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.
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 itself. 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 lifesustaining.
10 Reference Manual English
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.
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 user-designed derived parameter algorithms.
1
1.4.2. 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 software 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.3. Notes
Note: Before use, carefully review appropriate sections of this manual and the operator’s
manual for each connected device, applicable accessory instructions for use, and all
precautionary information and specifications.
Note: The platform’s data and audible alerts (including those appearing on optional
dedicated bedside display units) are informational. Except as specified for derived
parameter algorithms with adjustable alarm thresholds, the platform does not provide the
ability to change device settings or control linked devices in any way (including adjusting
or silencing device alarms).
Note: Before acting on information shown in the platform, assess the patient at the
bedside.
Note: Patients monitored via optional dedicated bedside display units should also be
monitored at a central monitoring station, as the dedicated bedside display unit is not
intended to be a primary source of alarms.
Reference Manual English 11
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.5. Obtaining Technical Assistance
1.5.1. Technical Services
For technical information and assistance if unable to correct a problem while using the
platform or platform-related applications, 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@Medtronic.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.5.2. Related Documents
Before using the software, carefully review appropriate sections of both this manual and
the operator’s manual for any connected device. This information is essential for
understanding the software’s functions and information displays.
Also read all precautionary information and specifications, both for the platform (and any
platform-related applications installed) and for any connected device.
1.6. Warranty Information
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.7. Licensing Information
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 the platform installation manual.
Users must obtain their own licenses for the downloading and use of such third party
software.
12 Reference Manual English
1.8. HIPAA Disclaimer
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.
1
Reference Manual English 13
14 Reference Manual English
2. Product Overview
2.1. Overview
This chapter provides an overall description of the functionality of the Vital Sync™ virtual
patient monitoring platform and informatics manager software.
2.2. Intended Use
The Vital Sync™ Informatics Manager is software that is intended to route and store medical
device data and device diagnostic information from supported devices to the Virtual
Patient Monitoring Platform, 3rd Party Annunciation Systems, Electronic Medical Record
(eMR) and Clinical Information System (CIS).
The Vital Sync™ Virtual Patient Monitoring Platform (VPMP) is a display system that
provides visual and audible renderings of physiologic data, waveforms and alarms routed
through the Vital Sync™ Informatics Manager from supported devices.
The Vital Sync™ Virtual Patient Monitoring Platform is intended to be used by healthcare
professionals in a hospital or hospital-type facility for the following purposes:
■
To remotely view and review patient data, waveforms, alerts, and alarm information
from supported devices and clinical information systems to facilitate clinical
management.
2
■
To facilitate remote collaboration with other healthcare professionals regarding patient
data from supported devices.
■
To access additional processed parameters to facilitate patient monitoring, assessment
and clinical management.
■
To set and adjust thresholds on supported devices where this capability is not available
on the device itself.
■
To access data, waveforms and alerts from supported devices where these capabilities
are not enabled or available on the device itself.
Warning: The Vital Sync™ Informatics Manager and Virtual Patient Monitoring Platform are
notification systems and are not replacements for direct patient observation, patient
assessment, or clinical judgment.
2.3. User Interface Overview
The Vital Sync™ virtual patient monitoring platform is designed to allow nurses, physicians,
respiratory care professionals and other caregivers (referred to in this manual as
“clinicians”), as well as users acting in a supervisory role, to access data from connected
devices via a computer terminal, mobile device, or optional dedicated bedside display unit.
The Vital Sync™ informatics manager is designed to allow administrative users to access
and manage system records for users, devices, algorithms, locations, and shifts; perform
alarm rule and normalization functions; and view system events and performance.
Users view data and perform other program functions within a Web browser window on a
personal computer or mobile device.
Reference Manual English 15
2.3.1. Basic Functions
Users can view general information, including alarms and advisory messages, for multiple
medical devices. The platform supports a wide range of devices, and in some cases acts as
the primary device user interface.
In the general device view (called the Tile View), each bed and unassociated device is
represented by a tile. Clicking on a bed tile accesses detailed information for a specific bed
and devices linked to the patient in that bed. Clicking on a tile for an unassociated device,
or dragging it onto a bed tile, accesses functions for linking the device to a patient.
Users can also create, manage, and remove links between patients and devices, and
discharge patients within the platform if appropriate. They can also create and remove
patient and area assignments. Shift management features help streamline the process of
assigning patients and areas to individual clinicians and supervisors.
Device inventory, bed management, and area management functions allow users to
associate individual devices (including optional dedicated bedside display units) with
specific beds in the facility, and to define areas in the platform that correspond with
specific locations (also sometimes referred to as zones or areas of care) within the facility.
Areas are assignable to specific clinicians and supervisors just as patients are.
Alarm and event management functions allow users to set up rule sets to refine the timing
of alarm and notification annunciation in the platform, also known as alarm filtering; this
can assist in reducing the incidence of nuisance alarms. In addition, users can adjust alarm
priorities for devices in the platform, in order to normalize alarm priorities across a facility.
Single-tone or multi-tone audible alerts are available, allowing users to hear as well as see
alarm indications when using the platform. Audible alerts can be enabled or disabled for
any user. Any user who has audible alerts enabled can temporarily silence them as they
occur. The platform visually indicates silenced alerts, alarms paused or silenced on devices,
and filtered alarms.
Reporting functions allow access to both current and historical information about
monitored devices and patients, users and usage, and the functioning of the platform itself.
These can be used in conjunction with derived parameter algorithms (which can be linked
to patients in the same way as devices are) as an aid in monitoring and managing patient
conditions. They also allow system administrators to monitor performance and events
within the platform, and also on its associated hardware.
The platform supports the use of optional dedicated bedside display units, which allow
view-only access to patient and device data for a specific bed, and are especially intended
for devices that use the platform as their primary user interface. The platform also can be
used at a central monitoring station, via a non-user-specific account specifically designed
for this purpose.
Note: The platform’s data displays and audible alerts (including those appearing on
optional dedicated bedside display units) are informational. Except as specified for derived
parameter algorithms with adjustable alarm thresholds, the platform does not provide the
ability to change device settings or control linked devices in any way (including adjusting
or silencing device alarms).
Note: The current release of this software allows viewing of data from ventilators,
capnography monitors, pulse oximeters, regional saturation monitors, bispectral index
monitors, and multiparameter monitors. The software also shows information from derived
16 Reference Manual English
parameter algorithms. See Device Types Supported, page 23 for a list of specific device
types with which this software is usable.
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: 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.
2.3.2. User Roles
Each user is identified in the software by username and password, and enters these to log
into the software. Functions available depend on the user”s assigned role.
■
Clinicians—Users in this role may view device information for many patients and
devices at once in a tiled overview screen, clicking on any tile to access detailed
information. They may also link devices with patients in the platform, manage patient
identifying information and links between patients and devices, and manage their own
patient and area assignments. They will hear an alert tone (if enabled in the platform)
when a device linked to any of their patients enters an alarm state, and may also
receive email and text message alerts for alarms. Finally, clinicians may run “snapshot”
reports showing oxygenation or ventilation data for specific patients.
2
■
Supervisors—Users in this role are able to perform the same tasks in the platform as
clinicians can, complemented with additional functions to assist in their supervisory
role. These functions include a multi-device list view; the ability to manage patient and
area assignments for other users; and a virtual user function allowing a view of the
platform as the selected clinician would see it. A wide range of reporting functions is
also available, providing information on alarm and setting change information, system
utilization statistics, and other historical data.
■
Administrators—Users in this role perform various system administration functions.
They may set up, maintain and deactivate user records in the platform; reset passwords
and unlock locked-out users (if the deployment allows); and view event and system
performance logs and utilization reports. They also manage the inventory of connected
devices, and set up and maintain beds, areas, work shifts, and dedicated bedside
display unit assignments in the platform. Administrators manage rule sets governing
alarm and event annunciation, normalize alarm priorities in the platform (if needed),
and may set up algorithms and derived parameter algorithms in addition to those
already supported in the platform. They also may access system performance and
usage reports, as well as reports showing alarm rule setting and priority information.
■
Clinical Administrators—Users in this role access the platform as administrators do, but
are not tasked with direct management of users, locations, or devices. Instead, their
role is to manage alarm and event priorities, rules, and rule sets, as well as to manage
parameters and derived parameter algorithms.
■
Link Managers—Users in this role access the platform as clinicians and supervisors do,
but do not directly monitor patients. Instead, their role is to link devices to patients to
support reporting of device data to an electronic medical record (eMR) system. As such,
link manager functionality is limited to linking of devices and management of existing
Reference Manual English 17
links. Consult Medtronic Professional Services for more details, and for information on
enabling this role.
■
External Services—Users in this role manage and configure interfaces between the
platform and various external application services. Consult Medtronic Professional
Services for more details.
In addition to using the platform on a PC or mobile device, users may also access it via a
central monitoring station (which does not require individualized login credentials) or on
an optional dedicated bedside display unit, which runs a streamlined version of the
software and shows patient and device data for a single bed. Consult Medtronic
Professional Services for more details on setup for either or both of these options. (Platform
operations for central monitoring stations or bedside unit users are similar to those for
individual users, varying only in the scope of functions available.)
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.
Note: Patients monitored via dedicated bedside display units should also be monitored at a
central monitoring station, as the dedicated bedside display unit is not intended to be a
primary source of alarms.
Note: The terms “clinician”, “supervisor”, “administrator”, “clinical administrator”, “link
manager”, and “external services user,” as used in this manual, refer only to types of users
and to roles fulfilled when using the software. These terms do not necessarily correspond
to similar titles used for employees of any particular facility, nor to functions those
employees perform at that facility.
2.4. User Interface Symbols
The software makes use of icons and symbols to denote user functions and to show data
from patients and devices. These are defined in the tables in this section.
Note: Some symbols may appear in different colors in the software than are shown in the
tables (for example, device icons shown in dark colors on a light background here may, in
certain locations, appear in light colors on a dark background). Unless noted, symbols in
the tables have the same meaning even if appearing in a different color scheme than is
shown here.
Table 1. Device Symbol Definitions
IconDescriptionDefinition
VentilatorRepresents a ventilator linked to a patient in the platform, or available
for linking.
Appears in various locations in the platform.
Capnography monitorRepresents a capnography monitor linked to a patient in the platform,
or available for linking.
Appears in various locations.
Pulse oximeterRepresents a pulse oximeter linked to a patient in the platform, or
available for linking.
Appears in various locations.
18 Reference Manual English
Table 1. Device Symbol Definitions (continued)
IconDescriptionDefinition
Bispectral index (BIS) monitorRepresents a bispectral index monitor linked to a patient in the plat‐
form, or available for linking.
Appears in various locations.
Regional saturation monitorRepresents a regional saturation monitor linked to a patient in the
platform, or available for linking.
Appears in various locations in the platform.
Multiparameter monitorRepresents a multiparameter monitor linked to a patient in the plat‐
form, or available for linking.
Appears in various locations.
Derived parameter algorithm
(DPA)
Represents a derived parameter algorithm linked to a patient in the
platform, or available for linking.
Note: Certain algorithms may have their own specific symbols.
Appears in various locations.
Table 2. Alarm and Status Symbol Definitions
IconDescriptionDefinition
Alarms active for patientsAlarms are active for the indicated number of patients.
Note: This symbol does not indicate alarm priority.
Appears on the common navigation bar (alarm button).
No alarms activeNo alarms are active for the indicated number of patients.
Appears on the common navigation bar (alarm button).
2
Device with active alarmOne or more alarms is active on the device indicated by the icon.
(See Table 1 for device icons.)
Note: This symbol does not indicate alarm priority, but only indicates
that alarms are active on this device.
Appears in the All Patients and Devices screen.
Device with active alarm (priority
indicated)
Algorithm with active alarmThe patient is in an alarm condition, according to the derived parame‐
Algorithm with active alarm (prior‐
ity indicated)
One or more alarms is active on the device indicated by the icon.
(See Table 1 for device icons.)
The colored square indicates the priority of the highest-priority alarm
currently active on the device. (Alarm priority symbols are explained
elsewhere in this table.)
Appears on bed tiles in the Tile View, and in the Device Detail screen”s
patient header.
ter algorithm (DPA) indicated by the icon.
Note: This symbol does not indicate alarm priority, but only indicates
that alarms are active for this algorithm.
Note: If an algorithm has its own specific symbol, it will appear
instead, with the designator for an alarm or missing data at lower
right.
Appears on the All Patients and Devices screen.
The patient is in an alarm condition, according to the derived parame‐
ter algorithm indicated by the icon.
The colored square indicates the priority of the patient”s alarm state,
as defined in the algorithm. (Alarm priority symbols are explained
elsewhere in this table.)
Note: If an algorithm has its own specific symbol, it will appear
instead, with the designator for an alarm or missing data at lower
right.
Appears on bed tiles in the Tile View, and in the Device Detail screen”s
patient header.
Reference Manual English 19
Table 2. Alarm and Status Symbol Definitions (continued)
IconDescriptionDefinition
High priority alarmWhen shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—The
active event with the highest priority on the indicated device or for
the indicated algorithm is a high-priority alarm.
When shown in other locations—At least one high-priority alarm is
active on the indicated device, or the indicated parameter or algo‐
rithm is in a high-priority alarm condition.
Medium priority alarmWhen shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—The
active event with the highest priority on the indicated device or for
the indicated algorithm is a medium-priority alarm.
When shown in other locations—At least one high-priority alarm is
active on the indicated device, or the indicated parameter or algo‐
rithm is in a medium-priority alarm condition.
Low priority alarmWhen shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—The
active event with the highest priority on the indicated device or for
the indicated algorithm is a low-priority alarm.
When shown in other locations—At least one high-priority alarm is
active on the indicated device, or the indicated parameter or algo‐
rithm is in a low-priority alarm condition.
Standard notificationWhen shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—The
active event with the highest priority on the indicated device is a noti‐
fication. (Specifically, this means no alarms are active on any devices
or algorithms linked to this patient.)
When shown in other locations—At least one notification is active on
the indicated device or algorithm.
Unfavorable patient event notifi‐
cation
Favorable patient event notifica‐
tion
Filtered alarmAn alarm is active on the indicated device, but the delay interval
Device with filtered alarmOne or more alarms that have been filtered (that is, annunciation is
When shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—A
potentially unfavorable event has occurred for the patient linked to
the indicated algorithm. This requires attention from the user..
When shown in other locations—At least one unfavorable event noti‐
fication is active on the indicated algorithm.
When shown on the alarm button menu, the message bar on bed tiles
in the Tile View, or in the Device Detail screen’s patient header—A
favorable event has occurred for the patient linked to the indicated
algorithm (for example, completion of an activity related to an algo‐
rithm).
When shown in other locations—At least one favorable notification is
active on the indicated algorithm.
before visible and audible annunciation in the platform has not com‐
pletely elapsed.
Appears on bed tiles in the Tile View, in the All Patients and Devices
screen, and on the parameter tile associated with the alarm in the
Device Detail screen.
delayed or turned off) is active on the device indicated by the icon.
(See Table 1 for device icons.)
Note: This symbol does not indicate alarm priority, but only indicates
that filtered alarms are active on this device.
Appears on bed tiles in the Tile View, in the All Patients and Devices
screen, and (in a slightly different form) in the Device Detail screen’s
patient header.
20 Reference Manual English
Table 2. Alarm and Status Symbol Definitions (continued)
IconDescriptionDefinition
Audible alerts silenced in the plat‐
form
Audible alarms paused or silenced
on a device
Device with audible alarms
paused or silenced
Notifications active for patientsNotifications are active for the indicated number of patients.
No notifications activeNo notifications are active on any devices linked to this user’s patients.
Indicates that the platform’s audible alerts are currently silenced for
one or more devices linked to a patient.
Appears in the Tile View on the bed tile for the affected patient during
the alert silence period.
Indicates that the platform’s audible alerts are currently silenced for
the device currently shown in the Device Detail screen.
Appears in the Device Detail screen’s patient header (in the color
scheme shown) during the alert silence period.
Audible alarms have been paused or silenced at the bedside on a
device linked to one of this user”s patients.
Appears in various locations.
Indicates that audible alarms have been paused or silenced at the
bedside on the indicated device. (See Table 1 for device icons.)
Appears on bed tiles in the Tile View, in the All Patients and Devices
screen, and (in a slightly different form) in the Device Detail screen’s
patient header.
Appears on the common navigation bar (notification button).
Appears on the common navigation bar (notification button).
2
Setting change on deviceOne or more settings have been changed on a device linked to one of
this user’s patients.
Appears in various locations.
Device with active setting
changes
Reset alarm on deviceAn alarm on a device linked to one of this user’s patients has reset (i.e.,
Device with reset alarmsOne or more reset alarms has occurred on the device indicated by the
Algorithm with standard notifica‐
tion
Unassociated devices availableThe indicated number of devices are connected to the platform, but
One or more setting change notifications is active on the device indi‐
cated by the icon, and has not yet been acknowledged. (See Table 1
for device icons.)
Appears in bed tiles on the Tile View, and in the Device Detail screen’s
patient header.
an alarm condition temporarily existed, but has resolved itself without
intervention).
Appears in various locations.
icon. (See Table 1 for device icons.)
Appears on bed tiles in the Tile View, in the Device Detail screen’s
patient header, and in the All Patients and Devices screen.
An event has occurred for the patient linked to the algorithm indica‐
ted by the icon.
Note: If an algorithm has its own specific symbol, it will appear
instead, with the notification designator at lower right.
Appears on bed tiles in the Tile View, and in the Device Detail screen’s
patient header.
are not currently linked to any patient.
Appears in the common navigation bar (device button).
No unassociated devicesAll devices connected to the platform are currently linked to patients.
Appears in the common navigation bar (device button).
Reference Manual English 21
Table 2. Alarm and Status Symbol Definitions (continued)
IconDescriptionDefinition
DisconnectionA device is not currently communicating with the platform.
Appears in various locations. On the Device Detail screen for a discon‐
nected device, this symbol appears in a much larger form.
Device disconnectedThe device indicated by the icon is not communicating with the plat‐
form.
Appears on bed tiles on the Tile View, in the Device Detail screen’s
patient header, and on the All Patients and Devices screen.
Database connectedThe platform is currently communicating with its databases.
The squares cycle through various colors when a data request is in
process.
Appears on the common navigation bar, at far right.
Database disconnectedCommunication between the platform and its databases is currently
interrupted.
Appears on the common navigation bar, at far right.
Table 3. Miscellaneous User Interface Symbol Definitions
IconDescriptionDefinition
Silence audible alert in the plat‐
form
View patient and location infor‐
mation
Denotes the button used to silence alert tones for a specific patient in
the platform.
This function does not silence audible alarms on any linked device;
those must be silenced on the device itself at the bedside.
Appears on the Device Detail screen”s patient header when alarms
are present on the selected device.
Denotes a link to information about the current patient.
Appears in the patient header on the Device Detail screen.
Edit patient information or loca‐
tion information
ReportsDenotes a link to available report functions.
Link new deviceDenotes the button used to access the Admit Patient screen for pur‐
Home screenDenotes a link to the current user’s home screen.
Patient typeThe patient type (from left to right, indicates neonatal, pediatric, or
Freshness levelDenotes the level of confidence in the data used in calculation of cer‐
Denotes a link to a dialog for editing information about the current
patient or location.
Appears in the Device Detail screen (patient detail).
Appears in the patient header on the Device Detail screen.
poses of linking a new device to a patient.
Appears in the patient header on the Device Detail screen.
Appears in the common navigation bar (Home button).
adult, respectively).
The darkened icon indicates the patient type for the patient currently
linked to this device.
Appears in the device header on the Device Detail screen.
tain derived parameters.
Freshness levels shown are 100%, 75%, 50%, 25%, and 0%. The top
half of the icon ranges from completely black for the 100% level to
completely white for the 0% level. (The icon at left indicates a 50%
freshness level.)
Appears on the Device Detail screen for the algorithm.
22 Reference Manual English
Table 3. Miscellaneous User Interface Symbol Definitions (continued)
IconDescriptionDefinition
Mark for deletionDenotes the button used to mark alarm rules for deletion.
Appears in the Manage Alarm Rules screen next to each custom alarm
rule.
SearchDenotes the button used to search the platform databases for a
patient ID number.
Appears in the Link Patient and Device screen and the Update Patient
Information window.
Battery chargeFor supported devices, shows the current battery charge level (more
black boxes indicate a higher charge level).
Appears in the device header on the Device Detail screen.
2.5. Device Types Supported
Note: Medtronic has verified the communication protocols used with the device types
listed in this section.
For more information on communication protocols, see Device Data Reporting, page 169.
For a listing of relevant standards, see Relevant Standards, page 178.
The current release of the software supports the following device types:
■
Ventilators (including the Puritan Bennett™ 980 ventilator, Puritan Bennett™ 840
ventilator, and Newport™ HT70 ventilator)
■
Pulse oximeters (including the Nellcor™ OxiMax N-595, Nellcor™ OxiMax N-600x, and
Nellcor™ N-600x-A bedside pulse oximeters, the Nellcor™ OxiMax N-85 handheld pulse
oximeter, and the Nellcor™ bedside respiratory patient monitoring system)
■
Capnography monitoring devices (including the Oridion Capnostream™ 20 and Oridion
Capnostream™ 20P capnography monitors and the Capnostream™ 35 portable bedside
monitor)
Bispectral index monitors (including the BIS™ Vista monitoring system)
2
■
Multiparameter monitors (including the Welch Allyn™* Connex™* 6700 (model
67NCTX-B) and Welch Allyn™* Connex™* 6800 (model 68NCTX-B) vital signs monitors)
Also, derived parameter algorithms, if set up and used in the software, will appear in
various screens as if they are devices, and can be linked to patients in the same way as
devices of the other types listed in this section.
Note: This manual includes only a partial listing of supported device types, and examples of
devices supported. Individual facilities may also support additional devices not listed in this
manual. Contact Medtronic Professional Services for a complete list of devices currently
supported.
Note: The term “device type” is replaced in some screens and report output in the software
with the term “device category”. For purposes of this manual and the software user
interface, the terms are interchangeable.
Reference Manual English 23
24 Reference Manual English
3. Installation and Access
3.1. Overview
This chapter tells users where to find current software and hardware requirements for
installation of the Vital Sync™ virtual patient monitoring platform and informatics manager
software, and also provides details on how to access and log into the software.
3.2. System Requirements
To install and use the software, the systems in question must meet certain hardware and
operating system requirements, and must also in some cases have other supporting
software installed.
For minimum hardware and software requirements, as well as recommended
configurations for best results when using the platform, refer to the installation manual.
For the most current information regarding minimum requirements and recommended
configurations, as well as additional installation and configuration information and lists of
known and resolved issues, refer to the release notes. Consult with Medtronic Professional
Services for the most current applicable revision.
3.3. Installation
For detailed information on installing and configuring platform components and
supporting software, refer to the installation manual, as well as the release notes for this
release of the software.
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 manual or the installation manual. Users must
obtain their own licenses for the downloading and use of such third party software.
3.4. Access
To access the software:
1.Open the Web browser on the PC or mobile device.
2.Enter the software”s Uniform Resource Locator (URL) in one of these formats,
depending on facility IT setup and policy:
■
http://{server name or IP address}/InformaticsWeb
■
https://{server name or IP address}/InformaticsWeb
Note: Before first using the software, consult facility IT personnel to obtain the server name
or IP address needed for access, and to find out whether to use “http” or “https” in the URL.
3
Note: To maximize data security, Medtronic recommends an HTTPS connection to the Vital
Sync™ software.
Reference Manual English 25
3.5. Login
To log into the software:
1.Access the platform in a Web browser. See Access, page 25.
2.Make sure the login screen is shown.
Figure 1. Login Screen
3.Username—Enter the username.
4.Password—Enter the password associated with the username. (The password will
appear as a series of dots when entered.)
5.Click Login.
Upon login, the home screen appropriate to the user’s role will appear.
Note: If credentials are entered incorrectly, the login screen will show a system message
indicating incorrect entry. If this user is locked out, or if a network or system problem is
preventing system access, a system message will appear with a brief description of the
problem. Consult with an administrative user or with facility IT personnel for assistance.
Note: To protect password integrity when using a public or shared computer to access the
platform, ensure the Web browser does not “remember” login information.
Note: Screen captures in this manual are representative. Actual screens may vary slightly
from those shown here, depending on the specific software release used, how the user is
accessing and viewing the software, and specific facility requirements. Also, the size and
position of tiles and other screen elements will vary with the number of elements present
and the size of the browser window. Finally, the format in which dates appear may differ
depending on the localized software build used.
26 Reference Manual English
Loading...
+ 186 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.