Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Designing: Step 5: Define Master Index Code Lists (Repository)
 

Classic Java CAPS

Developing Java CAPS Projects

Using SOAP Message Handlers

Creating a Runtime Environment

Designing Business Processes in the Sun Business Process Manager

Working with TCP/IP HL7 Collaborations

Developing Sun Master Indexes (Repository)

Related Topics

Sun Master Index Overview

About Sun Master Index

Master Index Repository Components

Learning about the Master Index Runtime Environment

Master Index Runtime Components

Enterprise Records

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

To Regenerate the Application

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

SWIFT Integration Projects

Java EE Based Components

Designing with Sun JCA Adapters

About the TCP/IP JCA Adapter

Defining Constants and Variables

Using Database Operations

Developing Sun Master Indexes

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Step 5: Define Master Index Code Lists (Repository)

You only need to perform this step if you defined any fields in the object structure to have a code module. The SQL script for entering processing codes and descriptions into the database is written in PL/SQL. The wizard creates a stanza in the Code List file (located under the Database Script node of the project) for each code list you specified in the field properties. You need to customize the file by defining the entries for each code list. This script inserts data into two tables: sbyn_common_header, which lists the types of common table data, and sbyn_common_detail, which lists each common table data element. Before you begin this step, complete Step 4: Define Master Index External Systems (Repository).

Note - The codes you specify in this file can be no longer than eight characters (the codes are the second value in the value list for each common table data type and data element).

To Customize Common Table Data for Oracle
  1. Under the master index project in the Projects window, expand Database Scripts and then open the Code Lists file in the NetBeans editor.
  2. Scroll to the following line.

    codes tCodeList := tCodeList(

    The statements following this line must be customized.

  3. In the first code list stanza, change “module description” in the first line to a brief description of the code type.

    For example:

    -- **** PHONTYPE **** tCode(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’),

  4. Create the entries for the module using the following syntax:

    tCode(’V’, ’code’, ’code description’),

    where “code” is the processing code of the data element and “code description” is the description of the element as you want it to appear on the Enterprise Data Manager windows. For example:

    -- **** PHONTYPE **** tCode(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’), tCode(’V’, ’H’, ’HOME’), tCode(’V’, ’C’, ’CELL’), tCode(’V’, ’F’, ’FAX’), tCode(’V’, ’O’, ’OFFICE’), tCode(’V’, ’HB’, ’HOME BUSINESS’),

  5. Repeat the previous two steps for each code list type defined in the file.
  6. If you specified additional code list fields in the Object Definition file and the Enterprise Data Manager file after the database scripts were generated, add a new stanza for each new code type.
  7. In the last code module stanza, make sure each line except the last contains a comma at the end.

    For example:

    -- **** ADDRTYPE **** tCode(’L’, ’ADDRTYPE’, ’ADDRESS TYPE’), tCode(’V’, ’H’, ’HOME’), tCode(’V’, ’B’, ’BUSINESS’), tCode(’V’, ’M’, ’MAILING’)

  8. Save and close the file.
  9. Do one of the following:
To Customize Common Table Data for SQL Server
  1. Under the master index project in the Projects window, expand Database Scripts and then open the Code Lists file in the NetBeans editor.
  2. Scroll to the following line.

    begin

    The statements following this line must be customized.

  3. In the first code list stanza, change “module description” in the first line to a brief description of the code type.

    For example:

    -- **** PHONTYPE **** insert into @codelist values(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’)

  4. Create the entries for the module using the following syntax:

    insert into @codelist values(’V’, ’code’, ’code description’)

    where “code” is the processing code of the data element and “code description” is the description of the element as you want it to appear on the Enterprise Data Manager windows. For example:

    -- **** PHONTYPE **** insert into @codelist values(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’) insert into @codelist values(’V’, ’H’, ’HOME’) insert into @codelist values(’V’, ’C’, ’CELL’) insert into @codelist values(’V’, ’F’, ’FAX’) insert into @codelist values(’V’, ’O’, ’OFFICE’) insert into @codelist values(’V’, ’HB’, ’HOME BUSINESS’)

  5. Repeat the previous two steps for each code list type defined in the file.
  6. If you specified additional code list fields in the Object Definition file and the Enterprise Data Manager file, add a new stanza for each new code type.
  7. Save and close the file.
  8. Do one of the following: