Skip Navigation Links | |
Exit Print View | |
Developing Oracle Java CAPS Master Patient Indexes Java CAPS Documentation |
Developing Oracle Java CAPS Master Patient Indexes
Oracle Java CAPS Master Patient Index Overview
About Oracle Java CAPS Master Patient Index
The Oracle Java CAPS Master Patient Index Solution
Standardization and Matching Logic
Oracle Java CAPS Master Patient Index and HIPAA
Oracle Java CAPS Master Patient Index Repository Components
Match Engine Configuration Files
Oracle Java CAPS Master Patient Index Runtime Environment Components
Oracle Java CAPS Master Patient Index Enterprise Records
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
Custom Plug-ins for Master Index Custom Transaction Processing
Master Index Update Policy Plug-ins
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
Standardization Engine Plug-ins
Phonetic Encoders Plug-ins for a Master Index
Implementing Master Index Custom Plug-ins
Creating Master Index Custom Plug-ins
Building Master Index Custom Plug-ins
Generating the Master Index Application
To Generate the Application for the First Time
Master Index Database Scripts and Design
Master Index Database Requirements
Database Platform Requirements
Master Index Database Structure
Designing the Master Index Database
Designing for Performance Optimization
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
Step 4: Define Master Index External Systems
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
Master Index Database Table Description for sbyn_user_code
Step 7: Create Custom Master Index Database Scripts
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
Creating a master index application requires in-depth analyses of your business requirements, legacy data, and data processing requirements. After the initial analysis, you can plan and design how you will create the master index application framework and how you will customize that configuration after creating the framework. After creating the master index application, you should perform an in-depth data analysis using the tools provided. This analysis will help you define matching and standardization rules and logic. The data analysis tool is provided in the service–enabled version of Oracle Java CAPS Master Patient Index only, so you would need to replicate your repository–based project using the service–enabled version in order to use the tool. You also need to plan and design each physical component of the Oracle Java CAPS Master Patient Index project and any projects referencing the master index application files..
The following topics provide information about what you need to know and do before you begin to create a master index application.
Before creating the master index application, perform a preliminary analysis against the data that will be stored in the index database to determine the structure of the records. Analyzing your data requires reviewing the message structure of each legacy system that will share data with the master index application. The master index application does not need to store every field from every system, so you can narrow the master index application object structure to just the pertinent fields from each system. However, the master index application stores the same fields for each system. A more in-depth analysis of the field values in the legacy data occurs after the initial master index application framework is created.
Before you create the Oracle Java CAPS Master Patient Index project, analyze the business requirements and determine which project components will help you meet those requirements. Planning the project includes defining how each external system will share information with the master index application and how the master index application will share information with those external systems. In addition, you can incorporate master index Java methods that define how the master index application processes incoming data. Master index methods can also be used to transform the data sent from external systems into a format that can be read by the master index application.
An additional consideration is whether to integrate the master index methods into a Business Process.
Before you begin developing your master index application, make sure you have obtained the following information:
The primary object to be indexed, such as a person, customer, business, and so on (in the case of Master Index, this is likely to be a Patient or Person object)
Any secondary objects, such as telephone numbers and addresses
All fields to be stored in the index for both the primary and secondary objects
The name of each field as it appears on the Patient EDM and whether the field will be a standard text field or will be populated from a menu list (if a field will be populated from a menu list, you should also define an eight-character name for the list)
The fields that are required in order to add a record or that are required for queries
The fields that will appear on reports
The fields that must be unique to an enterprise record (in other words, they uniquely identify a child object within an enterprise record)
The fields that will be used for matching
The fields that will need to be parsed or normalized prior to matching
Any special formatting requirements, such as character types, the data type, minimum and maximum values, and field size
The fields that will appear on Patient EDM search and search results windows
The processing codes for the source systems being integrated into the index