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

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)

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

Related Topics

Master Index Development Process Overview

The Master 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

Creating a Master Index Application

Step 1: Create a Project and Start the Wizard

Step 2: Name the Master Index Application

Step 3: Define Source Systems

Step 4: Define the Deployment Environment

Step 5: Define Parent and Child Objects

Step 6: Define the Fields for Each Object

Step 7: Generate the Project Files

Step 8: Review the Configuration Files

Master Index Wizard Field Properties and Name Restrictions

Master Index Wizard Field Name Restrictions

Master Index Wizard General Field Properties

Master Index Wizard MIDM Field Properties

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

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

To Create 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

Master Index Database Structure

Designing the Master Index Database

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

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

Step 9: Specify a Starting EUID for a Master Index

Dropping Master Index Database Tables

To Delete Database Tables

Defining the Database Connection Pools

Step 1: Add the MySQL or Oracle Driver to the Application Server

Step 2: Create two JDBC Connection Pools

Step 3: Create the JDBC Resources

Using the JMS JCA Wizard

Using the JAXB Wizard and Code-Seeder Pallete

Step 5: Define Master Index Code Lists

This topic was modified for Java CAPS 6 update 1.

Note - MySQL is only supported in Java CAPS 6 Update 1.

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 incodelist.sql (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.

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 MySQL
  1. Do one of the following:
    • Under the master index project in the Projects window, expand Database Scripts and then open codelist.sql in the NetBeans editor.
    • On your computer, navigate to project_home/src/DatabaseScript, where project_home is the location of the master index project files. Open codelist.sql in a text editor.
  2. Scroll to the first line that begins with “— **** “.

    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 tCodeList values(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’);
  4. Create the entries for that module using the following syntax:
    insert into tCodeList 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 Master Index Data Manager windows. For example:

    -- ****         PHONTYPE   ****
    insert into tCodeList values(’L’, ’PHONTYPE’, ’TELEPHONE TYPE’);
    insert into tCodeList values(’V’, ’H’, ’HOME’);
    insert into tCodeList values(’V’, ’C’, ’CELL’);
    insert into tCodeList values(’V’, ’F’, ’FAX’);
    insert into tCodeList values(’V’, ’O’, ’OFFICE’);
    insert into tCodeList 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 object.xml and midm.xml after the database scripts were generated, add a new stanza for each new code type.
  7. Save and close the file.
  8. Do one of the following:
To Customize Common Table Data for Oracle
  1. Do one of the following:
    • Under the master index project in the Projects window, expand Database Scripts and then open codelist.sql in the NetBeans editor.
    • On your computer, navigate to project_home/src/DatabaseScript, where project_home is the location of the master index project files. Open codelist.sql in a text 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 Master Index 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 object.xml and midm.xml 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. Do one of the following:
    • Under the master index project in the Projects window, expand Database Scripts and then open codelist.sql in the NetBeans editor.
    • On your computer, navigate to project_home/src/DatabaseScript, where project_home is the location of the master index project files. Open codelist.sql in a text 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 Master Index 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 object.xml and midm.xml, add a new stanza for each new code type.
  7. Save and close the file.
  8. Do one of the following: