Integration & Interoperability

Enterprise-Wide Integration Engine (IE) for Disparate Systems

The Astro Interface Engine is a message broker designed for structured data messaging and integration. It supports all industry-standard protocols, such as HL7, XML, ASCII text and SQL, etc. Using state-of-the-art Microsoft Windows-based foundation tools and Microsoft SQL Server, TSG offers decades of successful experience and technical know-how in data and application integration across heterogeneous platforms.

We have provided one-stop, seamless, robust and end-to-end integration solution for multiple HCIS vendors, including Siemens (SMS), McKesson (HBOC), Cerner, Eclipsys, Sunquest, Dictaphone, ChartMax and ECDS, etc. For MEDITECH hospitals, there are built-in integration adapters with no additional interface/support required from MEDITECH.

An assortment of interfaces have been developed since Astro's introduction in 1993, of which the following are examples:

KEY STRENGTHS

Designed to support all three layers of integration: Session layer, Middle-ware layer and Database layer
Comes with a built-in Web-based Interface for monitoring and tracking support issues
One-stop turnkey integration solution for the entire enterprise; i.e. in addition to HL7 text messaging, it supports all digital objects, for e.g. Wave files, Tiff, JPEG and PDF, etc.
Workflow-based integration across heterogeneous platforms
Open, robust standards and improved productivity
Single point of access for patient information
Real-time or batch interface
PACS and other modality integration
Web and RHIO integration
Third party system integration
Enterprise-wide data consistency
Centralized security and audit trail
Simplicity of drag-and-drop graphical user interface
Provides flexibility, scalability, manageability and interoperability
Decades of successful experience and technical know-how in data, application, and workflow integration

EMPI (Enterprise-Wide Master Person Index)

The major goal of an EMPI (Enterprise-wide Master Person Index) is to provide a seamless methodology in which all providers in an integrated delivery environment are connected together to capture and feed critical data sets of information for improved customer service, better patient care, and lower cost across the enterprise. TSG’s EMPI supports both message-based and object-based integration, such as HL7, SQL, and XML, etc. It centralizes the process for patient record index data from single or multiple facilities, which are then entered into the single, centralized EMPI database. This central location, developed and managed by EMPI, is responsible for the preservation of the complete master record index from which all sources will now draw their information.

As patients enter the EMPI system, they are accurately identified and assigned a unique and universal EMPI number. This number is completely separate from each facility’s medical record number the patient may have come in with, and is used by the EMPI database to properly distinguish, maintain, and merge patient data. This database is continuously updated as all medical record index data is examined and measured for possible merges and entered into the system. This again ensures that accurate, consistent, and reliable information will be available for each patient across the continuum of care. Potential errors are minimized via the use of improved patient search tools, sophisticated comparison algorithms, and effective user interfaces.

KEY STRENGTHS

Consolidates/merges duplicate patient medical record index data from multiple sources/systems
Longitudinal patient records for better quality of care
Robust audit trail to comply with HIPAA standards
Integrate with document imaging/management system
Improve clinician and patient satisfaction

FEATURES

Browser-based model for presentation of patient index data and merging process
Availability of up to 120 data fields for viewing and probing to merge records
Highly accurate algorithms for detecting patient identifiers and for establishing merges between record numbers representing the same individual
Built on Microsoft SQL RDBMS
Synchronizes the HIS database in a real-time mode
Ability to log all transactions with user identification to track data entry and other errors

BENEFITS

Ensures current and accurate patient information is available across the continuum of care
Ensures that patients are not asked the same questions repeatedly throughout episodes of care
Prevents fraud/identity swaps
Saves time and eliminates errors
Improves data quality
Effortless integration with existing systems and platforms
Preserves organization's existing policies and procedures

MRC (Medical Record Cleanup)

With TSG’s MRC product, you can streamline and merge patient index data and ensure that the most accurate and current patient demographic information is available across the enterprise. Our innovative, browser-based method to merge duplicate data speeds up the process of matching records accurately. You can also help overcome inconsistencies and errors created by different data entry practices used by multiple registration systems across a community.

KEY STRENGTHS

Compare a multitude of data elements
Rule-based logic that can be customized to fit hospital standards
Match patient records even when their individual data elements are not exactly the same
Reporting tool lists all index data edits and updates
Create a cleaner and more manageable index
Reduce the need to re-enter patient information
Drastically reduce costs associated with medical record cleanup
Bypass human error
Better quality of care with longitudinal patient record

FEATURES

Browser-based model for presentation of patient index data and merging process
Availability of up to 120 data fields for viewing and probing to merge records
Highly accurate algorithms for detecting patient identifiers and for establishing merges between record numbers representing the same individual
Consolidates/merges duplicate patient medical record index data from multiple sources/systems
Built on Microsoft SQL RDBMS
Synchronizes the HIS database in a real-time mode
Ability to log all transactions with user identification to track data entry and other errors

BENEFITS

Ensures current and accurate patient information is available across the continuum of care
Ensures that patients are not asked the same questions repeatedly through episodes of care
Prevents fraud/identity swaps
Saves time and eliminates errors
Improves data quality
Effortless integration with existing systems and platforms
Preserves organization's existing policies and procedures
Robust audit trail to comply with HIPAA standards

PACS Integration

