Configuration Migration Tool/ User Interface Internal Key Issue
(Doc ID 2513107.1)
Last updated on FEBRUARY 18, 2020
Applies to:Oracle Health Insurance Claims Adjudication - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Two OHI environments can have objects out of sync because of changes in the source environment.
When CMT is used to sync between two OHI environments, objects can get out of sync.
If an object is copied with the OHI functionality and the code of the original record is changed instead of the copied record, the import of CMT will fail. This is not easy to solve for the user and this issue can easy occur.
Take an object (record) form OHI for example a procedure group.
The procedure group is already moved in the past to another environment.
On the source environment the procedure group is copied.
Instead of changing the copied record the mandatory code of the original record is copied.
Now there is an issue because if the new line is imported the code is already matching and the existing UUID and the existing configuration can get a new code (procedure group).
OHI should not allow the user to change the original instead of the copied record.
This is probably difficult to realize, but at least make sure the active object will in all situations be the copied line when a object (record) is copied in OHI. Preferably enforce or show the changes to be made on the copied record.
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