Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.8

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

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

Access restriction on ability overturn deny messages

This enhancement extends the message group access restriction check to include the deny message overturn indicator update on claims and claim lines

POL-15334

Additional Data Masking Functions

This enhancement introduces two new data masking functions:

Text hash with seed, preserve size
Number hash with seed, preserve size

Along with the new masking functions:

New fields are added to the list of allowed native fields that can be part of the masking process.
Additional tables/columns are now purged as part of the masking process.

Documentation Links:
Administration Guide - Data Transformation Process - Purge Data
Developer Guide - Data Masking Configuration Integration Point- Transformation Functions

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.

Breaking Changes

Ref Action Description

NXT-31519

Modified

ReferenceSheetLines

When querying ReferenceSheetLine using SearchBuilder in dynamic logic, ensure that the query parameters match the data types defined in the associated dynamic record definition of ReferenceSheet. Passing a mismatched data type such as a number for a character field may cause errors like "ORA-01722: invalid number".

Example:
If a dynamic record definition contains a flex code field usage someUsage defined as a character, the following is incorrect:

def someUsage = 4
def search = new SearchBuilder(ReferenceSheetLine.class)
    .join("someReferenceSheet")
    .by("someUsage")
    .eq(someUsage)
    .execute();

The correct way to query someUsage is to pass the value as a String, as shown below:

def someUsage = "4"
def search = new SearchBuilder(ReferenceSheetLine.class)
    .join("someReferenceSheet")
    .by("someUsage")
    .eq(someUsage)
    .execute();

Bug Fixes

BugDB

SR

Internal

Summary

37921060

NXT-31563

Attributes, Segments, More sections retain previous search results in Accounting details page

Description:

In the claims accounting details page, when a search is performed without closing the previous search results, the Attributes, Segments and More sections are not refreshed. These fields retain the previous search results.

Resolution:

All fields are now refreshed after a search in Accounting details page.

37887138

NXT-31491

Generateaccountingmessage integration point populates reversal as false for null reversal accounting details

Description:

Reversal indicator is optional for accounting details. But the generate accounting message operation does not reflect that the reversal indicator could be empty.

Resolution:

Accounting details are now grouped by generateaccountingmessage integration point based on reversal being true or false or null. When the reversal indicator is null, the response item does not display the reversal field.

38021505

NXT-31742

Copy feature is missing for reference sheet lines

Description:

It is not possible to copy reference sheet lines as copy button is not visible in UI

Resolution:

Reference sheet lines table has the copy button enabled.

37898397

3-40602279631

NXT-31519

Querying ReferenceSheetLine in dynamic logic using SearchBuilder with mismatched parameter types causes ORA-01722 error

Description:

Querying ReferenceSheetLine using SearchBuilder in dynamic logic fails with "ORA-01722: invalid number" error when query parameters have mismatched data types. For example, providing a numeric value for a character type field defined in the dynamic record definition of ReferenceSheet causes this issue.

Resolution:

The query is generated based on the data type defined in the dynamic record definition of ReferenceSheet, not from the query parameter type. This works as expected only when the parameter type matches the defined field type. Refer to the "Breaking Changes" section for more details.

37912343

NXT-31543

Mandatory multivalued dynamic fields create extra row that prevents saving data.

Description:

If a floorplan has mandatory multi-valued dynamic fields, populating these fields create new empty rows. This leads to error on saving.

Resolution:

The validation for the newly created rows in multi value fields will only be performed if data is present.

37870625

3-40388321491

NXT-31460

No resolve link for pend reasons under Claims summary section if there are more than two pend reasons

Description:

The resolve link is displayed only for the first two pend reasons. If there are more pend reasons, they are displayed in 'See more' section but these do not have resolve link on them.

Resolution:

All the pend reasons are displayed in Claims summary section with an option to 'Resolve' pend. Additionally, Claim Line Summary section is modified as:
1) Summary Title gets ClaimLine Sequence Number
2) All messages and pends are now displayed in the drawer.
3) Resolved pends are displayed and marked as "Resolved" with the corresponding links disabled.
4) New section titles - Pend Reasons and Messages have been added to the drawer .

37832385

3-40369237351

NXT-31414

Claimline not highlighted for a finalized claim when 'details Inline' toggle is off

Description:

On clicking a claimline or on 'More' link for the claim line on a finalized claim , the claimline is not highlighted if 'details Inline' toggle is off.

Resolution:

Claimline is highlighted when the claim status is "finalized" and 'details Inline' toggle is off

38025524

NXT-31749

Multiple restart links appear in the UI when a large claim with unresolved subclaim pend reasons is submitted more than once.

Description:

If a large claim submit fails due to unresolved pend reasons on the subclaims, clicking restart link without resolving the pend reasons leads to creation of new activities that fails again and in turn displays new restart links. The system encounters Array index out of range error when processing these new activities.

Resolution:

It is now not possible to submit a large claim if a prior submit is in process or errored. This ensures that the ongoing activity is completed before a new submit can be triggered. Now, only one restart link is displayed in the user interface allowing to recover the failed activity.

38083208

NXT-31832

End date of a reference sheet line cannot be cleared using PUT on referencesheetlines API

Description:

Clearing end date of a reference sheet line using PUT gives success response, but does not update the end date.

Resolution:

End date can be updated to "" correctly now.

37954216

NXT-31644

An incorrect display name appears in the coverages section of the claim benefits tab

Description:

In the Claim Benefits > Coverages section, the display name is incorrectly sourced from Claim Line Coverage instead of Coverage Label

Resolution:

Display name is now shown correctly in the Coverages section of the claim benefits tab.

37987685

NXT-31697

Boilerplate text is displayed in advanced search of global activities page

Description:

Boilerplate text is displayed instead of label for creation date in advance search of global activities page.

Resolution:

Translations are done and labels are properly displayed for creation date in advance search

37957065

NXT-31648

Flexcodes as label do not work while using displayLabel for dynamic record fields

Description:

The fields from dynamic record which are configured as labels are displayed correctly when value is provided. But on adding displayLabel attribute with specific value details, the labels disappear.

Resolution:

Labels are now displayed correctly when configured for flex codes in dynamic record fields with displayLabel attribute

37984578

NXT-31695

UserJET property should expose userid, login name, display name, last login timestamp and defaultCountry information

Description:

userJET property exposes only displayName and id fields.

Resolution:

userJET property now exposes the user id, login name, display name, last login timestamp and defaultCountry of the logged-in user

38098916

NXT-31875

Claims CTR version - Benefit and pricing sections are not loading

Description:

When we change the version to any CTR version from working copy, and try to navigate to benefits or pricing section, the respective section loads but gets re-directed to claim detail page

Resolution:

Benefit and pricing sections are displayed in CTR claims version

37957233

NXT-31651

Boilerplate text code is being shown instead of the text value for dynamic records page

Description:

Boilerplate text code is being shown instead of the text value in detail page, configured for dynamic records. This issue occurs when a custom boilerplate is added as a title in floorplan tile

Resolution:

Boilerplate translations are done and proper text is displayed in UI

37894274

NXT-31514

Referencesheetline query API gives incorrect results when the same record field name is used in multiple reference sheets

Description:

Referencesheetline query API returns results from all the reference sheets which has the field usage name as passed in the query, where only the results from the resource mentioned in the URL are expected.

Resolution:

Referencesheetlines query api now works fine
* Usage name validation is done on all clauses in the query to check if usage name exists in OHI
* Search works fine now and returns only the results that are applicable for the resource mentioned in the endpoint.

Issues that were backported in previous Release / Patch

No backports.