 |
Click Here to View/Download PDF Version |
Last updated 27/07/09
CONTENTS
1) OPERATING SYSTEM SUPPORT
2) SQL SERVER SUPPORT
3) SPECIFICATIONS CLIENT PCs and PEER-TO-PEER NETWORKS
4) SPECIFICATION FOR SERVERs and LARGER NETWORK SYSTEMS
5) THIRD-PARTY INTEGRATION
If you would like assistance installing VIP.NET onto a system, please download the document: “VIP.NET SQL Installation Guide” from our website, which outlines the complete installation procedure on single user, peer-to-peer network, client/server and thin-client networks.
1) OPERATING SYSTEM SUPPORT
Houston VIP.NET Client application is is fully supported on the following operating systems:
Windows XP Professional
Windows Vista Business or Ultimate
Windows 7 Business or above
Windows Server 2003
Windows Server 2008
VIP.NET will work on both 32-bit and 64-bit operating systems.
The following operating systems are NOT supported:
Windows 95/98
Windows 2000
Windows XP Home
Windows Vista Home Basic
Windows Vista Home Premium
Mac OS / Server
Linux (even with WINE)
Macintosh PC’s with Intel hardware with “bootcamp” for Windows are supported.
Macintosh “parallels” with Windows is NOT a supported option.
2) SQL SERVER SUPPORT
VIP.NET SQL requires either:
· Microsoft SQL Server 2005 + SP2 or
· Microsoft SQL Server 2008 + SP1
NOTES
· SQL Server MUST be Standard Edition or higher and include FULL Reporting Services.
· Reporting Services requires IIS to be installed on the server.
· SQL Server requires Micosoft .NET Framework 3.5 to be installed.
· SQL Server can be installed on Windows XP, Windows Vista, Windows7, Windows Server 2003 and Windows Server 2008.
· SQL Server can be installed on 32-bit or 64-bit operating system
The SQL Server must be a dedicated server for larger installations.
In the case of a small peer-to-peer network it can be a non-dedicated machine with the VIP.NET application also installed.
Anything above 5-users need a dedicated SQL Server.
The following versions of Microsoft SQL Server are NOT supported.
· SQL Server 2005 Workgroup Edition (included with Small Business Server 2003) is not supported as it does not include reporting services.
· SQL Server 2005 Express is not supported as it does not include reporting services.
· SQL Server 2008 Express is not supported as it does not include reporting services.
· SQL Server MSDE is not supported.
· SQL Server 2000 is not supported.
· Linux and MAC Server systems are not able to run Microsoft SQL Server.
3) CLIENT PC and PEER-TO-PEER NETWORKS
Single Computer
A single PC system will also need to install and run Microsoft SQL Server 2005/2008 so will need the following minimum specifications:
FAST MODERN CPU
2 GB+ RAM
50+ GB FREE DISK SPACE
Microsoft SQL Server 2005/2008 with IIS, and Reporting Services
Microsoft .NET Framework 3.5
WINDOWS XP/VISTA/7/2003/2008 (support both 32-bit and 64-bit)
Small network – up to 5 workstations – non-dedicated server
For a small network up to 5 workstations, it is possible to have a non-dedicated server which can act as a workstation also. The non-dedicated server will have to run SQL Server 2005/2008 and will be delivering transactions to the workstations. Our recommended minimum specifications would be:
WORKSTATIONS
FAST MODERN CPU
1 GB+ RAM
50+ GB FREE DISK SPACE
Microsoft .NET Framework 3.5
ETHERNET NETWORK (Wifi is NOT supported)
WINDOWS XP/VISTA/7/2003/2008 (support both 32-bit and 64-bit)
SERVER
FAST MODERN CPU / MULTIPLE CORES / ADDITIONAL L2 CACHE
4 GB+ RAM
50+ GB FREE DISK SPACE
Microsoft SQL Server 2005/2008 with IIS, and Reporting Services
Microsoft .NET Framework 3.5
ETHERNET NETWORK (Wifi is NOT supported)
WINDOWS XP/VISTA/7/2003/2008 (support both 32-bit and 64-bit)
Wifi: please note that that because of the constant communication between the server and workstations, wifi or wireless is not support in the thick-client network model. This is due to “micro outages” which wifi networks constantly experience – any break in the network communication, no matter how small will cause errors on the client workstation.
If the requirement is for a wifi or wireless network, install a thin-client model network.
4) SERVERs and LARGER NETWORK MODELS
Any larger network should be designed and implemented by a suitably qualified network engineer. Networks have many requirements, including security, redundancy, access from within and without – there are many considerations which are outside the scope of this documentation. The requirements for VIP.NET are a guide for the VIP.NET application and do not consider what additional application and requirements are on individual workstations.
The important considerations with larger networks, and in particular server PC’s are:
· CPU power – how many cores, how much L2 cache, how many raw mhz rating?
· RAM – 32-bit OS maxmum ram is 4GB, 64-bit or Enterprise level software for 4gb+
· DISK TYPE and SPEED – serial-attached-scsi @ 15000rpm is better than 7200rpm Sata
There are two models for a larger network installation:
THICK CLIENT
Thick-client has the application installed on local PC’s which access the database across the network. In this instance, local processing power, network speed, and the ability of the server to deliver data back are all a consideration.
THIN CLIENT
Thin client is a terminal-server setup where PC’s log into a server. The only information travelling across the network is drawing of screen and keyboard and mouse commands.
For very large networks, it is advantageous to have a 2 SERVER SYSTEM:
1) Application server
1) Application server
2) SQL Server dedicated
In small-medium network it is not necessary to have a separate database and application server in fact in a multi-core/multiple access memory server they will be faster if they are together.
The server will need the .net framework 3.5 installed.
Reporting Services is installed during the initial installation of SQL Server, but configured after installation
Business Intelligence Studio should be installed as it can be used by advanced users to make reports.
Our basic guidelines for specifications are as follows:
CLIENT PC’s
(in a thick-client environment)
FAST MODERN CPU
1 GB+ RAM
50+ GB FREE DISK SPACE
Microsoft .NET Framework 3.5
ETHERNET NETWORK (Wifi is NOT supported)
WINDOWS XP/VISTA/7/2003/2008 (support both 32-bit and 64-bit)
Generally if the PC runs XP and Word/Excel comfortably then VIP.NET will be okay.
SERVERS
Server requirements will depend on the expected number of concurrent users, and the design of the network.
Our basic guidelines are as follows:
· Allow 1 Ghz on 1 core for every 4 users and 100 Mb of memory per user and 1 Gb of memory for the database.
· 60 Gb of storage space will be more than enough for Windows, SQL Server and the database.
Some examples:
A Core 2–Duo @ 2.8 Ghz with 3 Gb memory will support 22 users and the database.
A Core 2-Quad at 3.0 Ghz and 6 Gb memory will support 48 users and the database.
A new i7 CPU with 8 Gb memory will support 68 users and the database.
In a THIN-CLIENT NETWORK ENVIRONMENT is is possible to use any of the following as thin client workstations:
· Thin Client terminals (Winterms)
· Macintosh’s PC’s as a thin client workstation.
· Linux Terminals as a thin client workstation.
With terminal server and thin client, the speed of the workstations does not matter. In this manner any machine capable of running the Remote Desktop client can connect to a terminal server. In real practice, to generate the required screen draws without lag, terminals of 1000mhz + have proved best.
When designing a system for terminal server, the network engineer needs consider primarily how much ram will be needed.
With the server, reserve 1.5 GB for the server and SQL Server services only. Then add 100mb per user after that. If the clients are going to run any other applications such as email clients, office apps, and internet browsing then the ram per user will increase accordingly.
A simple table can plan the ram requirements:
Server 1.5 GB
15 users @ 150mb ea 2250mb
TOTAL RAM required 3.8 GB
SERVER NOTES
With a larger network, it will be necessary and recommended to have a SQL server DATABASE server standalone, an APPLICATION terminal server, and a separate server again for other network services, such as email and domain management.
Both the APPLICATION server and the DATABASE server should have Windows Server 2003 / 2008 Enterprise/DataCentre edition which support’s additional RAM beyond 4GB.
A typical network with 40 clients might have the following:
SQL DATASERVER
Intel Quad Core Processor
8GB or more RAM
SAS 300GB drives
Gigabit Ethernet
Windows Server Enterprise
TERMINAL SERVER
Intel Quad Core Processor
8GB or more RAM
SAS 300GB drives
Gigabit Ethernet
Windows Server Enterprise
MAILSERVER
Intel Processor
4GB RAM
SAS 300GB drives
Gigabit Ethernet
Windows Server
5) Third-Party Integration
Third party products:
VIP.NET works with a number of external hardware devices, such as Eye Machines, ECG Machines, ETT Machines and scanners. Not all devices are supported, and it is very imported to check and confirm that any device is compatible.
Scanners
VIP.NET SQL will work with any scanner which is compatible with the Microsoft .NET scanning.
With choosing models, it is best to decide depending on volume of scanned material.
For example, if only intended to scan a few documents a week, then a cheap flatbed model is adequate.
If scanning in excess of a dozen or so a day, then a multi-page-feed scanner is ideal, but expensive.
Other options exist for multifunction printers - many new printers these days are scanners, copiers, printers and fax machines all built into one.
Network device scanners such as photocopiers can be integrated with the network also.
VIP.NET SQL has support for individual document scanning direct into the individual patient file, bulk-scanning through document feeders, and the ability to scan / bulk-import images into clinical notes.
Digital Cameras
VIP.NET SQL has the functionality to import images from any location on the PC or network. Most digital cameras save their files as .jpg images, which VIP can import into Clinical Images.
Eye Machines
There are a large number of specialist eye-machines which we have developed interfaces for, including machines from TopCon, Humphrey and others.
ECG Machines
VIP.NET SQL does not have a direct interface with any ECG machines, however a number of our clients are exporting the ECG from their generic ECG software, and then importing that as part of the VIP.NET SQL imaging software in Clinical Notes.
Related Items