Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.21.2.0.6

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

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

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

33763742

3-28317336971

NXT-24102

BP

Claim line limit section is not involved in choosing the limit to be applied

Description:

As per current behavior, claim line limit is only used to override the limit height of the applied limit(chosen by count towards limit or prod ben spec parameter). But it is expected that claim line limit by itself can determine the limit to be applied on the claim line.

Resolution:

When there aren’t any count toward limits configured, limits configured at claim line level are evaluated and out of those only one is selected based on product and cover withhold rule category comparison as mentioned below:

Product should be mentioned at claim line limit
Product mentioned at claim line and claim line limit should be same
If cover withhold rule category isn’t null then category mentioned on claim line limit should be same as category mentioned in cover withhold rule

First claim line limit which satisfies above comparison is returned. If there isn’t any matching claim line limit, following check happens again on list of configured claim line limits.

Product shouldn’t be mentioned at claim line limit
Cover withhold rule category mentioned at claim line limit should be same as category mentioned in cover withhold rule

First claim line limit which satisfies above comparison is returned.

33835432

3-28425351821

NXT-24211

BP

Purge job PURGE_TECHNICAL_DATA_DAILY is failing

Description:

'PURGE_TECHNICAL_DATA_DAILY' purge job fails with an invalid number exception when batch_id column of pri$fee_schedule_lines table holds alphanumeric value

Resolution:

Job compares batch_id against activity id. Explicitly converted activity id to character type to avoid conversion of batch_id to number.

Issues that were backported in previous Release / Patch

No backports.