GE Healthcare MUSE v8 - Manual (Page 3)

MUSE System Requirements
Networking requirements
To ensure proper MUSE system operation on a network,
some form of NetBIOS name resolution such as WINS, DNS
or LMHOSTS must be used. All routers, switches, WANs, LANs,
and other networking infrastructure must support Microsoft
TCP/IP. Network “health” and response times can affect the
MUSE system performance. The amount of time required to
display the Edit List or a particular test will depend on the
number of tests on the Edit List, the speed of the network,
and, in the case of a particular test, the size of that test.
File Server: Requires a static IP address
Clients: Either static or DHCP assigned IP addresses
can be supported.
Physical layer
All network cabling must conform to the pertinent
IEEE 802.X standard, and the customer must test it prior
to system installation.
Connectivity
Each MUSE client must be able to connect to the MUSE file
server over the network. See the pre-installation manual for
more information about the required network ports.
Utilization
For optimum MUSE System performance, Ethernet band-
width utilization, on average without the MUSE system run-
ning must be less than 18% of the available bandwidth for
each MUSE system node’s network segment. Total Ethernet
bandwidth utilization on average must be less than 30% and
the maximum peak utilization level must be less than 55%.
The broadcast levels on any segment that a MUSE system
node is connected to may not exceed 10%.
Reliability
The overall error rate of a network segment
must be less than 2% of the available bandwidth.
When integrating the MUSE System at a customer facility,
additional integration charges may apply when either
of the following conditions occur:
• The MUSE system network is not on a standalone Local
Area Network (LAN)
• The MUSE system standalone LAN will be used to sup-
port any products, devices, or information other than GE
Healthcare supported products specifically sold under this
agreement.
Network printing requirements
The MUSE file server can be the print server or can send
to a print server. UNC (Universal Naming Convention) paths
are used to configure the destination for laser printing from
within the MUSE application. The MUSE system does not
print directly to Windows-defined printers.
The following three general options exist for MUSE
network printing:
1. A printer connected directly to the network and then
shared (or made for use) by a server. The server reduces
collisions from multiple transmissions to this printer.
It also provides queuing and possibly a retry mechanism.
2. A printer connected to an LPT port on a computer
and then shared by that computer.
3. A printer connected to an LPT port on a computer, but
not shared. This facilitates printing to MUSE EveryWARE
clients and would be the intended use of setting up
a printer this way.
NOTE: The first option is the preferred configuration for
network printing for the MUSE system. It is recommended
when generating Postscript Level 2 reports from a MUSE
system to have Postscript software from Adobe
® and a
laser printer with 14 MB RAM or more.
Warranty
Standard warranty is one year for hardware.
Standard warranty is 90 days for software.
Ordering information
Visit gehealthcare.com or contact your local
GE Healthcare representative.
Guidelines for VMware
Please refer to the 2034539-044 MUSE Cardiology Information
System Pre-Installation Manual for specific implementation-
related guidelines under the VM environment.
Microsoft Service Packs
The service packs for Windows Server and SQL 2005 as
referenced in this document were the latest service packs
available at the time of publication. Later Service Packs
released by Microsoft may not always be documented in
this manual, in this case refer to the GE Healthcare Product
Security Web Site, http://prodsecdb.gehealthcare.com, or
contact MUSE Technical Support to determine if later Service
Packs have been qualified for use with the MUSE system or
the HL7 Interface server.