We Need A Better Way To Load Implementation Data/config
(Doc ID 2331005.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Health Insurance Claims Adjudication - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
There needs to be a better way to create/transfer/load implementation config/data.
During implementation the CMT (configuration migration tool) is the main source of data/config migration, but the CMT tool is not very reliable. There is a lot of data which cannot be selected, and the tool does not have a way to remove data from the target environment. In some cases it can take more time to load the data using the CMT than if it is done manually.
A proposed enhancement is to create an option in the system which allows users to CRUD (create, read, update, delete) any data of the database through REST IPs. Some objects have the option to CRUD data thought an IP, for example, FlexCodes, Providers, Procedures, but others do not have this option, for example, table usage, dynR, dynL, and others. There could be a parameter in the application properties file which would enable the application into a CONFIG mode, or something like it.
This would enable loading of all our configs thought scripts. There would be a single place to hold the config, would be much easier to create new environments. Having a version control over these scripts, the scripts could be treated as a deliverable to the customer.
Continuing to use CMT requires more time to create a deliverable, implement it and/or update it.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document