The TIE install will create a new instance of TIE or upgrade an existing installation. It installs TIE in one of two modes: a production server, which runs as a windows service in the background, or in developer mode, where TIE runs as a desktop application. If you have a purchased certificate, this will dictate what kind of mode is installed. If you are evaluating TIE, then you can choose which mode to install.

 

TIE requires a database in order to operate. Two database servers are supported: Microsoft SQL Server (versions 2008 through 2016) and MySQL (versions 5.1+). If you have an existing installed database, then you can configure TIE to use that. Otherwise, choose to install the Dedicated TIE MySQL Service - this is a full MySQL server (v5.5.27) specially installed to support TIE (though you can choose to use for other purposes if you want). Note that TIE is able to interact with data in almost any database, but requires either Microsoft SQL Server or MySQL for it's own primary database.

 

TIE is cluster aware. For information about installing on a cluster, see Cluster Installation.

 

System Requirements

 

  • Any supported version of Microsoft Windows (32 or 64 bit, though TIE is only 32 bit)

  • Administrator Access to the System (only required for installation)

  • A web browser (Microsoft Edge, IE, Firefox, Safari, or Chrome)

  • A database server, as described above

  • Microsoft Script Engine (usually installed)

  • MSXML Core Services(usually installed, or see https://docs.microsoft.com/en-us/dotnet/api/system.xml?redirectedfrom=MSDN&view=netframework-4.7.2)

  • Internet access is required for some functionality

 

 

The hardware requirements for TIE vary greatly depending on the transaction load and how scripts are used. Disk storage requirements depend how long TIE is configured to retain content. A standard hospital with information flow rates of around 1 message or document per second should be able to run TIE on a standard entry-level server.

 

Notes:

 

 

  • The TIE database can grow rapidly when storing CDA documents and HL7 messages. As the database size grows, performance can deteriorate quickly. System administrators should pay attention to messages archive and deletion policies, and carefully monitor the overall performance of the database using the RDBMS management facilities.

 

  • For normal operation, TIE does not require dbo/sa/administrator/root access to it's database. There is facility to provide account details for an administrative account during install/upgrade. TIE will not apply any permission settings to the databases created. If permission control is sought, this should be reviewed after installation (consult the TIE documentation for assistance with this process).

 

What is installed?

 

The following features may be installed depending on the options selected during the installation:

 

  • TIE Service - The production service that can exchange contents with other systems.

  • Developer - A set of HL7 and script development tools. If the TIE Service is not installed (Developer Mode), it also loads the core module that provides all the TIE functionality

  • Manager - a tool to manage the database and terminology definitions

  • COM Library - The COM interface to TIE. There is no run-time license requirement to use the COM library, and it can be used on PC's on which TIE is not installed.

  • Mobile Clients - helps mobile phones to control TIE (or just use a browser)

  • HL7 v2 schemas - for use in validation, and for reference (refer issues to HL7!)

  • LOINC - LOINC codes and definitions in the knowledge base

  • MySQL - MySQL Community Server 5.5.27 - on port 9557

 

 

Which parts are installed depends on the options selected when the installer runs.

 

 

Dynamic Health IT, Inc . © 2019

FHIR® is the registered trademark of Health Level Seven International and is used with the permission of HL7. The use of these trademarks do not constitute a product endorsement by HL7.