| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Designing: Enterprise Records |
|
Creating a Runtime Environment
Designing Business Processes in the Sun Business Process Manager
Working with TCP/IP HL7 Collaborations
Developing Sun Master Indexes (Repository)
Master Index Repository Components
Learning about the Master Index Runtime Environment
Master Index Runtime Components
Working with Project Components
Master Index Development Process Overview (Repository)
The Master Index Framework and the Runtime Environment (Repository)
Before You Begin Developing a Master Index (Repository)
Preliminary Data Analysis for a Master Index (Repository)
Planning a Master Index Project (Repository)
Master Index Project Initiation Checklist (Repository)
Creating a Master Index Application (Repository)
Step 1: Create a Project and Start the Wizard (Repository)
Step 2: Name the Master Index Application (Repository)
Step 3: Define Source Systems (Repository)
Step 4: Define the Deployment Environment (Repository)
Step 5: Define Parent and Child Objects (Repository)
Step 6: Define the Fields for Each Object (Repository)
Step 7: Generate the Project Files (Repository)
Step 8: Review the Configuration Files (Repository)
Master Index Wizard Field Properties and Name Restrictions (Repository)
Master Index Wizard Field Name Restrictions (Repository)
Master Index Wizard General Field Properties (Repository)
Master Index Wizard EDM Field Properties (Repository)
Custom Plug-ins for Master Index Custom Transaction Processing (Repository)
Master Index Update Policy Plug-ins (Repository)
Master Index Field Validation Plug-ins (Repository)
Master Index Field Masking Plug-ins (Repository)
Master Index Match Processing Logic Plug-ins (Repository)
Master Index Custom Plug-in Exception Processing (Repository)
Custom Plug-Ins for Master Index Custom Components (Repository)
Master Index Survivor Calculator Plug-ins (Repository)
Master Index Query Builder Plug-ins (Repository)
Master Index Block Picker Plug-ins (Repository)
Master Index Pass Controller Plug-ins (Repository)
Match Engine Plug-ins (Repository)
Standardization Engine Plug-ins (Repository)
Phonetic Encoders Plug-ins for a Master Index (Repository)
Implementing Master Index Custom Plug-ins (Repository)
Creating Master Index Custom Plug-ins (Repository)
Building Master Index Custom Plug-ins (Repository)
Generating the Master Index Application (Repository)
To Generate the Application for the First Time
Master Index Database Scripts and Design (Repository)
Master Index Database Scripts (Repository)
Master Index Database Requirements (Repository)
Master Index Database Structure (Repository)
Designing the Master Index Database (Repository)
Creating the Master Index Database (Repository)
Step 1: Analyze the Master Index Database Requirements (Repository)
Step 2: Create a Master Index Database and User (Repository)
Step 3: Define Master Index Database Indexes (Repository)
Step 4: Define Master Index External Systems (Repository)
Master Index Database Table Description for sbyn_systems (Repository)
Step 5: Define Master Index Code Lists (Repository)
Step 6: Define Master Index User Code Lists (Repository)
Master Index Database Table Description for sbyn_user_code (Repository)
Step 7: Create Custom Master Index Database Scripts (Repository)
Step 8: Create the Master Index Database Structure (Repository)
Step 9: Specify a Starting EUID for a Master Index (Repository)
Deleting Master Index Database Tables (Repository)
To Delete Database Tables (Repository)
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
Step 3: Create the JDBC Resources
Developing Sun Master Patient Indexes
Developing OTDs for Application Adapters
Developing OTDs for Communication Adapters
Developing OTDs for Database Adapters
Developing OTDs for Web Server Adapters
Designing with Application Adapters
Designing with Communication Adapters
Designing with Web Server Adapters
Designing with Sun JCA Adapters
An enterprise record includes all components of a record that represents one entity. The master index application stores two different types of records in each enterprise record: system records and a single best record (SBR). A system record contains an enterprise record’s information as it appears in an incoming message from an external system. An enterprise record’s SBR stores data from a combination of external systems and it represents the most reliable and current information contained in all system records for an enterprise record. An enterprise record consists of both system records and the SBR.
The structure of a system record is different from the SBR in that each system record contains a system and local ID pair. The remaining information contained in the system records of an enterprise record is used to determine the best data for the SBR in that enterprise record. If an enterprise record only contains one system record, the SBR is identical to that system record (less the system and local ID information). However, if the enterprise record contains multiple system records, the SBR might be identical to one system record but will more likely include a combination of information from all system records.
The SBR for an object is created from the most reliable information contained in each system record representing that object. The information used from each external system to populate the SBR is determined by the survivor calculator, which is configured in the Best Record file. This data is determined to be the most reliable information from all system records in the enterprise record. The survivor calculator can consider factors such as the relative reliability of an external system, how recent the data is, and whether the SBR contains any “locked” field values. You define the rules that select a field value to be persisted in the SBR.
In a master index application, each system record and SBR in an enterprise record typically contains a set of objects that store different types of information about the business object. A record usually contains a parent object and several child objects. A record can have only one parent object, but can have multiple child objects and multiple instances of each type of child object. For example, if the business object being indexed is a person, the record can only contain one primary name and social security number, which would be contained in the parent object (for example, a person object). However, the record could have multiple addresses, telephone numbers, and aliases, which would each be defined in different child objects (for example, in address, phone, and alias objects). Each address would be stored in a different instance of an address object.