JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Developing Oracle Java CAPS Master Patient Indexes     Java CAPS Documentation
search filter icon
search icon

Document Information

Developing Oracle Java CAPS Master Patient Indexes

Related Topics

Oracle Java CAPS Master Patient Index Overview

About Oracle Java CAPS Master Patient Index

The Oracle Java CAPS Master Patient Index Solution

Configurability

Standardization and Matching Logic

Matching Weight Determination

Alias Processing

Data Maintenance

Oracle Java CAPS Master Patient Index and HIPAA

Oracle Java CAPS Master Patient Index Repository Components

Editors

Project Components

Configuration Files

Database Scripts

Custom Plug-ins

Match Engine Configuration Files

Object Type Definition (OTD)

Dynamic Java Methods

Connectivity Components

Deployment Profile

Environment Components

Oracle Java CAPS Master Patient Index Runtime Environment Components

Oracle Java CAPS Master Patient Index Enterprise Records

System Records

The Single Best Record

Objects in an Enterprise Record

Oracle Java CAPS Master Patient IndexIdentification Codes

Master Index Development Process Overview

The Master Patient Index Framework and the Runtime Environment

Before You Begin Developing a Master Index

Preliminary Data Analysis for a Master Index

Planning a Master Index Project

Master Index Project Initiation Checklist

Custom Plug-ins for Master Index Custom Transaction Processing

Master Index Update Policy Plug-ins

Enterprise Merge Policy

Enterprise Unmerge Policy

Enterprise Update Policy

Enterprise Create Policy

System Merge Policy

System Unmerge Policy

Undo Assumed Match Policy

Master Index Field Validation Plug-ins

Master Index Field Masking Plug-ins

Master Index Match Processing Logic Plug-ins

Custom Match Processing Logic Methods

Custom Match Processing Logic Plug-in Requirements

Custom Match Processing Configuration

Master Index Custom Plug-in Exception Processing

Custom Plug-Ins for Master Index Custom Components

Master Index Survivor Calculator Plug-ins

Master Index Query Builder Plug-ins

Master Index Block Picker Plug-ins

Master Index Pass Controller Plug-ins

Match Engine Plug-ins

Standardization Engine Plug-ins

Phonetic Encoders Plug-ins for a Master Index

Implementing Master Index Custom Plug-ins

Creating Master Index Custom Plug-ins

To Create Custom Plug-ins

Building Master Index Custom Plug-ins

To Build Custom Plug-ins

Generating the Master Index Application

To Generate the Application for the First Time

To Regenerate the Application

Master Index Database Scripts and Design

Master Index Database Scripts

Master Index Database Requirements

Database Platform Requirements

Operating System Requirements

Hardware Requirements

Oracle Database

Microsoft SQL Server

Master Index Database Structure

Designing the Master Index Database

Designing for Performance Optimization

Data Structure Analysis

Common Table Data

User Code Data

Database Considerations

Database Sizing

Database Distribution

Database Indexes

Creating the Master Index Database

Step 1: Analyze the Master Index Database Requirements

Step 2: Create a Master Index Database and User

Step 3: Define Master Index Database Indexes

To Define an Index

Step 4: Define Master Index External Systems

To Define an External System

Master Index Database Table Description for sbyn_systems

Step 5: Define Master Index Code Lists

To Customize Common Table Data for Oracle

To Customize Common Table Data for SQL Server

Step 6: Define Master Index User Code Lists

To Define a User Code List

Master Index Database Table Description for sbyn_user_code

Step 7: Create Custom Master Index Database Scripts

To Create a Custom Script

Step 8: Create the Master Index Database Structure

To Create the Database Structure

Step 9: Specify a Starting EUID for a Master Index

Deleting Master Index Database Tables and Indexes

To Delete Database Tables and Indexes

Defining a Database Connection Pool Through the Application Server

Step 1: Add the Oracle Driver to the Application Server

Step 2: Create the JDBC Connection Pools

To Create the JDBC Connection Pools

Step 3: Create the JDBC Resources

To Create a JDBC Resource

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.

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 Adapters 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.