beautypg.com

Other requirements, Networked concerns – Welch Allyn Acuity Software Upgrade CD - Installation Guide User Manual

Page 6

background image

2

Prerequisites for the Upgrade

Welch Allyn

Other Requirements

To minimize the impact of upgrading your System, please plan ahead. Make sure all of the
following have occurred prior to beginning.

Arrange for 20 minutes of time for each individual System to not be monitoring
patients. (This is more than enough time for a successful patch. If problems occur it
could take longer)

Have these instructions

(part number 810-2878-00)

and the proper Software Upgrade

CDROM.

Upgrade CDROM for Standard and Networked Acuity Systems

(part number 810-2861-00)

.

Upgrade CDROM for Acuity LT, Mobile Acuity LT and RadNet Systems

(part number 810-2862-00)

Know the Acuadmin password for each System to be updated.

Know the root password for each System to be updated.

Have the telephone numbers for Welch Allyn Technical Support handy. Refer to

“Contact Welch Allyn”

on page 17 for additional information.

Have a way to take notes.

Networked Concerns

If the System you are planning to upgrade is part of a network of more than one system,
some additional planning measures need to be taken.

All systems on the network must be upgraded, so that all systems are at the same
software version upon completion.

While it is allowable to run two different software versions on the network during the
upgrade, it is not recommended to leave the network in this state for more than a 24
hour period. Work quickly to minimize clinical work-flow disruptions.

System behavior for accessing patients monitored by other CPUs on the network may
change when their software versions are different.

Typically, the temporary behavior changes in a way that control on the system
with the lesser software version will display one less level of control.

For example, a system configured to act as an Auto Open Secondary (AOS) may
act as a Patient List Remote (PLR) system with very limited controls.

Additionally the ability to ID or confirm patients on the network may be affected.

Normal system behavior is restored when all system on the network are at the
same software version.

While an High Availability (HA) system or back-up CPU will minimize the impact of
loss of patient monitoring across a reboot, access to all full disclosure data may not
be available when one CPU is down or when the software versions are different
between the two CPUs.

Note

Most Systems will meet all these requirements. If your system does not meet
these requirements, you will be notified during the installation process.