Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.2

This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.2.

Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.23.1.x is only compatible with other Oracle Health Insurance applications release version 4.23.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-28569

Migration of credentials from OPSS to ohistore

4.23.2 Release does not support opss anymore hence two new endpoints have been developed to export existing keystore/credentials. This functionality can be used while upgrading to 4.23.2 and moving away from opss/vault to ohistore.

POL-12478

Exclude reference resources for generic GET operation

This enhancement introduces a new resource representation parameter excludereferenceresources. When set to true, it excludes the list and reference resources from the generic GET response.

Additionally, for the search requests originating from UI, excludereferenceresources is set to true, that is, to retrieve only the required details.

4.23.2.0.0

POL-14103

Ability to access PII in base views

By default, the base views exclude all columns and dynamic fields that contain Personally Identifiable Information (PII). This enhancement introduces a system property that overrides this behavior, so that PII data elements become available in base views. This feature enables customers to use base views to create reports that contain PII.

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

Additional Upgrade Steps for Installation

The following phases are defined:

  1. pre-upgrade: Application is still running

  2. pre-undeploy: Application is stopped, but not undeployed.

  3. post-undeploy: Application is undeployed. Database is backed up

  4. post-upgrade: Released upgrade script has run.

  5. post-deploy: New application is deployed and is up and running.

Stage: post-upgrade

Action: Applicable for SaaS deployments/AMS team: configure property "ohi.baseview.exclude.pii" in the property file and set the property value to "true". This property when set to false will allow the end user to access PII data in baseviews. In case SaaS customer wants to flip value of property then they need to raise ticket to AMS team.

Configuration Properties

Ref Action Description

POL-14103

Added

ohi.baseview.exclude.pii

This new boolean property controls whether Personally Identifiable Information (PII) is included in base views. By default, PII is excluded from base views. SaaS customers can change the value of this property by submitting a service request.

Web Services

Ref Action Description

NXT-28569

Added

Export Keystores

Export existing keystores

NXT-28569

Added

Export Credentials

Export existing credentials

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

35903498

3-33092865931

POL-13832

Group account not reflected correctly

Description:

When searching Policies by Person in ADF the Group Account does not always get reflected correctly.

Resolution:

The Group Account is reflected correctly in the View Person page now.

35694338

POL-13412

Policy Page: Member drawer - When edited any record and clicked on Save, the scroll bar and deeplink on the policy page freezes

Description:

  1. Open a policy record.

  2. Click on the Policyholder or Member deeplink.

  3. Click Edit on the member drawer.

  4. Make changes.

  5. Click on Save.

The drawer will be closed, and the scroll bar will stop working on the policy page. Also, the deeplink stopped working, so a few elements on the policy page are frozen. We have to click on another object navigation link and then return to the policy details page, and then it gets resolved.

Resolution:

When details are edited in the Member drawer and click on Save, the page does not freeze, and changes are saved.

35694346

POL-13413

Policies: Adding a new person in policyholder gives an error while saving.

Description:

  1. Click on Create Policies.

  2. Add a new person in Policyholder using deeplink.

  3. Click on Save.

The policy is not created but throws the error.

Resolution:

A new person can be created using the deeplink for the policyholder field on the create policies page.

35867312

3-34391377541

POL-13786

Registration is re-applied when using the /applyregistrations IP

Description:

When a registration is in Applied status but has a pay date later than the look-back date, the registration will be reapplied. The system tends to keep the policy calculation periods created during the initial registration application. As a result, when the registration is reapplied, it is applied to a new period instead of the one initially applied to.

Resolution:

The system will remove the policy calculation periods with the same pay date as the registration to ensure that the registration can be re-applied for the same period it was applied for initially.

35982985

3-34704151961

POL-13912

Deeplink of PremiumSchedule in on GroupAccountProducts page is throwing a blank screen

Description:

When deepLink for PremiumSchedule is enabled on the GroupAccountProducts page, the deeplink drawer opens with a blank screen. Instead, it should show the expected data in the drawer.

Resolution:

Enabling deeplink for PremiumSchedule works fine; the deeplink drawer opens with the expected data.

36028185

3-34828017531

POL-13989

JET policies- Empty policy is shown when version exceeding 51 is selected

Description:

Go to Policy version 50 → edit policy → submit policy → Policy should get version 51 but in JET UI it shows an empty policy

Resolution:

Empty policy is not shown when version exceeding 51 is selected. Also now in the policy version drop down latest 50 versions are shown

35963414

POL-13896

Dynamic Logic is not compiled at startup

Description:

Dynamic logic was not always recompiled at application startup.

Resolution:

Any dynamic logic with tec_byte_code as null will be compiled during the application startup, and tec_byte_code will be populated accordingly.

35811129

3-34053143361

POL-13709

Person level policy event with a reference to a non-existing policy ID is not removed after mutations are created

Description:

The orphan policy events (having a reference to a non-existing policy) were not removed after generating mutation, leading to the creation of unwanted financial transactions.

Resolution:

Added deletion logic to delete orphan policy events after the mutations are generated.

35917309

POL-13844

Unable to add Oradocs link in Policies Jet page policyenrollment

Description:

The external link icon is not displayed when configured in floorplans.

Resolution:

External link configured in floorplans is displayed in UI.

36093656

POL-14085

Unable to select Covered Service Tiers in Product Covered Services

Description:

On the Product Covered Services page, the drop-down for the covered services tier is not loading any values and also not displaying existing values.

Resolution:

Now, it is possible to select and view values for the covered services tier on Product Covered Services tier page.

35999715

3-34734720061

POL-13951

Premium calculation results in JET UI not displaying accurately when enrollment product is ended

Description:

In a retro termination scenario where premium calculation results have been reversed and not recreated, the premium view in JET UI incorrectly displays the reversed calculation results.

Resolution:

JET UI displays proper reversed calculation results in a retro-termination scenario where premium calculation results have been reversed and not recreated.

36020657

3-34751448551

POL-13980

PROCESS_REGISTRATIONS activity takes more than an hour to create child activities

Description:

PROCESS_REGISTRATIONS activity takes more than an hour to create child activities when the volume of policy mutations is high.

Resolution:

PROCESS_REGISTRATIONS activity will now take less time than before to create child activities when the volume of policy mutations is high.

35958806

POL-13883

Policy In IP matches the identifier but updates the policy code

Description:

The Policy In IP sometimes updates the code of an existing policy. Steps to reproduce: 1. Send in a policy request with an identifier as code (like an SSN-no) with an identifier type to add this identifier to the new policy. 2. Approve the policy (or submit in step 1) 3. Send in the same payload, and a new version is created, but the code is now updated to the value of the identifier (like the SSN-no).

Resolution:

When the identifier retrieves an existing policy in the Policy In IP, the code of that existing policy will not be updated.

Issues that were backported in previous Release / Patch

No backports.