Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.7

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

Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.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

No enhancements.

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. 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 .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

Ref Action Description

NXT-26797

Modified

ohi.processing.max.concurrentparentactivities.size

The default value is changed to 8

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

35392235

NXT-26931

BP

The flex code descriptor value should be shown in create as well as edit state

Description:

When a dynamic record with flex code as one of its property is configured as a subproperty for a LOV, the descriptor of the flexcode is not shown in the create state but is shown in the edit state when a value is selected for the LOV

Resolution:

The flex code descriptor value are shown in create as well as edit state in UI pages where it is configured

35341098

NXT-26864

BP

Same column name being assigned for multiple flex code usages

Description:

When multiple numeric columns of the flex code field usages were imported using the configuration migration routine, it was noticed that the same column name was being assigned to all the field usages leading to import failures.

Resolution:

Appropriately chosen unique column names are now assigned to the multiple numeric flex code field usages that are being imported using the configuration migration routine.

35302555

3-32742074681

NXT-26797

BP

ActivitySubmissionTask enqueued to AQ does not use the priority from the task type

Description:

When ActivitySubmissionTask is enqueued (if activities throttling is enabled) to AQ, the priority is set to 0 instead of using the priority (9) from the task type

Resolution:

When ActivitySubmissionTask is enqueued to AQ, the priority from the task type is used. The default value of the property ohi.processing.max.concurrentparentactivities.size is changed to 8. System spawned activities (eg: INTEGRATION_OUT_PROCESSING) are not throttled by default

35390874

NXT-26929

BP

Advanced search is not working in referencesheetlines page when the record definition contains flexcodesystem

Description:

Advanced search is not working in referencesheetlines page when the Record Definition that is used to create Referencesheet Contains flexcodesystem.

Resolution:

Advanced search is working fine with flexcodesystem in referencesheetlines page.

35340944

3-32824655691

NXT-26862

BP

Values entered in SVNTV type fields are not retained when record definition fields are also present

Description:

SVNTV fields are not retained when record definition fields are added to the resource.

Resolution:

User can now configure SVNTV fields when record definition fields are present. Also fields like claimed, allowed and covered amount are now shown in Claims screen

35386915

NXT-26924

BP

The Test Unit now accepts changes made in a Derivation Rule

Description:

The Test Unit now accepts changes made in a Derivation Rule

Resolution:

Security Context is set appropriately

Issues that were backported in previous Release / Patch

No backports.