Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.26.1.0.1
This document contains the release notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.26.1.0.1.
| Version compatibility: Oracle Health Insurance Enterprise Policy Administration Release 4.26.1.x is only compatible with other Oracle Health Insurance applications release version 4.26.1.x unless explicitly stated otherwise. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
POL-19010 |
Extensible Waiver Reasons With this enhancement it is now possible to configure non time valid dynamic fields for Waiver Reasons |
4.25.1.0.23 |
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 ofohi_install.cfg.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto 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:
-
Open a command window and browse to
<OHI_ROOT>/util/install. -
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
Web Services
| Ref | Action | Description |
|---|---|---|
POL-19121 |
Modified |
Data Transfer IP Introduced an optional attribute |
Breaking Changes
| Ref | Action | Description |
|---|---|---|
POL-19121 |
Modified |
Data Transfer IP If an integration relies on the previous 200 MB export file limit, it must explicitly provide |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
39943793 |
POL-19121 |
Improved performance for large data transfer exports with configurable file sizing |
|
Description: |
Data transfer IP uses a 200 MB file size value to DBMS_CLOUD.EXPORT_DATA, which could severely degrade performance for large exports. |
||
Resolution: |
Data transfer IP supports the optional maxFileSize attribute for CSV, JSON, and XML exports in SaaS deployments. This attribute is not supported for on-premises deployments. When maxFileSize is not specified, exports use the default file size of 10 MB. The application displays OHI-IP-ORV-011 when maxFileSize is outside the supported range: “The value of maxFileSize must be between 10 MB and 1024 MB” It displays OHI-IP-ORV-012 when maxFileSize is specified for PARQUET exports: “maxFileSize is not allowed for dataTransferFormat PARQUET” |
||
40095123 |
4-0002666364 |
POL-19387 |
Incomplete premium calculation for invoice catch-up periods. |
Description: |
Premium is not calculated for the full duration of an invoice catch-up period when the period spans multiple months. |
||
Resolution: |
Policy calculation period generation includes all catch-up periods for invoice and sample invoice operations. This supports premium calculation for the full catch-up duration before the regular collection cycle begins. |
||
40011954 |
4-0003751096 |
POL-19213 |
Activity processing supports financial transaction identifiers of up to 19 digits. |
Description: |
Activity processing could fail when a financial transaction identifier exceeded the 14-digit limit used for related activity records. This could interrupt workflows such as daily billing. |
||
Resolution: |
Related activity identifiers now support up to 19 digits, allowing activity processing to continue when larger transaction identifiers are used. |
||
40089001 |
POL-19372 |
Prevent application startup stall caused by Coherence cache initialization |
|
Description: |
During application startup, the plan manager could remain blocked while accessing a shared cache. This could prevent a node from completing startup and processing cluster communication. |
||
Resolution: |
The application now loads the plan cache only when needed, preventing startup stalls and allowing the node to process messages from other nodes and complete initialization. |
||
39926962 |
POL-19109 |
Audit API should inherit the access restriction of its parent resource |
|
Description: |
Currently, Audit API resources have their own newly created access restriction instead of inheriting the access restriction of the corresponding resource. As a result, a user who already has access to a resource (for example, Policies) may still be unable to access that resource’s Audit API unless an additional Audit API-specific access restriction and grant are provided. The Audit API must work by default for users who are authorized to access the underlying resource. It should therefore use the same access restriction as its parent resource, rather than requiring a separate restriction. |
||
Resolution: |
Users with access to a resource can access that resource’s Audit API without additional grants. |
||
39895797 |
4-0003279914 |
POL-19064 |
Amount Parameter Value Floorplan Uses paramterAlias Title Property |
Description: |
The delivered Amount Parameter Value floorplan uses the title property paramterAlias instead of parameterAlias. Although the property name appears to be a typographical error, changing it to parameterAlias is causing existing parameter amount values to display incorrectly in Edit mode. |
||
Resolution: |
Fixed the display of Parameter Value properties and corrected the property name typo in the Number of Units, Percentage, Service Days, and Amount Parameter Value floorplans. Custom floorplans for these pages should also be updated to use the correct property name, "parameterAlias". |
||
39939452 |
POL-19117 |
Not Authorized error in persons Page |
|
Description: |
A user with the Persons Access Grant receives an authorization error when opening the Persons page. The page requests specialty data that the grant does not permit the user to access. |
||
Resolution: |
The Persons Access Grant now permits access to the specialty data that the Persons page requires. A user with this grant can open the Persons page without an authorization error. |
||
39959063 |
4-0003638382 |
POL-19138 |
Policy enrollment time valid multi value flex code values are not displayed against their respective start date and end date after collapse and re-expand in edit mode when sort is configured |
Description: |
When sort criteria is configured for a multi-value dynamic field, collapsing and re-expanding the policy enrollment in edit mode may cause the field columns to display out of the configured sort order |
||
Resolution: |
All columns of multi-value dynamic fields are correctly sorted based on the configured sort criteria after collapsing and re-expanding the member in edit mode. |
||
39962766 |
POL-19145 |
Enforce minimum 30-days retention period for policy operational data purge requests |
|
Description: |
Policy operational data purge requests accepted retention periods below 30 days. This could allow policies to be purged earlier than the required retention threshold. |
||
Resolution: |
Added validation to reject Day retention periods below 30 with POL-IP-PUPO-008 error message. |
||
40057888 |
4-0002849021 |
POL-19257 |
Base View Generation fails for Insurable Persons Base View |
Description: |
In certain environments, Base View Generation could fail when generating the non-PHI Base View for Insurable Persons. |
||
Resolution: |
Obsolete configuration information is removed, allowing Base View Generation to complete successfully. |
||
39953732 |
4-0003656939 |
POL-19131 |
File is not downloaded in Reference sheet lines page |
Description: |
Download option not working for Reference sheet lines. When clicking on Download option getting error and lines are not getting downloaded. |
||
Resolution: |
Able to download csv file in Reference sheet lines page. |
||
39913822 |
4-0003570908 |
POL-19095 |
IntegrationTransformation can remain ERRORED without spawning the next task |
Description: |
When a connector task fails and creation of its replacement also fails, processing may stop because no task is queued to continue the work. This can affect event aggregation, transformation, and republishing of failed messages. |
||
Resolution: |
Updated task recovery to requeue the existing task when replacement creation fails. Replacement creation runs in a separate transaction so its failure does not prevent recovery. The existing task is marked Pending and requeued within the error-handling transaction. |
||
40089655 |
POL-19375 |
DBMS_CLOUD CSV exports incorrectly escape JSON values causing column misalignment in excel |
|
Description: |
Operational reporting CSV exports generated through DBMS_CLOUD do not correctly quote and escape JSON-valued fields. As a result, commas within JSON are treated as CSV delimiters when opened in Excel. This splits one JSON value across multiple columns and misaligns data with its headers. The issue is observed only in cloud environments. |
||
Resolution: |
Updated OPERATIONAL_RPT_PKG to handle text containing commas, quotation marks, or line breaks correctly. This helps keep values in the right columns when the exported file is opened. |
||
39996654 |
4-0002548324 |
POL-19201 |
Automatic recovery can fail to identify the latest errored task |
Description: |
When an earlier task has a higher identifier than a more recently created task, automatic recovery can fail to identify and recover the latest errored task. |
||
Resolution: |
Retrieval of errored tasks is optimized and based on latest creation date. |
||
40052077 |
POL-19250 |
Add index on the date of birth column of relations table |
|
Description: |
Customer dynamic logic may contain queries that search for person records in the relations tables using date of birth along with other attributes. Due to the absence of an appropriate index, these queries can be expensive and may result in performance degradation. |
||
Resolution: |
Add the index on the date of birth column to improve query performance. |
||
40133850 |
4-0003995571 |
POL-19441 |
Dynamic Record Definition configured as tab under Attached Data renders incorrect records in UI |
Description: |
When opening a dynamic record tab, some records could be missing from the table even though the total record count was correct. This occurred when the table automatically arranged the records during loading, leaving the displayed list incomplete. The records remained available, and running a blank quick search made them visible again. |
||
Resolution: |
The table has been updated to refresh the displayed list after automatically arranging the records. This ensures all loaded records appear without requiring a quick search. Sorting and loading additional records as you scroll continue to work as before. |
||