TITANIUM
SCHEDULE
Requirements

This page is intended primarily for your technical staff. It outlines Titanium Schedule’s hardware, database, and operating system requirements. Technical documents containing this and other information are available upon request from our sales department.

Hardware & Operating Systems

If your center can use one of your university's existing file servers and/or SQL Servers, or if you have your own file server, then you will probably not need to purchase any new computers to run Titanium Schedule. Our software does not require its own dedicated server. All portions of Titanium Schedule will operate in a virtual server environment without issue.

Titanium Schedule is a client-server application with three parts:

  1. Workstation: Microsoft .NET Framework 4.7.2 or later must be installed on each user's workstation computer.
  2. Application Files: The application files are stored in a shared folder where they can be accessed by all workstations. This shared folder can be on any file server (Windows, Novell, Linux). The security for that folder should be set to center personnel only. No confidential data is stored in that folder unless a user exports and saves data there.
  3. Data: Data is stored in Microsoft SQL Server (2012 and later versions). The free SQL Server Express Edition will work for many small centers with 20 users or fewer. Larger centers, centers that expect to have more than 10 GB of data, or if you plan to use Titanium Schedule in a multi-department capacity, you will need SQL Server Standard or Enterprise Edition.
Hardware Configuration

Typical hardware configuration is as follows:

  • SQL Server is hosted by your university's computer support staff on a physical, virtual, or cloud server.
  • The shared application folder is on one of your university's existing file servers.

Frequently, universities already have SQL Server installed for other applications on campus. A single SQL Server can support many applications, depending on resources and licensing requirements. This configuration often requires no new hardware or software purchase. It has the added benefit that your local computer support staff will maintain the SQL Server and oversee automatic backups of the data. SQL Servers hosted by your computer support staff are usually in a secure area with emergency power, unattended backups, and reside behind firewalls.

System Requirements

There are separate requirements for the server, workstations, and the optional Web Component. The data is stored on the server in Microsoft SQL Server. Titanium is only compatible with Microsoft SQL Server and does not run on MySQL, Oracle, or other data repositories.

The hardware requirements for Titanium Schedule are very modest, and as you can see by the minimum required specifications below, almost any Windows-based computer you can purchase today is more than adequate.

Server Requirements

The following requirements are for the computer running SQL Server which contains the data from Titanium Schedule. At some centers, the SQL Server is installed on a university-hosted computer or the center's existing file server, so an additional computer is not required.

  • Desktop Operating System: Any recent version of Windows Desktop. (Windows 10 is the oldest acceptable version)
  • Server Operating System: Any recent version of Windows Server. (2012 is the oldest acceptable version)
  • Required Software: Any recent version/edition of MS SQL Server (2012 is the oldest acceptable version) and .NET Framework 4.6.1 or later.
  • Hardware recommendations for your Windows server: Windows Server Catalog
  • RAM: 4 GB recommended (RAM is more important than CPU speed for performance)
  • Disk Space:
    • Minimum of 600 MB for SQL Server installation. At a large center, the Titanium database will probably grow to 2-4 GB over a few years. If the center is going paperless and scanning a lot of old documentation into Titanium, storage needs could be several times that large.
    • At least 400 MB for the shared application folder.
Workstation Recommendations

Each computer workstation that will be running Titanium Schedule will need the following:

  • Screen resolution of 1024 x 768 or higher.
  • Intel Pentium or compatible 1GHz or higher processor. (800 MHz or higher is supported but not recommended)
  • 1GB Memory (512 MB is supported but not recommended)
  • Operating System: Microsoft Windows® 10 or later
  • Microsoft .NET Framework 4.7.2 or later
  • Disk Space: 200 Megabytes of available hard-disk space.
Web Component (Optional)

There are two available choices for the optional Web Component feature:

  • Installed and maintained by your IT group on an IIS server on your campus
  • Hosted by Titanium Software without the need for IT involvement

The requirements in the remainder of this section only apply if the Web Component is installed locally by your IT group.

The Web Component is an ASP.NET website and requires Microsoft Internet Information Services (IIS) 8 or later with .NET Framework 4.8. The web server OS must be Windows Server 2012 or later. The web server must also be able to access the SQL Server where the Titanium database is installed. The web server will use a restricted account to access the SQL Server, and that account can only insert new records into the confidential tables. The account does not have the rights to view, update or delete any confidential information.

To encrypt data traffic between the devices used by clients and the web server, a minimum of Transport Layer Security (TLS) 1.2 is required.

