Creating a Migration Set
Configuration Migration Sets
Configuration Migration Sets are assembled through a dedicated user interface page [1].
This page allows the user to select the top level migration items that should be included in the set. It also provides the option to exclude dependent items from the top-level migration items.
Unless explicitly specified differently, the system excludes agents, brokers and providers from the migration set. These objects have their own data exchanges.
Including Configuration Items
Configuration rules in Oracle Health Insurance are hierarchical in nature; complex configuration rules are a composite of more basic configuration rules. For example, a process step is a composite of any combination of callout-, event-, pend- and validation rules. In turn, the pend rule is a composite of a dynamic logic condition and a message (and more) as well.
To assist the user in assembling a migration payload, the migration function automatically determines what other configuration is required to successfully install the selected configuration item on the target environment.
The page offers the option to either create a full migration set or to include only a user-defined selection of the available configuration items in the migration set.
By default the page suggests to create a full migration set.
Switching the Full Migration Set?
toggle, opens the Configuration Items section at the bottom of the page.
This section lists the the items that are available for migration.
For each available configuration item the system supports to include all or just a selection of records for a particular top level configuration item. The 'Remove All From Set' option removes all the records for this configuration item from the migration set.
Selecting the 'Select Specific' radio-button enables the 'Select Specific' link to a window where the user can select one or more occurrences of that top-level item.
Below is the list of configuration items that can be included in a configuration migration data set. Each entry mentions which dependent items are auto-included and which dependent items can be excluded as an option.
Top-Level Item | Automatically Includes | Optional Excludes |
---|---|---|
access role |
access restriction |
- |
activity type |
dynamic field usage [2]. |
- |
address type |
- |
- |
add-on |
add-on detail |
product |
boilerplate text |
- |
- |
brand |
- |
- |
bulk update definition |
- |
dynamic logic |
business event definition |
- |
- |
notification definition |
business event definition |
dynamic logic |
business event rule |
business event definition |
dynamic logic |
calculation period |
- |
- |
callout rule |
- |
dynamic logic |
capitation contract |
- |
- |
change event rule |
- |
dynamic logic |
collection method |
- |
- |
connector configuration |
dynamic logic |
dynamic logic |
country |
bank account validation |
dynamic logic |
country region |
country |
- |
currency |
- |
- |
covered service tier |
- |
- |
dynamic field usage (displayed as usage in the UI) |
dynamic logic |
- |
dynamic logic |
dynamic logic reference sheet |
reference sheet |
enrollment product |
adjustment rule |
add-on |
enrollment product type |
enrollment product category |
- |
enrollment type |
- |
- |
enrollment response definition |
- |
dynamic logic |
exchange rate |
currency |
- |
excluded attribute |
- |
- |
fee definition |
- |
dynamic logic |
fee schedule |
currency |
dynamic logic |
flex code group |
flex code detail |
- |
flex code system |
dynamic logic |
flex code group |
floor plan |
- |
|
gender identity |
- |
|
group client |
add-on |
collection method |
identifier type |
access restriction |
- |
insurable class |
- |
- |
insurable entity type |
- |
- |
insurance type |
insurable entity type |
- |
line of business |
access restriction |
- |
macro definition |
- |
dynamic logic |
marital status type |
- |
- |
message |
- |
- |
message group |
message group detail |
message |
never in force reason |
- |
- |
output definition |
- |
dynamic logic |
parameter alias |
- |
- |
pend reason |
- |
- |
pend rule |
brand |
dynamic logic |
policy account definition |
- |
- |
policy account transaction type |
- |
- |
policy identifier type |
- |
- |
prefix |
- |
- |
premium schedule |
currency |
dynamic logic |
premium tier |
enrollment type |
|
process flow [3] |
access restriction |
|
product |
- |
- |
product covered service |
- |
- |
provider assignment type |
- |
- |
provider group |
provider group affiliation |
- |
reference sheet |
dynamic field usage [4] |
- |
relation link type |
- |
- |
schedule definition |
adjustment rule |
add-on |
specialty |
- |
- |
title |
- |
- |
user sequence [5] |
- |
- |
validation rule [6] |
- |
dynamic logic |
waiver reason |
- |
- |
widgets |
- |
- |
Including Agents, Brokers, and Providers
Unless explicitly specified differently, the system excludes agents, brokers, and providers from the migration set. These objects have their own data exchanges.
The user has the option to make the system also include these dependent reference items by checking one or more of the Include? checkboxes.
Including these reference data is restricted to records that are linked to the migrated configuration items. For example, if the source environment has 1000 providers, but only 600 of them are linked to the configuration items in the payload, then only the 600 linked providers are migrated.
This option applies across the entire migration set. For example, if the user opts to include providers, then all providers that are linked to one or more configuration items in the data set are included.
If a migration set includes linked reference data, it also automatically includes any setup configuration that is required; there is no option to exclude the supporting configuration. For example, if a provider has a specialty (which is at itself a top level item) that has not been explicitly added to the migration set, then the configuration migration function will still add the specialty (to ensure a successful migration for that provider).
Reference Data | Automatically Includes |
---|---|
agents |
agent address |
brokers |
broker address |
providers |
individual provider:
organization provider:
|
Optional Excludes
Configuration rules in Policies are hierarchical in nature; complex configuration rules are a composite of more basic configuration rules. For example, pend rule is a composite of dynamic logic and message group (and more) as well.
To assist the user in assembling a migration payload, the migration function automatically determines what other configuration is required to successfully install the selected configuration item on the target environment. The exclude options allow the user to carve out configuration records from that automatic inclusion. Consider the following example to clarify.
Enrollment product A refers to premium schedule B. In this context, premium schedule B is a dependent item to enrollment product A. If enrollment product A is selected for migration, the user has the option to include the referenced premium schedule as part of that migration as well.
Because an enrollment product is also a top-level item, the user can alternatively choose to migrate enrollment product A without migrating premium schedules as well. This alternate approach requires that premium schedule B is already present on the target environment. This allows the user to have separate configuration tracks, for example, the updates to the enrollment product using premium schedule B can be migrated before migrating the updates to premium schedules itself.
Dynamic Field and Record Usages
Configuration items can be extended with dynamic fields and records. If an extended item is included in the payload, the dynamic field and record values and the related dynamic field usages are automatically included as well. The target environment requires the dynamic field usages in order to know where it can find and update the dynamic field values.
Intended Usage
The intended user for this functionality is the configuration expert, that is the same user that has made the configuration changes. This is the person who knows which changes are ready for migration, and which are not.
Creating and saving a migration set in this page does not make the migration set available for other environments to import; this is a separate step described in Building a Configuration Migration Set.
The system determines the items in the configuration migration set at the moment of creating or updating that set.
It does not automatically include or remove configuration items that were added to or deleted from the system after the creation or update of the set.
It requires an update of the set to include (or remove) these configuration items. The # Items in the configuration migration set is the number of items that the system detected during the creation or latest update of the set.
|