PACS Integration Engine is a middleware component of TSG's multi-purpose Integration Engine (Astro Interface Engine) specialized for PACS integration. You can transmit ADT, Orders/Exams, and Results data in real-time to PACS systems with the PACS Integration option. With open standards for all messaging, you can launch and display the medical image with a single log-on, anywhere and anytime to anyone. You can launch PCI/EMR with one button and support all HL7 messaging functions related to your HCIS.

Middleware Level Integration Option

TSG creates a component to transmit ADT, Orders/Exams, and Results data from MEDITECH in a real-time manner. This interface supports all messaging functions described in the HL7 specifications as these relate to the MEDITECH system.

Pre-Fetching Option

TSG creates a component to transmit Patient Scheduling data in HL7 format from MEDITECH in a real-time manner.

Historical Data Transfer Option

TSG creates a component to transfer historical results data from MEDITECH.

FUTURE EXPANSION CAPABILITIES

Paperless

The real power of PACS is achieved when your clinical department workflow is automated to be filmless and paperless. In order to become paperless, TSG can work with your specific workflow process and based on your needs, TSG can provide seamless solutions that come with built-in integration to MEDITECH and non-MEDITECH platforms as applicable.

Multi-Facility Integration and Master Patient Index

It is important to note that once you have this IE infrastructure in place, you can add new integration messages to build a multi-facility Master Patient Index, linking disparate physician practice systems to create community-wide integration. This feature helps you to attract more physicians, better market your radiology and other clinical services, and improve your physician and patient satisfaction across the community.

Session Level Integration

Depending on if you are running MEDITECH’S Magic or Client/Server version, TSG has developed software that will allow you to launch PCI or EMR via a button on the toolbar using a single log-on concept. TSG will pass the medical record number, patient account number, and the exam information to the PACS vendor to launch and display the desired image. The software also supports the web-enable option to launch PCI or EMR from a browser. The integration option is physician-based and community-based, connecting systems for integrated healthcare across the community.

HIS to HIS Integration

For HIS to HIS Integration, our main goal is to design an integration strategy to overlay new technology to enhance current processes, yet maintain workflow integrity and customer satisfaction.

The challenge is how to lay an integration strategy—how to synchronize data, accelerate its movement, automate processes, and communicate information to facilitate solid healthcare decisions. Architecturally, TSG’s HIS to HIS Integration strategy is designed to conquer all of the challenges facing today’s and tomorrow's healthcare arena. We provide integration between disparate Health Information Systems like ‘hand in a glove.’

Our HIS To HIS Integration methodology starts with understanding how your current HIS dictionaries, CDS’s, and workflow is functioning, followed by overlaying the new technology to enhance process and maintain workflow integrity.

KEY STRENGTHS

Open Systems Approach
Relational Database driven for rule-based messaging
Industry-Standard Programming Language Communication Protocol
Combination of Interfaces and Synchronization for an integrated solution

BENEFITS

The best-in-class integration solution that is customized for your unique business needs
Reduce the time, money, and effort needed to connect information systems together
Greater operational efficiency
Higher return on investment

Object Integration

TSG’s Object Integration strategy provides a powerful infrastructure to prepare your hospital for the Healthcare industry’s migration toward interoperable systems.

Industry-standard objects are supported using TSG’s powerful Object Integration Engine. Our integration engine makes interoperability and integration possible by encapsulating heterogeneous objects through its powerful message broker technology.

One of the most powerful features of the Object Integration Engine is the ability to support Napster-like integration for your Healthcare Information System. It provides the drag-and-drop feature to support all industry-standard documents and objects. We support all of the object file formats that are supported by Windows.

KEY STRENGTHS

We support all of the file formats listed below:

*.avi
*.jpeg
*.rtf
*.tif
*.htm
*.msg
*.mpeg
*.bmp
*.prn
*.xls
*.gif
*.wav
*.doc
*.txt
*.pdf

BENEFITS

Ability to access objects with a single log-on, anywhere and anytime by any authorizer
Reduces the number of HL7 interfaces required
Improves end-user experience
Improves efficiency, accuracy and functionality across the organization

MEDITECH PP to Third-Party Integration

MEDITECH PP to third-party HR integration is a two-way integration between MEDITECH's PP application and a third party HR application. This integration involves the ongoing identification of source tables and source fields by the vendor. TSG works with the third-party vendor to develop mutually acceptable SQL views that will be used to import the data back into MEDITECH using interface standards acceptable in the MEDITECH marketplace.

Interface Specifications

SQL database is utilized by both vendors to contain permanent tables, interface tables and interface views.
Data transfer is accomplished by querying views.
The interface table is populated via a series of triggers that have been placed on the source fields within the source tables as identified in the Database Table Field Scope (DTFS).
Only records that have a trigger time less than or equal to the SnapShotTime field (defined in the DTFS) and that have not been transferred must be displayed.

Interface Views

An individual view exists for each source table identified in the DTFS.
The individual view contains all source fields for that source table as identified in the DTFS.
The views do not contain source fields from different tables other than the employee number.
The views are named using the view names as identified in the DTFS.

Triggers

A trigger exists on every source field within every source table for each event as identified within the DTFS.

Refreshment Cycle

Interface data transfer rate is determined by mutual agreement.