About the PIX/PDQ Core Projects

The PIX/PDQ core projects define the core functionality of the PIX/PDQ system, including the master index, the domain lookup interface, the master index facade interface, and the audit service interface. They also include two projects that support the PIX/PDQ projects by holding common files or defining utilities.

The PIX/PDQ core projects include the following:

• PIXPDQAuditService

• PIXPDQCommon

• PIXPDQDomainLookupEJB

• PIXPDQMasterIndex

• PIXPDQMuralFacadeEJB

• PIXPDQUtilities

• PIXUpdateNotification

PIXPDQAuditService

The PIXPDQAuditService EJB project defines the interface to the ATNA audit log. This project builds on the functions defined in the ATNA audit log projects and provides an interface to the audit repository. The JAR file from this project is deployed to the application server.

PIXPDQCommon

The PIXPDQCommon project holds all of the processing files that are common to multiple projects in the PIX/PDQ system. These files include the CustomConfig.jar file, the audit service WSDL file and its corresponding schema, and the HL7 V3 messaging schemas. For a complete list of the HL7 V3 artifacts provided in the common project, see HL7 V3 Messaging. No files from this project are deployed.

PIXPDQDomainLookupEJB

The PIXPDQDomainLookupEJB project defines an EJB to resolve the domain identification differences between the HL7 messages and the system codes used by the Sun Master Index. The Sun Master Index typically uses the namespace ID field of the domain identifier to locate a system, but the domain identifier includes two additional fields, universal ID and ID type. This EJB module resolves the identification information (namespace ID, universal ID, and ID type) for the domains in the incoming data and then resolves the information again for outbound data. The JAR file from this project is deployed to the application server.

PIXPDQMasterIndex

The PIXPDQMasterIndex project defines the enterprise-wide master patient index that provides a cross-reference of each domain's local IDs and also maintains a centralized repository of each patient's demographic information. This project contains all of the master index processing logic for data standardization, matching, queries, updates, assumed matches, potential duplicate flagging, and single best record (SBR) survivorship. It also defines the data structure for the master patient index. This project is deployed to the application server.

This project, or files from this project, are referenced from several of the projects included with the PIX/PDQ Manager. You should rebuild and redeploy the required projects if you modify the PIXPDQMasterIndex project in such a way that it needs to be rebuilt and redeployed. The PIX/PDQ Manager provides build scripts that automate the process of rebuilding and redeploying all projects. For more information, see Building and Deploying the PIX/PDQ Manager Projects in Working With the PIX/PDQ Manager.

PIXPDQMuralFacadeEJB

The PIXPDQMuralFacadeEJB project provides an interface to the functions of the master patient index primarily to facilitate the paging of query results. The JAR file from this project is deployed to the application server. The Libraries folder in this project include the index-core.jar and master-index-client.jar files from the master index project (PIXPDQMasterIndex), so the project should be rebuilt and the JAR file redeployed when the PIXPDQMasterIndex project is updated.

PIXPDQUtilities

The PIXPDQUtilities project defines utility functions that support the remaining PIX/PDQ core projects, including exceptions, internationalization and location functions, and EJB client stubs. No files from this project are deployed to the application server.

PIXUpdateNotification

The PIXUpdateNotification project defines a message driven bean (MDB) to handle PIX update notification events. These events occur when changes are made application server. This MDB waits for the JMS topic to receive messages. Messages in the topic trigger the PIX update notification bean, which then checks the message to determine which domain caused the update and looks up the domains that are subscribed to updates from that domain. It generates all the necessary JMS messages and queues them on a V2 or V3 topic.