Microsoft SQL Server version 2012 is the oldest supported SQL Server version. The SQL Server that hosts your center’s Titanium Schedule database must be updated with the latest Microsoft SQL Server Service Pack. The preceding link provides service packs for each supported version of Microsoft SQL Server.

Note: If you are a current Titanium customer who is considering adding the Web Component, your Titanium Schedule database version must be 150101 or newer. You can see how to determine your database version by visiting the Program Updates page at our website.

Users, Database, Performance

There are several factors that could affect how many users in your center can use Titanium Schedule simultaneously with acceptable performance. Titanium Schedule itself is licensed for a given number of concurrent users. Our base product licenses your center for five users, and you can purchase additional user licenses in five-user blocks. Your license agreement with Microsoft for the version of SQL Server you use, combined with the performance of the hardware and network you use, will determine how many users your center can support with acceptable performance. For example:

  • Microsoft SQL Server Standard or Enterprise Edition (version 2012 or later) can support hundreds of users and databases larger than 10 GB.
  • Microsoft SQL Server Express (2012 or later) can support at least 20 users and databases up to 10 GB. The Express Edition is available for free from Microsoft.
Titanium on Macs

Titanium Schedule does not have a Mac native client, but our software will work in a Mac environment under the following conditions:

1. You run a PC emulator like Parallels or vmFusion on your workstations.

OR

2. Your IT department serves Titanium Schedule on a Citrix server.

Titanium Software, Inc. does not support issues with Mac computers, PC emulators, or the Citrix environment. Those will be the responsibility of your IT department.

There are several universities that are successfully using Titanium Schedule in a Mac environment.

Security

Security is the most important feature in EMR software. Unfortunately, it often gets the least attention. Some software products store data in easily accessible files, like an Access database, which can be vulnerable to data theft.

Titanium Software, Inc. takes security very seriously. Our software uses Microsoft SQL Server to store your data. This allows users of our program to access your facility's sensitive data without having direct access to data files. Users are thus prevented from activities like copying data files to a flash drive, CD, or attaching data files to e-mail for sending off-site.

HIPAA

Even though Titanium Schedule has HIPAA (Health Insurance Portability and Accountability Act) compliant features like user names, strong passwords, internal security levels, a login audit trail, inactivity timeout, etc., there is often a great deal of confusion about what HIPAA requires and how difficult it is to implement and maintain.

Here's what our company president has to say about HIPAA and Titanium Schedule:

Titanium Schedule meets the requirements specified by HIPAA when it is installed as specified in our installation instructions and security checklist document.

The term “HIPAA compliance” applies to facilities, not to software. Software can have HIPAA-compliant features, as Titanium Schedule does, but it is the overall policies and procedures at the facility that determine if the facility is HIPAA-compliant. No software by itself can make your facility HIPAA-compliant.

For example, if a software user writes their password on a Post-It note and attaches it to their monitor, the facility is not HIPAA-compliant. If an IT department makes a backup copy of HIPAA-protected data, and the backup is not encrypted or stored under lock-and-key, the facility is not HIPAA-compliant.

Karl Zercoe, President
Encryption

Most of the questions we receive about HIPAA concern encrypting data. There are several places where encryption can be applied:

Password Encryption

Users' passwords must be encrypted, and this is done automatically inside Titanium Schedule.

Encryption of Network Traffic

Titanium Schedule uses Microsoft SQL Server to store data. SQL Server can be configured to encrypt all data while it is being transmitted using SSL. Our installation instructions explain the simple process of turning on this feature.

Encryption of Data on the Hard Drive

There are multiple ways to encrypt the files on the hard drive where SQL Server stores data. TDE (Transparent Data Encryption) is available in some versions of SQL Server. TDE has the added benefit of automatically encrypting backups of the database. You must be extremely careful to make copies of the encryption key and securely store it off the computer where SQL Server is installed. If the SQL Server fails, all your backups will be useless unless you have the TDE encryption key stored somewhere else.

Another way to encrypt the files on the hard drive is to use the Microsoft EFS (Encrypted File System) that is built into the Windows operating system.

There is more information on the these and other security issues in this whitepaper from Microsoft.

Encryption of Data Backup Copies

If you do not use TDE as mentioned above, then you will need to do something extra to secure the backup copies of the data. This might be physically securing the backups or using one of the many third-party encryption utilities. Make sure that encrypted backups can be decrypted on a different computer. Do not encrypt backups using an encryption key that is only available on one computer, because if that computer fails, all your backups are useless. As with all backup approaches, it is best to test your technique before relying on it. Backup your data, encrypt it, then decrypt and restore the data on another computer. Remember, if your backup encryption key is lost, your backups are useless.