Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 3.20.3.0.3

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

Enhancements

ID	Summary	Description	Included in Patch
POL-6169	Procedural Rounding	This enhancement adds logic that calculates the last calculation period in a span (e.g. calendar month) as the net difference between the total (1) span period premium and the (2) sum of all calculated periods in that span prior to the last period. This calculation ensures that the summed premium for all separate calculation periods adds up to the exact span premium, regardless of how the periods are broken down and whether the respective premiums end in odd or even numbers. With this enhancements two attributes are added to policy calculation period, pcp span start date and pcp span end date. Generate Policy Calculation Period is modified to set PCP span start date and end dates to policy calculation period start and end date before any split a) by the system or b) within dynamic logic. PCPs are (re) generated through a number of operations/activities. The concept of pcp span dates applies irrespective of the operation/activity through which the PCPs are generated. {color} Additional step is added to Calculate Premium process to reconcile the last pcp split. Note When using non-prorate function with adjustment and surcharge reconciliation must be done in the dynamic logic. See dynamic logic signature for details.

Summary

Description

Included in Patch

POL-6169

Procedural Rounding

This enhancement adds logic that calculates the last calculation period in a span (e.g. calendar month) as the net difference between the total (1) span period premium and the (2) sum of all calculated periods in that span prior to the last period. This calculation ensures that the summed premium for all separate calculation periods adds up to the exact span premium, regardless of how the periods are broken down and whether the respective premiums end in odd or even numbers.

With this enhancements two attributes are added to policy calculation period, pcp span start date and pcp span end date.

Generate Policy Calculation Period is modified to set PCP span start date and end dates to policy calculation period start and end date before any split a) by the system or b) within dynamic logic.

PCPs are (re) generated through a number of operations/activities. The concept of pcp span dates applies irrespective of the operation/activity through which the PCPs are generated. {color}

Additional step is added to Calculate Premium process to reconcile the last pcp split.

Note: When using non-prorate function with adjustment and surcharge reconciliation must be done in the dynamic logic. See dynamic logic signature for details.

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

Ref	Action	Subject	Description
POL-6169			For all the existing policy calculation periods, if there exists a contract period that spans over policy calculation period start date and end date then the contract start and end date are copied to policy calculation period span dates otherwise the policy calculation period start and end dates are copied to policy calculation period span start date and policy calculation period span end date respectively.

Ref

Action

Subject

Description

POL-6169

For all the existing policy calculation periods, if there exists a contract period that spans over policy calculation period start date and end date then the contract start and end date are copied to policy calculation period span dates otherwise the policy calculation period start and end dates are copied to policy calculation period span start date and policy calculation period span end date respectively.

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
32323892	3-24704227441	POL-7064	BP	JET UI - Policies details page show different enrollment start date
Description:	When the timezone is in GMT(negative) values, Policies details page show different enrollment start date in JET UI.
Resolution:	The start date field in Policies page Enrollment section shows the date in sync with DB/ADF screen values
32343015	3-24690688341	POL-7075	BP	Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist
Description:	When input date to calculate premium activity is 4th Dec, the system only looks at the first collection setting. However second collection setting with start date 5th Dec should be looked at for further period generation as there is collection method with calculation date offset of -1 associated with this collection setting.
Resolution:	Calculate premium activity now selects a valid collection setting when multiple collection settings with collection method exist.
32344226	3-24455989661	POL-7079	BP	Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date.
Description:	The pay date of all PCPs generated by sample invoice API must be set to system date automatically.
Resolution:	The pay date is now correctly set for all PCPs generated by sample invoice API.
32312638	3-24777871611	POL-7045		Default sort is not working correctly under billing accounts tab in group client page
Description:	When user clicks on billing accounts the corresponding billing account details are not populated correctly in group client pages.
Resolution:	Now user is able to get the billing account details correctly based upon the selection. This issue is now resolved because of the default sort functionality working properly.

BugDB

Internal

Summary

32323892

3-24704227441

POL-7064

JET UI - Policies details page show different enrollment start date

Description:

When the timezone is in GMT(negative) values, Policies details page show different enrollment start date in JET UI.

Resolution:

The start date field in Policies page Enrollment section shows the date in sync with DB/ADF screen values

32343015

3-24690688341

POL-7075

Calculate premium activity fails to select valid collection setting when multiple collection settings with collection method exist

Description:

When input date to calculate premium activity is 4th Dec, the system only looks at the first collection setting. However second collection setting with start date 5th Dec should be looked at for further period generation as there is collection method with calculation date offset of -1 associated with this collection setting.

Resolution:

Calculate premium activity now selects a valid collection setting when multiple collection settings with collection method exist.

32344226

3-24455989661

POL-7079

Sample invoice API is not setting the pay date of the PCPs generated as part of its process to system date.

Description:

The pay date of all PCPs generated by sample invoice API must be set to system date automatically.

Resolution:

The pay date is now correctly set for all PCPs generated by sample invoice API.

32312638

3-24777871611

POL-7045

Default sort is not working correctly under billing accounts tab in group client page

Description:

When user clicks on billing accounts the corresponding billing account details are not populated correctly in group client pages.

Resolution:

Now user is able to get the billing account details correctly based upon the selection. This issue is now resolved because of the default sort functionality working properly.

Issues that were backported in previous Release / Patch

No backports.