The Master Patient Index Framework and the Runtime Environment

The values you enter in the Configuration Editor or directly in the XML files define how other components of the master index application are generated, such as the database scripts, the Patient Enterprise Data Manager, and the dynamic Java API. This section provides an overview of how the values you enter correspond to the runtime environment.

From XML to the Database

The master index database is created using a standard Oracle or SQL Server database and a database script generated directly from the Object Definition file. Additional scripts are created based on any user codes or menu lists you defined for the fields in the object structure. Running the database scripts against the database creates the tables necessary for your master index application and also creates startup data, such as external system information, processing codes, and so on.

From XML to the Patient Enterprise Data Manager

Based on information you specify in the Configuration Editor, edm.xml is generated to define the appearance of the Patient Enterprise Data Manager (Patient EDM) . This file defines the fields and appearance of the Patient EDM and also specifies the searches used by the Patient EDM. The available search types are defined in the Candidate Select file. You can customize many features of the Patient EDM, including the following.

• The fields that appear on the Patient EDM pages

• The field attributes, such as a display name, order of appearance, length, type, data format, and so on

• The types of searches that can be performed and the fields available for each type

• The appearance of search results lists

• The location of the fields on all windows

From XML to the Connectivity Components

When you generate the master index application, several connectivity components are created, including a method OTD, Business Process methods, and an outbound OTD. All are based on the Object Definition file. The method OTD contains certain Java methods for use in Collaborations to specify how data is processed into the database. The outbound OTD is used when publishing messages processed by the master index application for broadcasting to external systems. Generating a project also creates application files that you can drag into the Connectivity Map.

From XML to the Runtime Environment

The information you specify in the master index configuration files is stored in the Repository and is read at runtime when the domain is started. The only exception is the Object Definition file, which is stored only as a record of the object structure. You can modify the configuration files after moving to production; however, for the changes to take effect, you must regenerate the application and then rebuild and redeploy the project to apply the changes to the server. You also need to restart the Patient EDM and any eWays or Binding Components connected to the application for the changes to take effect. Use caution when modifying these files; changing these files after moving to production might result in loss of data integrity or unexpected weighting and matching results.