iWay Public Health Information Network (PHIN) Touchpoint Adapter
iWay Public Health Information Network (PHIN) Touchpoint Adapter (PDF).
Download free Adobe Acrobat Reader.
Fast, Cost-Effective PHIN Implementations
The iWay Public Health Information Network (PHIN) Touchpoint Adapter eliminates the complex custom programming that would be required to move data from laboratory information management systems (LIMS) and electronic lab reporting (ELR) systems into a database that complies with the PHIN logical data model (LDM).
To support their vision of a PHIN - an electronic nervous system that provides a platform for routine public health activities, bioterrorism response and detection, and disease surveillance, the CDC mandated the use of a specific LDM in which all healthcare-related information should be stored. Compliant healthcare organizations must capture data from LIMS and ELR systems and load it into a common relational database.
Performing this task by hand would require expertise with many diverse technologies, including:
-
HL7 2.3 and 3.0 message formats for interoperating with LIMS and ELR systems -
Sophisticated programming skills needed to parse, validate, and transform the data into formats compatible with the data load -
Data modeling skills to map incoming message-based data to the appropriate database structures -
Relational database skills to execute the data load process The iWay PHIN Touchpoint Adapter is a commercial, off-the-shelf (COTS) product that encapsulates these requirements so they can be achieved automatically, without custom programming. This enables an organization to communicate easily with public and private medical labs regarding test results for reportable conditions, using standard communication protocols and message formats.
Flexibility, Compatibility, and Extensibility
Users may configure the iWay PHIN Touchpoint Adapter to stand alone, but it was developed as part of the iWay Universal Adapter Suite - an industry-leading platform for message handling, Web services publishing, and integration.
The iWay Universal Adapter Suite offers deployment flexibility in every configuration, including the ability to deploy on any major J2EE application server.
The iWay Universal Adapter Suite supports a wide variety of industry standards, including many more than those that come with the iWay PHIN Touchpoint Adapter. It was designed to accommodate almost any industry-standard format, messaging protocol, and service interface. This broad standards compatibility, combined with tools that help users extend the iWay PHIN Touchpoint Adapter, gives organizations the ability to:
-
Accept non-HL7 message formats -
Modify the touchpoint parsing, validation, and transformation rules -
Extend the PHIN logical data model or iWay's physical implementation of it to capture additional information or change normalization levels -
Provide Web services, ODBC, JDBC, and XML interfaces to other organizations that need to consume data already loaded in the PHIN data structure For example, the iWay Universal Adapter Suite can communicate information from hospital emergency rooms, emergency medical vehicles, and pharmaceutical systems using any standard protocol (e.g., FTP, HTTP, AS2) and any data format (e.g., flat files, Microsoft Excel spreadsheets, XML, HIPAA documents).
Messaging Protocols
The CDC's PHIN architecture specifies ebXML messaging for data exchange between public health partners. The CDC offers its own implementation of ebXML messaging, called PHIN MS. The iWay PHIN Touchpoint Adapter can receive information from any organization that uses PHIN MS, completely automating the process of receiving its data and moving it into the logical data model.
In addition, the iWay Universal Adapter Suite can use many other types of protocols as well. On trusted or internal networks, for example, organizations may choose to use standard TCP/IP, HTTP, or FTP protocols. The iWay PHIN Touchpoint Adapter can even accept e-mail messages with the data inline or in attachments. Also, iWay's support for emerging standards such as EDIINT ensure that if your organization needs to branch out of ebXML - for receiving additional message formats, or as future standards changes require - your PHIN will always be able to communicate with any other organization.
Message Formats
The iWay PHIN Touchpoint Adapter provides out-of-the-box support for HL7 versions 2.3.1 and 3.0, which are commonly used for ELR. The adapter can also be used in conjunction with other format adapters to accept flat files, HIPAA documents, Excel spreadsheets, and more.
Targeted Data Structures
The iWay PHIN Touchpoint Adapter can insert data into any major relational database, including IBM DB2, Microsoft SQL Server, Oracle, NCR Teradata, and Sybase.
In addition, the adapter can be modified with iWay Universal Adapter Suite tools to support different physical models that support the logical model mandated by the CDC. Different levels of normalization, indexing, and extensions to tables can all be created for specialized purposes, while still maintaining complete CDC LDM compliance.
Electronic Lab Reporting
The iWay PHIN Touchpoint Adapter was tested with the nation's two leading medical laboratories, LabCorp and Quest Diagnostics, to ensure that it could easily parse HL7 messages, map them into appropriate data structures, and load them into a PHIN/ NEDSS-compliant database.
The iWay Public Health Information Network Suite
The iWay PHIN Touchpoint Adapter can be acquired standalone or with complementary business intelligence, reporting, and real-time alert software as part of the iWay Software PHIN Suite. Professional services are also available as part of this product suite.
The iWay PHIN Suite works in conjunction with products from parent company Information Builders.
Some of our other Intelligent Adapters include:
Find Out More
For More Information
No other company provides the kind of sophisticated data integration and SOA-based integration technology that iWay Software does. To find out more, call toll-free (866) 297-4929 or e-mail us at info@iwaysoftware.com.
Interact with organizations that don't use ebXML as a transport -