TIE Features

CDA Documents And TIE

• Support for all released HL7 versions from v2.1 to v2.7

• Full support for v2.xml encoding

• Support for v2 localization using z-segments, and even support for re-defining the HL7 standard if necessary

• Support for CDA R2

• Support for CCD

• Support for CDA extensions using alternate namespaces

 

TIE Message Store

• Messages and documents are stored in a transaction-safe database (Microsoft SQL Server or MySQL)

• They can be stored as long as desired, or alternatively archived or deleted after a configurable interval of time since receipt

• They can also have annotations attached which can be used to manage the workflow (see below)

• TIE stores audit information relating to interface status, user history, and a full history for messages and documents, including resending failures

 

Workflow Management

• Messages and/or documents can be passed straight through from one system to another, or stored in the TIE message store, and then forwarded

• They can be sent to multiple destinations using sophisticated routing decision making.

• In addition to destinations that represent other systems, administrators can define virtual queues that can be used for additional workflow management.

• Email, SMS or Windows Event Log notifications can be generated to alert administrators when problems occur

 

Multiple Exchange Options

• TIE supports many network protocols:

  • MLLP: TIE's Minimal Lower Layer Protocol (v2 messages)

  • XDR: IHE's Cross-Enterprise Document Transfer protocol. (CDA documents)

  • HTTP: Several variations of how to use HTTP, principally a simple RESTful based POST protocol

  • Email: A simple email transfer protocol

• TIE also supports file based transfer using a variety of file formats:

  • Plain Text (with scripts to convert the format)

  • CDA documents - one per file

  • HL7- one message per file

  • HL7 v2 Batch file format

  • LLP dump format

• Alternatively, you can use the COM library to exchange messages or documents between your application and TIE, or you can use the web services interface. In addition, it's possible to write a custom DLL to handle message and document exchange

 

Extensibility using scripting

• Utilize a variety of scripting languages to create, validate, manipulate or modify messages and documents or modify and control the workflow.

• Interact with other databases or applications and insert information into the messages or insert data into a database using SQL statements.

• TIE supports a number of scripting languages:

  • Javascript

  • VBScript

  • XSLT

  • KScript (TIE scripting language for generating HL7 and CDA documents)

 

Message and Document Validation

• TIE can validate messages and documents interactively, or as part of the workflow

• TIE supports a number of validation approaches:

  • Basic Validation against the standards

  • Javascript/VBScript

  • XML Schema

  • XSLT

  • OCL (Object Constraint Language)

  • (CDA) Eclipse OHF validation

 

Knowledge Resources

• TIE includes a full knowledge base that provides:

  • a full copy of HL7 v2 definitions (all versions: structures, events, segments, structures, and datatypes)

  • a full copy of the CDA definitions (CDA clones, RIM classes and attributes, and datatypes)

  • LOINC definitions and classifications

  • SNOMED-CT terms and relationships

• These knowledge resources are available through the system as appropriate, for example performing message and document routing based on Snomed-CT subsumption logic

 

Simple User Interface

• A web-based user interface can be used from any web client, including mobile phones.

• Custom mobile phone applets are included for ease of remote management.

• An interactive development environment for working with HL7 v2 messages, CDA documents, and developing and testing scripts for the TIE extensibility features