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 diagnosis, procedures 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.

Table 1. List of Entities to Include in Configuration Migration
Top Level Item	Automatically Includes	Optional Excludes
access role	access restriction access restriction grant data access group	-
address type	-	-
authorization form	insurance type	-
basket	basket detail currency	-
boilerplate text	insurance type	-
country	-	dynamic logic
country region	country	-
currency	-	-
diagnosis group	diagnosis group detail	-
dynamic field usage (displayed as usage in the UI)	dynamic logic field flex code system message	-
dynamic logic	dynamic logic reference sheet message	reference sheet
flex code group	flex code detail	-
flex code system	dynamic logic field flex code flex code field usage flex code set detail flex code system message	-
insurable entity type	-	-
insurance type	insurable entity type supported insurable entity type	-
marital status type	-	-
message	-	-
message group	message group detail	message
pend reason	-	dynamic logic
prefix	-	-
process step	access restriction brand rule step callout rule event rule pend rule validation rule	authorization form diagnosis group dynamic logic message message group pend reason procedure group service type
procedure group	procedure group detail	-
product	brand currency funding arrangement product family product line	-
reference sheet	dynamic field usage ^[2] reference sheet line	-
service type	-	-
specialty	-	-
title	-	-
unfinalize reason	-	-

Table 2. Other Entities
Reference Data	Automatically Includes
diagnoses	access restriction diagnosis setting
procedures	access restriction procedure setting
providers	individual provider: country country region prefix provider (service address organization provider) provider specialty provider title rendering address service address specialty title organization provider: country country region provider (parent organization provider) provider specialty service address specialty

Including Diagnosis, Procedures, and Providers

Unless explicitly specified differently, the system excludes diagnosis, procedures, 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).

Table 3. Including Diagnosis, Procedures, and Providers
Reference Data	Automatically Includes
diagnoses	access restriction diagnosis setting
procedures	access restriction procedure setting
providers	individual provider: country country region dynamic logic (bank account validation) prefix provider (service address organization provider) provider specialty provider title rendering address service address specialty title provider identifier organization provider: country country region provider (parent organization provider) provider specialty provider identifier service address specialty

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.

1. JET Menu > Operations > Data Exchanges > Configuration Migration Sets

2. Each reference sheet relies on a single dynamic field usage record that serves as an integral part of the reference sheet by connecting the reference sheet to its definition. This dynamic field usage record is not visible in any user interface page, but is migrated as part of the reference sheet.