Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.13
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.1.0.13.
| 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. |
| As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months. |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
37689176 |
3-39953000191 |
POL-16767 |
PCPs with forward billing are skipped for apply registrations |
Description: |
A change in Collection Setting can result in consecutive Policy Calculation Periods (based on the start- and end date of those Policy Calculation Periods) having different pay dates. In most cases the pay date of the latest Policy Calculation Period will also be later compared to the pay date of the earliest Policy Calculation Period. But, when the earliest Policy Calculation Period was not paid for in the first place, the pay date will be pushed according to the principle of forward billing. This could result in a scenario where the latest Policy Calculation Period (based on start date), has a pay date which is earlier compared to its predecessor. When a registration is processed, the system starts applying the registration to the Policy Calculation Period with the earliest pay date and skip the forward billed Policy Calculation Period. |
||
Resolution: |
When there are Policy Calculation Periods found without a corresponding Calculation Result, the system skips Process Registrations and adds the informative message POL-FL-PREG-004 to the activity. If there is no activity spawned, no informative message is added. |
||
38072404 |
3-40008658091 |
POL-17319 |
Apply Registrations functionality leaves gaps when regenerating Policy Calculation Periods for over a year. |
Description: |
Policy Collection Settings are time valid entities, which means that there can be multiple consecutive Policy Collection Settings with different settings. One of those settings is the Policy Calculation Period length and another one is the Offset, indicating at what moment the Policy Calculation Periods should be generated. As these variables have no restrictions, it can happen that the offset of a later Policy Collection Setting is bigger compared to the Policy Calculation Period length of the previous Policy Collection Setting. As a result, the system generates the periods for the second Policy Collection Setting before finishing with the last periods of the first Policy Collection Setting, causing time based gaps in the Calculation Results. |
||
Resolution: |
During Policy Calculation Period generation, the system checks if all the periods are generated for a specific Policy Collection Setting. If not, the system does not continue with generating the Policy Calculation Periods for any later Policy Collection Setting, those periods are only generated once the system finishes the first Policy Collection Setting. |
||
38273449 |
3-41471633021 |
POL-17561 |
Policy Calculation Period Unique Key violation thrown by Apply Registrations activity |
Description: |
The system throws a Policy Calculation Period Unique Key violation during Apply Registrations, when the policy has a suspension period that has a duration for over a year. |
||
Resolution: |
The system will not throw a Policy Calculation Period Unique Key violation and the registration will be applied. |
||