With the current focus on improving the exchange of electronic healthcare information, the ability to share information stored in various healthcare systems and healthcare organizations is becoming a requirement. Integrating healthcare systems makes data more easily accessible to providers and participants, ensures that the data is accurate and current, and provides the basis for the exchange of electronic health data. The Health Information Technology for Economic and Clinical Health (HITECH) Act encourages the adoption of electronic healthcare records by all providers and also defines penalties for breaches of patient health information.
Sun's PIX/PDQ Manager provides a flexible solution to healthcare integration needs in the form of a lightweight enterprise service bus (ESB) that can be easily customized and extended to meet your integration needs. The processing logic in the PIX/PDQ Manager is based on the guidelines and standards put forth by Integrating the Healthcare Enterprise (IHE). This assures compatibility with other vendors and healthcare organizations, making it easier to integrate now and in the future.
The PIX/PDQ Manager forms a specialized implementation of HL7 messaging that facilitates patient health information exchange, and supports both HL7 v2 and HL7 v3 messaging. It leverages the advanced standardization and matching algorithms of Sun Master Index to cross-reference and uniquely identify the patients in your healthcare organization. Master Index provides a single complete view of the participants in your healthcare system and is able to quickly reconcile which information is associated with which patient, allowing you to quickly create a complete medical history.
The PIX/PDQ Manager processes messages based on the IHE frameworks, which define how to process HL7 messages using existing standards when available. In compliance with these frameworks, the PIX/PDQ Manager generates and maintains an audit repository of all events processed by the manager, and also maintains a trace record of how each message was processed through the system and by which components. Information about the state of the PIX/PDQ Manager components is provided by a common logging, alerting, error handling, and reporting mechanism. The PIX/PDQ Manager provides a monitoring and management tool where you can monitor the audit repository, log messages, and message traces.
Integrating the Healthcare Enterprise (IHE) is an organization whose aim is to improve how electronic patient information is shared among healthcare systems and, by doing so, to make sure that current and accurate data is readily available to both patients and healthcare professionals. IHE has developed technical frameworks that define how to process healthcare events, how data is shared, how security is handled, how audit records are generated, and how components interact with one another. The frameworks are made up of integration profiles that provide specifications of how each type of event is processed and how the audit message should be generated for each type of event. The profiles also define standards for security, communication, and time synchronization. These profiles are designed to ensure that data is transmitted securely and accurately among systems, and that data handling is coordinated according to communication and security standards. Having this common framework gives the various participants in a healthcare system a common base for integrating disperse systems.
Sun's PIX/PDQ Manager focuses on the following IT Infrastructure profiles of the IHE framework:
Audit Trail and Node Authentication (ATNA): This profile describes authenticating systems and transmitting audit events to a repository. The PIX/PDQ Manager provides a complete audit log of events processed through the PIX/PDQ system in the prescribed ATNA format. You can view a complete log of audit events on the PIX Console. The format varies according to the type of event being processed.
Patient Identifier Cross Referencing (PIX): This profile describes cross-referencing patient identifiers between the various systems that register and store healthcare information. This allows domains to correlate information about a patient from multiple sources that use different identifiers. Sun Master Index maintains a complete cross-reference of patient identifiers using probabilistic matching to identify records. When updates are made to key information in the master index database, Master Index generates PIX outbound notifications, which can then be broadcast to interested domains. The PIX/PDQ Manager supports PIX queries for patient identifiers associated with a given identifier.
Patient Demographics Query (PDQ): This profile describes system queries against a central repository of patient information to obtain a patient's demographic information, allowing multiple domains to query a central source of patient information to retrieve demographic data for matching patients. Sun Master Index maintains this central repository for the PIX/PDQ Manager, and processes patient demographic queries.
Each healthcare participant registers identifiers for patients in their own computer system, also known as a domain in the IHE framework. Participants maintain control over their own domain's index, but sometimes need access to information in a different domain. They can access the central repository of the PIX/PDQ Manager to find additional local identifiers for their patients. Domains can also be automatically notified when other systems update patient information.
As per IHE standards, Sun's PIX/PDQ Manager cross-references patient IDs (PIX) and supports patient demographic queries (PDQ). It also supports PIX queries for local IDs that are associated with a given local ID from a domain and patient identity feeds, such as when a record is added or updated in a domain. The PIX/PDQ Manager can broadcast notifications to interested domains when certain updates occur in the master patient index.
The Audit Trail and Node Authentication (ATNA) profile defines how audit messages are generated and formatted. The audit repository helps ensure that patient information remains confidential, data integrity is maintained, and users are accountable for accessing data. The Sun PIX/PDQ Manager supports the ATNA profile by maintaining an audit repository that stores information about each event processed through the system, including the source type and source ID, event type, event ID, event action, and event outcome. It also stores the date and time the event occurred and the date and time it was received by the PIX/PDQ system.
Sun's PIX/PDQ Manager uses various components of GlassFish ESB such as HTTP, JMS, and HL7 Binding Components; the BPEL Service Engine; Composite Applications; Java EE EJBs; and Sun Master Index. The solution includes the following GlassFish ESB components:
Sun Master IndexMaintains a central repository of patient information from all domains that share data in the PIX/PDQ system, and also provides the cross-referencing, query, standardization, and matching functions to support patient identity resolution for PIX and PDQ requests. The master index can detect when two records from the same or different domains are referring to the same person, and can reconcile the two records to determine the best information to use.
PIX ConsoleProvides a view into the ATNA audit repository and PIX/PDQ processing log, and traces how a message is processed through the PIX/PDQ Manager. The console also provides tools to manage and maintain domains, subscriptions to outbound notifications, and application configurations and variables.
BPEL Service EngineDefines the processing flow and business logic of messages through the PIX/PDQ system, including routing and transforming data, mapping data fields, and calling the appropriate functions from other PIX/PDQ components. The BPEL processes also write the required data to the ATNA audit repository, and are responsible for generating HL7 ACK/NACK responses. Each BPEL process is specific to either HL7 v2 or HL7 v3.
HL7 Binding ComponentSupports the HL7 messaging structure up to version 2.6 and defines the communication protocols for connecting to the HL7 messaging systems The HL7 Binding Components is configured to use the Minimal Lower Layer Protocol (MLLP) version 1 to connect to external systems.
HTTP Binding ComponentSupports the HL7 v3 messaging structure and defines the communication protocols for connecting to the HL7 messaging systems. The HTTP Binding Components uses the SOAP protocol to connect with external systems. The PIX/PDQ Manager provides for and supports both SOAP versions 1.1 and 1.2.
JMS Binding Component: Supports outbound notifications from the master patient index, which are published to JMS topics and then distributed to all subscribed domains.
The following figure illustrate the interaction of the above components in the PIX/PDQ Manager.