Release Notes for Oracle Health Insurance Product Definition Patch 4.23.2.0.1

This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.23.2.0.1.

Version compatibility: Oracle Health Insurance Product Definition Release 4.23.2.x is only compatible with other Oracle Health Insurance applications release version 4.23.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

ID Summary Patch

NXT-24066

WebLogic authentication implemented compliant with the Java Authorization and Authentication Service (JAAS) specification

This enhancement introduces support for the SAML 2.0 authentication mechanism in the Oracle Health Insurance. Additionally, a new JAR file named "CustomIdentityAsserter" has been created to accommodate the Basic Auth configuration.

Refer installation guide for further detail.

Documentation Links:
Installation Guide - Users and Authentication

4.23.1.0.4, 4.24.1.0.0

NXT-28449

Additional functionality for UI Form component

With this enhancement, the UI Form component now supports:

  • Editable list resources

  • Sort capabilities for tables configured within a Form

  • Conditionally hiding a sub-section

4.24.1.0.0

PRD-3875

Selective financial limit Carry-over

This enhancement introduces the ability to decide whether an out-of-pocket-maximum (OOPM) limit consumption counts towards year-end carryover. For example: * An OOPM consumption from a coinsurance or a copay do not count towards a carryover. * An OOPM consumption from a deductible does count towards a carryover.

A new indicator, exclude from carry over is introduced on the product-benefit-specification limit to help make this decision. The indicator is available for the build product process to define the carryover settings.

Documentation Links:
Configuration Guide - Product Benefit Specification Limit
Configuration Guide - Carryover Settings
Operations Guide - Build Product

4.23.1.0.3, 4.23.1.0.4, 4.24.1.0.0

Additional Upgrade Steps

Pre-Upgrade phase

  1. Execute the below SQL statements with user: OHI_PRODDEF_OWNER.

update databasechangelog set filename = '2024-04-08_PRD-4321_ADD_COLUMN.xml' where filename = '2024-02-27_PRD-4169_ADD_COLUMN.xml';

update databasechangelog set filename = '2024-04-08_PRD-4321_CARRY_OVER_SETTING_PRD.xml' where filename = '2024-02-27_PRD-4169_CARRY_OVER_SETTING_PRD.xml';

commit;

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

This section intentionally left blank.

Web Services

Ref Action Description

PRD-3875

Modified

Products Export

Exclude from carry over indicator is included in the product benefit specification limits

PRD-3875

Modified

Build Product

Carry Over Settings are used when product benefit specification limits are generated

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

NXT-28449

Modified

Policy Enrollment page

Form Table is made editable and sort is enabled in the form table for policy enrollment page with 'MEDICARE_ADVANTAGE' tag

PRD-3875

Modified

View Generated Product

Exclude from carry over indicator is visible in the product benefit specification limits

PRD-3875

Modified

Products Page

New section to define carry over settings

Breaking Changes

Ref Action Description

NXT-24066

Modified

Installation Configuration

Customers using the Basic Authentication mechanism must follow the installation guide to install the newly built JAR file, "CustomIdentityAsserter.jar," and configure the WebLogic security provider accordingly.

Bug Fixes

BugDB SR Internal Summary

36886418

3-36452370811

PRD-4468

Advanced search lov’s for dynamic fields are not loading in referencesheetlines

Description:

Not able to search using the LOV’s in the reference sheet lines page. When clicking in the LOV field an error occurs on the api/generic/flexcodes/search.

Resolution:

Proper results are displayed in the LOV for flexcodes based on diagnosis, procedures and providers, displays

36203977

3-34786906091

PRD-4065

Dynamic logic byte code is not loaded during server startup on non master nodes after invalidateall API is invoked

Description:

Dynamic logic byte code is expected to load at the startup of non-master nodes if the invalidateall API was invoked in master node but was not being observed.

Resolution:

Dynamic logic byte code is now loaded at the startup of non-master nodes if the invalidateall API was invoked in master node.

36506952

3-36314937451

PRD-4330

Parameter Alias Value Not Visible in JET when it has value 0

Description:

Parameter values of any type, when the parameter has a value of 0, are not displayed in JET

Resolution:

Parameter Alias value which has value set to 0 is visible in JET

36270608

PRD-4131

Unable to edit values in drawer when a field is configured as deeplink

Description:

It is not possible to edit resources which are configured as Deeplinks. For example in Individual providers, it is not possible to edit service address in rendering address tab. On click of edit button in service address drawer, its directly navigating back to individual providers page and not possible to edit/save

Resolution:

Edit works fine in Deeplink drawers now and also the values are saved properly on the resource configured as deeplink

36531977

3-36224017471

PRD-4259

Conversion Script For Floorplan Region Sets Changes

Description:

A data conversion was performed for all seeded floorplans that included the region in the payload. In the JSON payload for floorplans, the format "region → set1, set2, set3" was converted to an array format "set[]".However, the conversion script for customer floorplans (non-system specific) was not delivered as part of the major release.

Resolution:

Customer floorplans (payload) having region components with the format "region - set1, set2, set3" are converted to an array format "set[]". Note : It is also recommended to convert all the non system specific floorplans that are stored externally. This can either by done manually or by configuring the floorplans in the system before the upgrade.

36377448

PRD-4216

Save and Cancel shortcuts aren’t working for create Hierarchical Recursive pages

Description:

Save and Cancel shortcuts aren’t working for create Hierarchical Recursive pages

Resolution:

Save and Cancel shortcuts will work for create Hierarchical Recursive pages also now

36472068

3-36256248451

PRD-4263

Unable to search on service option in service definitions page

Description:

When opening the Service Definitions page in Jet is is not possible to search on the Service Option. Advanced search using service option is missing in service definition page.

Resolution:

Search on service option is possible in both quick/advance search in service definitions page

36820482

PRD-4479

Incorrect result shown in Boilerplates Table

Description:

The boilerplate table shows incorrect results after performing the 'ADD' and then 'CANCEL' actions simultaneously. This behavior is generic to other table-based pages.

Resolution:

Correct results are shown after performing the 'ADD' and then 'CANCEL' actions simultaneously in table-based pages

36757862

PRD-4428

Product Export Set not working, showing error

Description:

Navigate to product export set and click on create. There is an error in console

Resolution:

Product export set can be created without any errors

36946278

PRD-4557

BP 4.23.2: More button is not shown on double click of row or click of edit button

Description:

more button getting hidden when edit button is clicked

Resolution:

36718878

PRD-4411

Add new row is shown at last in table pages

Description:

Click Add new in table page. A new row is getting appended in the last visible row of the screen

Resolution:

Table component is modified with the below changes: 1) On click of Add button, a new row will be added to the top of the available rows. It is a sticky row to the table 2) Two new icons are added to a new row. Check icon would add the new row to the table and clicking on Cross icon would discard the new row. 3) User will have to click on Check icon and Save to persist the newly added data

36459371

3-36176430291

PRD-4252

Dynamic records ID should be returned as string in the API response

Description:

The ID of dynamic records of resources are returned as number (Long) in the API response, they should be returned as String.

Resolution:

The Dynamic records ID was transformed from Long to String in the API response

36672581

PRD-4402

QD status activities are not set to TE during system startup

Description:

Activities that were not processed and in 'QD' status before system down, are not setting up to status 'TE'

Resolution:

During system startup, activities which are in status 'QD' will be set to status 'TE'

Issues that were backported in previous Release / Patch

No backports.