Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.21.1.0.3

Enhancements

ID Summary Description Included in Patch

POL-7252

Upgrade / Downgrade Data model

Waiting periods are common in the Australian Health Insurance market. Different periods apply to different health care services. When a waiting period applies for service X, it’s measured from the day that member was insured for an equal or better version of service X (known as a modality or clinical category). This check is based on the member’s plan history across funds.

To determine how one version of service X compares to the next, each services for which a member is insured has a score. This score can be specific to the member as certain benefits get better overtime.

When a member is still within a waiting period, he / she defaults to the lesser coverage. The lesser coverage is determined based on (at least) two dimensions: limits & parameters. These dimensions are applied separately so that the lesser coverage can be a combination of the current product’s copay and the previous product’s coverage limit.

In this context parameters are member liabilities in the form of flat amounts or percentages Suspensions are periods that the member is not insured without breaking the continuity of coverage. Previous funds send plan data to enable the current payer to accurately calculation length of cover for benefit limits and waiting periods. Waivers are member specific exemptions from a waiting period for a specific services.

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

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

32808859

POL-7835

In policy details page, parameter field values are not rendered in UI.

Description:

In policy details page, Enrollment tab summary section did not render parameter field values in UI.

Resolution:

The policy with the enrollments, which have the parameter values associated to it. The parameter values can now be seen in the summary section in policy detail page.

32855767

POL-8095

Not able to filter the results in Lov’s based on anything else apart from code.

Description:

The user is not able to perform search for anything else apart from the code in the LOVs. . Steps - 1. Find an LOV which have multiple search criteria for the search. 2. Click on the gear icon beside the search icon on the LOV 3. Select any other option apart from code for search criteria 4. Try to search a result based on that field which should return a result. . Expected: The LOV should work properly and return proper search results based on the selected search criteria.

Resolution:

Now able to filter/search the results based on checkbox selected from advanced attribute (i.e gear icon)

32847537

3-25807956679

POL-8100

Scroll required between tabs to navigate to all tabs in a page without zooming out

Description:

Customer needs to display more than 7 tabs, but the screen cannot fit all of them. Since there is no option to scroll between tabs the only option is to zoom out to be able to see all the tabs

Resolution:

Now the scroll option is available for the tabs, so now without zooming out the user can navigate from one tab to another in case of more no. of tabs.

32868151

3-25842782931

POL-8112

BP

Totals are incorrect if aggregate function count is used when grouped by enrollment product code

Description:

When a policy has multiple policy group accounts and if all the group accounts have the same enrollment product and if all the group accounts belong to the same group client, then querying policyenrollments generic API by group client code and grouping by enrollment product code produces incorrect totals results. The root attribute totalResults is however correct.

Eg: GET /api/generic/policyenrollments?q=policy.policyGroupAccountList.groupAccount.groupClient.code.eq('GROUP_CLIENT_CODE').and.policy.lastVersion.eq(true)&totalResults=true&groupBy=policyEnrollmentProductList.groupAccountProduct.enrollmentProduct.code&aggregate=count():totals

Resolution:

Resolved the issue by counting distinct policy enrollments. The totals (and totalResults) are now displayed correctly if aggregate function count is used when grouped by enrollment product code.

32871678

POL-8116

BP

Parameter alias field values are not displayed for group policy.

Description:

In policy pages, Parameter alias field values are not displayed for group policy under parameter value tab of policy enrollment section.

Resolution:

In policy pages, parameter alias field values are being displayed based on enrollment product and group account product.

Issues that were backported in previous Release / Patch

No backports.