Configuring the PIX/PDQ Components

The PIX/PDQ Manager was designed to be implemented with minimal required customizations. However, GlassFish ESB provides a flexible framework that allows you to extend the functionality beyond its original design. At a minimum, you would need to configure connectivity information for a product environment. You can also optionally customize the Master Index and how it processes and matches patient records.

Configuring Connectivity Information

You can customize and extend the functionality of the PIX/PDQ Manager, but only the following configuration changes are required for a production environment.

• Add information about each domain that shares data with PIX/PDQ Manager to the database tables. For instructions, see Managing Domains. Make sure the following is correct to enable messaging and PIX update notifications.

  • The receiving URL for each domain.

  • The endpoint (either HL7V2 or HL7V3).

  • The name of the HL7 application or device.

  • The name of the facility or organization (organization is not required).

• Define a list of which receiving domains will subscribe to updates from which sending domains. For instructions, see Maintaining Subscriptions to Patient Updates.

• Verify the port numbers for the following variables. As long as there are no port conflicts, the default values should be fine.

  • jmsURL (for the JMS BC)

  • GFDefaultHttpPort (for the HTTP BC)

  • sunpixmgr-v2–url (for the HL7 BC)

• Verify the URLs for SOAP communication for the following application configurations:

  • sunpdqsup-soap11

  • sunpdqsup-soap12

  • sunpixmgr-soap11

  • sunpixmgr-soap12

Configuring the Master Index

You can configure several features of the Master Index to customize how data is matched and processed through the PIX/PDQ Manager. The type and quality of data stored for a patient varies from system to system and from organization to organization. The Master Index takes this into account and allows you to tailor the processing for your specific data requirements. For example, you may know that some systems contain more accurate data than others. You can weight those systems higher when determining which values will populate the single best record (SBR). Also, some fields might contain more accurate data than others and would thus be given a higher match weight than other, less accurate fields.

You can configure the following components of the Master Index:

• Patient demographic queries, matching queries, and queries performed from the MIDM.

• Standardization and matching rules, including which fields to standardize, which fields to match, a range of match weights to assign to each field, and the type of algorithm to use to match each field.

• Filters for match results (for example, you can configure the Master Index to ignore default values).

• The single best record and how it is formed.

• The appearance of the MIDM.

• The structure of the data stored by the MIDM.

• Field validations.

In addition, you can customize logic for the underlying process of the master index. For complete information on configuring the Master Index, see the Sun Master Index Configuration Guide.

If you modify the configuration of the Master Index, you need to do the following:

1. If you made any changes to the object structure, make the corresponding changes to the mappings in the BPEL processes.

2. Rebuild and redeploy all PIX/PDQ projects. Scripts are provided to automate this process since the projects must be built and deployed in a specific order. For more information, see Building and Deploying the PIX/PDQ Manager Projects