Overview Seed Data
Types of Seed Data
Generic Seed Data
Seed data is maintained by Oracle. It is delivered as part of a release and may be updated by software upgrades. In general, customers should not change this data (see the Restrictions on using Seed Data section below).
Localization Seed Data
This category covers specific data that is required by localizations. The data is maintained by Oracle. Examples:
-
Flex Code Definitions for diagnosis and procedure codes
-
Specific messages for localizations.
Sample Data
Sample data is provided by Oracle to give a headstart during configuration. Install this data during a fresh install or upgrade. It is not modified during future upgrades (note that sample data will only be loaded if the target table has no rows in it). To load sample data, adjust the appropriate parameter in the ohi_install.cfg configuration file. To not load sample data for a certain table, remove the unwanted file from the database/sample_data directory prior to running the install/upgrade process. Tables containing Sample Data include:
| Table Name | Remarks |
|---|---|
COD_FLEX_CODES_B/TL |
|
PAS_PRODUCT_LINES_B/TL |
|
PAS_FUNDING_ARRANGEMENTS_B/TL |
|
CLA_DIAGNOSIS_TYPES_B/TL |
|
OHI_CLAIM_FORM_TYPES_B/TL |
Restrictions on Using Seed Data
Because Seed Data is maintained by Oracle, it may be modified or even deleted as part of an upgrade. Customers should therefore exercise caution when using seed data in their configuration by abiding these rules.
-
Do not remove (delete) Seed Data rows. A patch may re-insert the row.
-
Do not update columns, other than those indicated as updateble below.
-
Do not make references to rows that may be deleted by Oracle (see table below).
Violations of the rules above (especially rule 3) may lead to failures during the installation of upgrades.
The table below lists the Seed Data tables.
- Data
-
The table or logical entity
- Updatable columns
-
The customer may update the values in these columns. They will not be overwritten by upgrade scripts. Other columns should not be updated by the customer.
- Physical Delete
-
Upgrade scripts may delete this data. The customer should not create references to this data. Example: Do not use Oracle Health Insurance messages for dynamic checks.
| Data | Updatable columns | Physical Delete | Remarks |
|---|---|---|---|
Access Restrictions |
Yes |
Also deletes Access Restriction Grants referring to this row |
|
Access Restriction Grants |
Yes |
||
Access Roles |
No |
Four roles are seeded |
|
Activity Types |
ind_active |
No |
|
Boilerplate Texts |
Yes |
||
Claim Forms |
claim_form_type |
No |
|
Claim Form Types |
No |
||
Countries |
all _b columns |
No |
|
Country Regions |
No |
||
Coverage Labels |
label |
No |
|
Date Set Definition |
Yes |
||
Diagnosis Types |
No |
||
Dynamic Field Usages |
number_format_type |
No |
|
Dynamic Logic |
logic |
No |
|
Fields (+ dynamic logic) |
No |
||
Flex Code Sets (+ details) |
No |
||
Flex Code Systems |
No |
||
Floorplan |
description |
No |
|
Floorplan Tag Details |
ind_enabled |
No |
|
Funding Arrangements |
No |
||
Languages |
ind_default ind_installed |
No |
|
Line of Business |
descr |
No |
|
Messages |
ind_suppress_log_in_ui ind_suppress_log_in_ext ind_mark external_code |
Yes |
|
Process Fields |
step, claim_level |
No |
|
Product Lines |
No |
||
Resource |
Yes |
||
Resource Cache Settings |
Yes |
||
Resource Properties |
Yes |
||
Single Flex Code Definitions (+ usage) |
No |
||
Signature |
No |
||
Source Events |
Yes |
||
Target Events |
Yes |
||
Task Types |
Yes |
Customer is not allowed to change anything in base table |
|
Task Type Attributes |
value_char value_number value_datetime value_clob |
Yes |
|
Transaction Sources |
No |
||
Transaction Source Usages |
No |
||
Users |
No |
Two users will be seeded (system user + setup user) |
|
Widgets |
ind_enabled |
No |