PIX/PDQ Manager Architecture

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.

Figure 1 PIX/PDQ Manager Architecture