| |
OHM/Web™ Application
Minimum System Requirements |
|
| Web Server |
Java™ Runtime Environment |
1.2.2 or greater |
| |
Database Interface |
JDBC |
| |
Java Compliant Application Server |
JSP/Servlet™ Container |
| |
|
|
| |
Supported Application Servers: |
Oracle™ 9i Application Server or greater |
| |
|
IBM WebSphere® 3.5/4.0 or greater |
| |
|
BEA WebLogic™ 6.1 or greater |
| |
|
Macromedia/Allaire JRun™ 3.0/4.0 or greater |
| |
|
Apache/Tomcat |
| |
|
New Atlanta ServletExec |
| Client Workstations |
Internet Explorer 4.x or greater |
| |
Javascript Support |
| |
Recommend Adobe Acrobat® Reader 5.0 or greater |
| |
|
| Database Server |
Supported Databases: |
| |
Oracle™ 7.3.4 or greater |
| |
Sybase® 11.5.1 or greater |
| |
SQL Server™ 7 or greater |
| |
|
| Security |
SSL |
| |
User ID/Password logon required |
| |
User has ability to change password |
| |
Password change required at user-defined intervals |
| |
Minimum password length required |
| |
|
| |
|
Note: OHM/Web may be run as a pure thin-client application (i.e. no client side Java) or may be run with a client-side java applet. If the client-side java applet is enabled, the client browsers must support this feature (i.e. IE 4.x or greater) |
| |
|
| OHM/ASP™ Application |
| Minimum System Requirements |
| Client Workstations |
Microsoft® Internet Explorer 4.x or greater |
|
| |
Recommend Adobe Acrobat® Reader 5.0 or greater |
| |
Minimum 56K Internet Connection / Recommend 128K or higher for heavy use |
| |
|
Let USSI house your data for a complete turn-key solution! |
|
|
OHM Web-Enabled Client Server Application
Minimum System Requirements |
Microsoft SQL Server™ or Sybase® or Oracle™
(w/MS Terminal Services, Windows 2000 Server or Citrix MetaFrame) |
| Client Workstations |
Intel Pentium® 133 or greater |
| |
64 MB RAM |
| |
Windows 98/NT/2000/XP |
| |
Microsoft NT Terminal Server Version 4.0 or higher, Windows 2000 Server or CitrixTechnologies |
| |
|
| Application Server |
600 Mhz Processor or greater |
| |
Memory Requirements depend upon concurrent users |
| |
Microsoft NT Terminal Server 4.0 or Windows 2000 Server |
| |
|
Note: Must also have an existing Citrix or Terminal Server Product Installed |
| |
Database Server Disk Size Requirements
Greatly depends on the amount of data. Normally 5000 -10000 bytes per patient record. (1,000 patients mean 5 to 10 MB / 10,000 patients means 50 to 100 MB, etc. ) NOTE: OHM can use up to 50,000 bytes per patient if many areas of the software are used. Recommend at least 2 Gigabyte per 50,000 patient records (this means 50,000 patients with multiple hearing tests, encounters, billing records, etc.) |
| |
|
OHM Client Server Application
Minimum System Requirements |
| Microsoft SQL Server™ or Sybase® or Oracle™ |
| Client Workstations |
Intel® Pentium® 133 or greater |
| |
64 MB RAM |
| |
Windows® 98/NT/2000/XP |
SQL Server or Sybase: |
SQL Server or Sybase ODBC Driver |
Oracle: |
Oracle Client and OCI Software |
Btrieve / Pervasive.SQL: |
Btrieve Client Server Requester software |
| |
|
| Application Server |
Minimum Bandwidth 256K |
| |
|
| Database Server |
|
SQL Server: |
7 or greater |
Sybase: |
11.5.1 or greater |
Btrieve / Pervasive.SQL: |
7.3.4 or greater |
| |
Pervasive Btrieve Server Engine |
| |
Windows NT |
| |
Netware 3.11 or greater |
| |
|
Memory requirements depend on concurrent users (recommend 256MB or greater) |
| |
|
|
OHM for Windows® Application
Minimum System Requirements |
| Client Workstations |
Single or Multi-User: |
| |
Intel® Pentium® 133 or greater |
| |
32 MB RAM |
| |
Windows® 98/NT/2000/XP |
| |
|
| Database Server |
Btrieve™/Pervasive.SQL Server Engine |
| |
Memory Requirements depend on concurrent users (recommend minimum of 256MB) |
Minimum Bandwidth 56K (recommend minimum of 256K or greater) |
Windows® NT |
Netware 3.11 or greater |
| |
|
| Application Server |
Network Operating System |
| |
Windows® NT |
Netware 3.11 or greater |
| |
Database Server Disk Size Requirements
Greatly depends on the amount of data. Normally 5000 -10000 bytes per patient record. (1,000 patients mean 5 to 10 MB / 10,000 patients means 50 to 100 MB, etc. ) NOTE: OHM can use up to 50,000 bytes per patient if many areas of the software are used. Recommend at least 2 Gigabyte per 50,000 patient records (this means 50,000 patients with multiple hearing tests, encounters, billing records, etc.) |
|
|
|
|
|
|
|
|
|
|