Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.3

This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.23.1.0.3.

Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.1.x unless explicitly stated otherwise.

In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID	Summary	Patch
NXT-28569	Migration of credentials from OPSS to ohistore 4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore. Documentation Links: Developer Guide - Credentials Developer Guide - Keystores

Summary

Patch

NXT-28569

Migration of credentials from OPSS to ohistore

4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore.

Documentation Links:
Developer Guide - Credentials
Developer Guide - Keystores

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

Perform any pre-upgrade steps.
Stop all the managed nodes running the existing version of the application.
Perform any pre-undeploy steps.
Undeploy the existing version of the application.
Back up the database.
Perform any post-undeploy steps.
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
Run the Upgrade script:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. Run the upgrade by executing ./ohi-update.sh .
Make the required changes to the ohi properties file
Perform any post-upgrade steps
Start WebLogic application server
Deploy the Application
Perform any post-deploy steps

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up
post-upgrade: Released upgrade script has run.
post-deploy: New application is deployed and is up and running.

Note: This is only required while upgrading to 4.23.2 and migrating from opss/vault to ohistore.

Configure property "ohi.credential.migration.enabled" either in the database or property file and set the property value to "true". This property will allow the end user to access the endpoint to export the secrets i.e. keystore and credentialstore.

To disable exports of the keystore and Credentials, set this property "ohi.credential.migration.enabled" value to "false".

Configuration Properties

This section intentionally left blank.

Web Services

Ref	Action	Description
NXT-28569	Added	Export Keystores Export existing keystores
NXT-28569	Added	Export Credentials Export existing credentials

Ref

Action

Description

NXT-28569

Added

Export Keystores

Export existing keystores

NXT-28569

Added

Export Credentials

Export existing credentials

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	Summary
35964055	3-34674229901	NXT-28003	The description of the procedure code (if configured) is not displayed when the procedure code is selected from lookup
Description:	Configure the claim lines floorplan in a way so that a description can be displayed when a value of procedure code is selected. Click on the Lookup option for the procedure code. After the selection of a value, the user should be moved back to the claim lines page, where the selected value of the procedure code is displayed as expected, but the description field is not displayed.
Resolution:	The description of the procedure code (if configured) is displayed when the procedure code is selected from lookup.
36101397	3-35012024601	NXT-28260	Conditional population of fields are not working in create process even though objectstate is 'always'
Description:	In Claims - Payer page, add a new custom page (dynamic record) payer details. The conditional population of certain fields are not working during create but only in "Edit" even though "objectState": "always" is set. The data is showing correctly while viewing and during Edit but not during create.
Resolution:	Conditional display works for dynamic records in create mode (with object state set to "always")
36101381	3-35067781441	NXT-28259	Label component not working when it’s configured inside tab-results component
Description:	Configure a dynamic record as tab-region and try to configure the flex code value to show as a label. The label isn’t showing up in the tab.
Resolution:	Flex code value can be configured to be shown as a label in tab results in HRR page

BugDB

Internal

Summary

35964055

3-34674229901

NXT-28003

The description of the procedure code (if configured) is not displayed when the procedure code is selected from lookup

Description:

Configure the claim lines floorplan in a way so that a description can be displayed when a value of procedure code is selected. Click on the Lookup option for the procedure code. After the selection of a value, the user should be moved back to the claim lines page, where the selected value of the procedure code is displayed as expected, but the description field is not displayed.

Resolution:

The description of the procedure code (if configured) is displayed when the procedure code is selected from lookup.

36101397

3-35012024601

NXT-28260

Conditional population of fields are not working in create process even though objectstate is 'always'

Description:

In Claims - Payer page, add a new custom page (dynamic record) payer details. The conditional population of certain fields are not working during create but only in "Edit" even though "objectState": "always" is set. The data is showing correctly while viewing and during Edit but not during create.

Resolution:

Conditional display works for dynamic records in create mode (with object state set to "always")

36101381

3-35067781441

NXT-28259

Label component not working when it’s configured inside tab-results component

Description:

Configure a dynamic record as tab-region and try to configure the flex code value to show as a label. The label isn’t showing up in the tab.

Resolution:

Flex code value can be configured to be shown as a label in tab results in HRR page

Issues that were backported in previous Release / Patch

No backports.