Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.20.3.0.4

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

Enhancements

No enhancements.

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

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
32204315		NXT-21595	BP	SELECT_REPROCESSCLAIMS activity completes successfully, but the notification received on the data file notification end point has status as "Failure"
Description:	Even though the "SELECT_REPROCESSCLAIMS" activity completes successfully, the notification received on data file notification end point has "Failure" status.
Resolution:	When the activity "SELECT_REPROCESSCLAIMS" completes, the status in the data file notification now correctly reflects the status of the activity. With this bug fix, the order of the links in the data file notification has changed.
32353024	3-24806375171	NXT-21819	BP	Claims IP to fetch procedures for procedure groups not working correctly
Description:	Claims IP to fetch procedures for procedure groups not working correctly when procedure group code has leading zero. Steps to reproduce are: 1.Setup a Procedure 2.Setup a Procedure GROUP (code should have leading zero, ex: 054) 3.Add the procedure (created in step 1) to the procedure group (created in step 2) 4.Run the procedure group details IP. The one with leading zero always returns '204 - No Content', though there is associated procedure/s in the system.
Resolution:	Claims IP to fetch procedures for given procedure groups (with leading zero) now work correctly
32383996	3-24611017191	NXT-21850	BP	Dynamic Records are not rendered in the UI when they are configured as tab resource.
Description:	Dynamic records are not rendered in the UI when Dynamic fields are configured in the region and Dynamic record as tab resource.
Resolution:	Changes were made in the request header of the API call to show Dynamic Records.
32243540	3-24626119191	NXT-21686	BP	An error is coming when user tries to save the LOV value without selecting from the search results
Description:	The error is coming when user try to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved.
Resolution:	If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV.
32374109	3-24807818401	NXT-21846		Contracted Providers IP not working correctly
Description:	The correct OhiContext (and hence correct Locale) is not used in the contracted providers IP which leads to the default language being 'en' instead of 'es'. This is a coding bug and needs to be fixed.
Resolution:	The OhiContext is now using the default locale that is set in ohi_laguages.
32384250	3-24565719851	NXT-21851		For Provider Hierarchy, GET requests do not return all attributes
Description:	When using the generic API on organization providers, depending on the display order of providers, the service addresses are shown or not shown for the last provider.
Resolution:	For provider hierarchy GET request, service addresses are now shown in all cases.

BugDB

Internal

Summary

32204315

NXT-21595

SELECT_REPROCESSCLAIMS activity completes successfully, but the notification received on the data file notification end point has status as "Failure"

Description:

Even though the "SELECT_REPROCESSCLAIMS" activity completes successfully, the notification received on data file notification end point has "Failure" status.

Resolution:

When the activity "SELECT_REPROCESSCLAIMS" completes, the status in the data file notification now correctly reflects the status of the activity. With this bug fix, the order of the links in the data file notification has changed.

32353024

3-24806375171

NXT-21819

Claims IP to fetch procedures for procedure groups not working correctly

Description:

Claims IP to fetch procedures for procedure groups not working correctly when procedure group code has leading zero. Steps to reproduce are:
1.Setup a Procedure
2.Setup a Procedure GROUP (code should have leading zero, ex: 054)
3.Add the procedure (created in step 1) to the procedure group (created in step 2)
4.Run the procedure group details IP.
The one with leading zero always returns '204 - No Content', though there is associated procedure/s in the system.

Resolution:

Claims IP to fetch procedures for given procedure groups (with leading zero) now work correctly

32383996

3-24611017191

NXT-21850

Dynamic Records are not rendered in the UI when they are configured as tab resource.

Description:

Dynamic records are not rendered in the UI when Dynamic fields are configured in the region and Dynamic record as tab resource.

Resolution:

Changes were made in the request header of the API call to show Dynamic Records.

32243540

3-24626119191

NXT-21686

An error is coming when user tries to save the LOV value without selecting from the search results

Description:

The error is coming when user try to save the LOV value without selecting from the search results. If the user doesn’t select any value, the value does not get saved.

Resolution:

If the user wants to select a value from an LOV, then they must enter the complete value of the LOV and press Enter key. This will pick the first value from the search results of LOV.

32374109

3-24807818401

NXT-21846

Contracted Providers IP not working correctly

Description:

The correct OhiContext (and hence correct Locale) is not used in the contracted providers IP which leads to the default language being 'en' instead of 'es'. This is a coding bug and needs to be fixed.

Resolution:

The OhiContext is now using the default locale that is set in ohi_laguages.

32384250

3-24565719851

NXT-21851

For Provider Hierarchy, GET requests do not return all attributes

Description:

When using the generic API on organization providers, depending on the display order of providers, the service addresses are shown or not shown for the last provider.

Resolution:

For provider hierarchy GET request, service addresses are now shown in all cases.

Issues that were backported in previous Release / Patch

No backports.