Release Notes for Oracle Health Insurance Enterprise Policy Administration Patch 4.23.2.0.10

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

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

Enhancements

ID	Summary	Patch
CPN-3079	Auto purge feature As data volume in Oracle Health Insurance applications continue to grow with the processing of more data, it becomes essential to manage the database efficiently. Oracle Health Insurance applications include various PL/SQL packages for purging processes. However, these processes currently require manual intervention by customer DBAs/AMS team to configure and schedule purge jobs during planned maintenance windows. To streamline this process and automate database maintenance, we are introducing an auto-purge job feature. This feature eliminates the need for manual scheduling of various purge jobs and ensures that data is regularly purged according to predefined criteria. As part of this enhancement, we have a introduced a new PL/SQL package ohi_auto_purge_pkg.purge_all and modified the following functionalities : The structure of the following procedures has been revised, introducing an optional input parameter p_commit_size to enhance flexibility and control over the purging process cla_data_purge_pkg.purge_data ohi_repl_purge_pkg.purge_data Log message purging is now integrated into the auto-purge feature, and as a result, the following HTTP API resources have been made read-only. logeventretentionperiods API loglevelretentionperiods API Purging of PHI logs is now integrated into the auto-purge feature. So, the property ohi.logging.phi.min.retentionperiod is removed The process now integrates purging of all datafile sets into the auto-purge system, eliminating the need for separate scheduled scavenging and purging of incident files. So, the property ohi.incident.datafileset.retentionperiod is removed Oracle recommends frequent and automatic purging of technical data and operational data using the auto-purge job feature. For example, customer DBA/AMS team (in SaaS) can set up auto purge through the use of a DBMS_SCHEDULER job. See the user guide for more details and for a sample SQL script that creates auto purge job using DBMS_SCHEDULER.create_job PL/SQL procedure. Note that the initial purge job might take longer if the volume of the data is very high (for example, if the system has two years of data to purge and if the retention days for technical data are set to 60 days). So, Oracle recommends the DBA/AMS team to set a higher retention period (for example, one year and 11 months) for the initial run (so only 30 days of data is purged in the very first run). The retention days can be reduced gradually until the historical data is purged. Documentation Links: Administration Guide - Purging Data from Technical Tables Administration Guide - Purging Data from Replication Technical Tables Administration Guide - Datafile Set Trace Files Retention Administration Guide - Auto Purge	4.23.1.0.8, 4.24.1.0.0
POL-12956	Purge data files In Oracle Health Insurance applications, data files generated during various activities (e.g., extract activity, financial messages activity and data files uploaded to initiate long-running operations) remain in the system even after they have been processed/consumed. Currently, there is no mechanism in place to automatically clean up these data files once they have been processed/consumed, leading to inefficiency of the database storage space. This enhancement aims to automate the cleanup process and optimize database storage space. To enable purging data files, we have introduced a new PL/SQL package ohi_purge_datafileset_pkg. Documentation Links: Administration Guide - Purging Data from Data File Sets	4.23.1.0.8, 4.24.1.0.0
POL-16476	Remove restrictions from registrations entity This enhancements removes the additional restrictions from the registration entity that were introduced as part of POL-15396 i.e. Payment registration with code type 'CARRYOVER', 'CARRYOVER_OFFSET' and 'REFUND_OFFSET' can neither be created, updated nor deleted Payment registrations with status 'Applied' cannot be created or deleted and update is not allowed on the fields 'type', 'status', and 'codeType' fields for such registrations	4.23.1.0.9
POL-9574	Populating elementId in activity messages (for technical errors) Activity messages have an elementId populated in almost all cases (except for global activities, where, for instance, a message is added, if a parameter is not passed on correctly). That way, it is possible to correlate an error to a policy.	4.23.1.0.8, 4.24.1.0.0

Summary

Patch

CPN-3079

Auto purge feature

As data volume in Oracle Health Insurance applications continue to grow with the processing of more data, it becomes essential to manage the database efficiently. Oracle Health Insurance applications include various PL/SQL packages for purging processes. However, these processes currently require manual intervention by customer DBAs/AMS team to configure and schedule purge jobs during planned maintenance windows.

To streamline this process and automate database maintenance, we are introducing an auto-purge job feature. This feature eliminates the need for manual scheduling of various purge jobs and ensures that data is regularly purged according to predefined criteria.

As part of this enhancement, we have a introduced a new PL/SQL package ohi_auto_purge_pkg.purge_all and modified the following functionalities :

The structure of the following procedures has been revised, introducing an optional input parameter p_commit_size to enhance flexibility and control over the purging process
- cla_data_purge_pkg.purge_data
- ohi_repl_purge_pkg.purge_data
Log message purging is now integrated into the auto-purge feature, and as a result, the following HTTP API resources have been made read-only.
- logeventretentionperiods API
- loglevelretentionperiods API
Purging of PHI logs is now integrated into the auto-purge feature. So, the property ohi.logging.phi.min.retentionperiod is removed
The process now integrates purging of all datafile sets into the auto-purge system, eliminating the need for separate scheduled scavenging and purging of incident files. So, the property ohi.incident.datafileset.retentionperiod is removed

Oracle recommends frequent and automatic purging of technical data and operational data using the auto-purge job feature. For example, customer DBA/AMS team (in SaaS) can set up auto purge through the use of a DBMS_SCHEDULER job. See the user guide for more details and for a sample SQL script that creates auto purge job using DBMS_SCHEDULER.create_job PL/SQL procedure.

Note that the initial purge job might take longer if the volume of the data is very high (for example, if the system has two years of data to purge and if the retention days for technical data are set to 60 days). So, Oracle recommends the DBA/AMS team to set a higher retention period (for example, one year and 11 months) for the initial run (so only 30 days of data is purged in the very first run). The retention days can be reduced gradually until the historical data is purged.

Documentation Links:
Administration Guide - Purging Data from Technical Tables
Administration Guide - Purging Data from Replication Technical Tables
Administration Guide - Datafile Set Trace Files Retention
Administration Guide - Auto Purge

4.23.1.0.8, 4.24.1.0.0

POL-12956

Purge data files

In Oracle Health Insurance applications, data files generated during various activities (e.g., extract activity, financial messages activity and data files uploaded to initiate long-running operations) remain in the system even after they have been processed/consumed. Currently, there is no mechanism in place to automatically clean up these data files once they have been processed/consumed, leading to inefficiency of the database storage space.

This enhancement aims to automate the cleanup process and optimize database storage space. To enable purging data files, we have introduced a new PL/SQL package ohi_purge_datafileset_pkg.

Documentation Links:
Administration Guide - Purging Data from Data File Sets

4.23.1.0.8, 4.24.1.0.0

POL-16476

Remove restrictions from registrations entity

This enhancements removes the additional restrictions from the registration entity that were introduced as part of POL-15396 i.e.

Payment registration with code type 'CARRYOVER', 'CARRYOVER_OFFSET' and 'REFUND_OFFSET' can neither be created, updated nor deleted
Payment registrations with status 'Applied' cannot be created or deleted and update is not allowed on the fields 'type', 'status', and 'codeType' fields for such registrations

4.23.1.0.9

POL-9574

Populating elementId in activity messages (for technical errors)

Activity messages have an elementId populated in almost all cases (except for global activities, where, for instance, a message is added, if a parameter is not passed on correctly). That way, it is possible to correlate an error to a policy.

4.23.1.0.8, 4.24.1.0.0

Configuration Properties

Ref	Action	Description
CPN-3079	Removed	ohi.logging.phi.min.retentionperiod Purging of logs is now integrated into the auto-purge feature. So, this property is removed. The default retention for PHI logs with the auto-purge function is 2560 days (7 years) and can be managed through the autopurgemetadata API
CPN-3079	Removed	ohi.incident.datafileset.retentionperiod Purging of all datafile sets is now integrated into the auto-purge system, hence, eliminating the need for separate scheduled scavenging and purging of incident files. So, this property is removed.

Ref

Action

Description

CPN-3079

Removed

ohi.logging.phi.min.retentionperiod

Purging of logs is now integrated into the auto-purge feature. So, this property is removed. The default retention for PHI logs with the auto-purge function is 2560 days (7 years) and can be managed through the autopurgemetadata API

CPN-3079

Removed

ohi.incident.datafileset.retentionperiod

Purging of all datafile sets is now integrated into the auto-purge system, hence, eliminating the need for separate scheduled scavenging and purging of incident files. So, this property is removed.

Web Services

Ref	Action	Description
CPN-3079	Added	autopurgemetadata API Added a new autopurgemetadata API
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

Ref

Action

Description

CPN-3079

Added

autopurgemetadata API

Added a new autopurgemetadata API

CPN-3079

Removed

loglevelretentionperiods API

loglevelretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

CPN-3079

Removed

logeventretentionperiods API

logeventretentionperiods API supports only GET operation. POST/PATCH/PUT/DELETE operations are not longer supported

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Breaking Changes

Ref	Action	Description
CPN-3079	Removed	loglevelretentionperiods API loglevelretentionperiods support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature
CPN-3079	Removed	logeventretentionperiods API logeventretentionperiods API support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature

Ref

Action

Description

CPN-3079

Removed

loglevelretentionperiods API

loglevelretentionperiods support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature

CPN-3079

Removed

logeventretentionperiods API

logeventretentionperiods API support only GET operation. POST/PATCH/PUT/DELETE operations are no longer supported. So, it is not possible to purge log messages based on a specific log level. Instead purging of logs (irrespective of the log level) is now integrated into the auto-purge feature

Bug Fixes

BugDB	SR	Internal	Summary
37231507	3-38581095771, 3-38556860431, 3-38933128751	POL-16187	Parent activity terminates or is marked as terminated (TE) prematurely, while its child activities are still under execution
Description:	While initializing one of the groups of activities, the parent activity is marked as 'TE' while the other groups (children) are still running.
Resolution:	If a group of activities fail to initialize, the system will automatically retry the initialization process up to a configurable maximum number of attempts. If all retries fail, the group of activities will be marked as Terminated (TE). This approach ensures that the parent activity remains active until all its child groups have been successfully processed, preventing premature termination
36547800	3-37468227341	POL-15064	Multiple issues while translating screens from English to Dutch
Description:	Translations not applied at several places when language is changed
Resolution:	Translation issues are fixed at few pages
37082021	3-37852540711	POL-15911	Global Activities page taking lot of time to retrieve results.
Description:	When a query is performed without any filters on the global activities page, it takes a lot of time to load the search results.
Resolution:	Updated the search criteria for the page to load results only when filters are applied.
37286658	3-37575580501	POL-16264	Field values are intermittently not being set when using the JET UI in version
Description:	Create dynamic fields, set a value for this field and save it. The updated value is not being saved properly.
Resolution:	Dynamic field values are updated properly using additional fields dialog
Backports:	4.23.1.0.9
37067536	3-36700304951	POL-15877	Processing of activities stuck with NPE on AggregateResumableActivityTask during node initialization
Description:	The Coherence service started processing activities too early, before the node was fully initialized, causing the ServiceLocator to initialize prematurely and resulting in a NullPointerException (NPE), which destabilized the entire application.
Resolution:	Delayed Coherence session creation until system initialization is complete, ensuring a stable environment for subsequent operations.
37287761	3-38222400721	POL-16265	Person details are not correctly copied with Policy In Patch integration point
Description:	Person details (like Assigned Providers, Contract Alignments, Person Covered Services etc.) were not correctly copied when using Policy In Patch IP. If change events are configured for create, delete and update operations then on updating any details corresponding create and delete events were getting registered instead of update events. This signifies that in Patch update operation too respective record was getting deleted and created instead of update.
Resolution:	Entity specification implementation has been changed to apply list behavior for Person details when using Policy In Patch IP. On doing update operations corresponding update change events are getting registered instead of create and delete events.
37038212		POL-15755	Batch jobs consisting extracts fails when OHI Extract purge runs concurrently
Description:	Policies daily exchange batch job fails when OHI policies extract data file purge is triggered concurrently because foreign key index for foreign key constraint on extract table was missing.
Resolution:	This issue was resolved by adding a foreign key index for the foreign key constraint on the extract table.
37146948	3-36913840401	POL-16003	Extract requests can have a limited number of characters in the condition
Description:	Extract request with a large query fails with activity message "ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 1". This is because the selection is stored in a variable with a maximum of 32000 characters.
Resolution:	Selection is now stored as a clob of which the maximum size depends on environment settings: (4 GB - 1) * DB_BLOCK_SIZE initialization parameter (8 TB to 128 TB). Contact database administrator for more details if needed. This change allows for a more extensive query in the extract request and a lesser chance of running into the ORA-06502 error.
36943678	3-37715853681	POL-15680	ID of single value flex code is returned as "null" (String) in the generic API response
Description:	ID of single value flex code is returned as "null" (String) in the generic API response.
Resolution:	ID attribute of single value flex code is now excluded from the generic API response
36921293	3-37479307981	POL-15660	Decimals are not shown on premium schedule lines for dimensions of datatype number.
Description:	When a premium schedule line with dimensions of datatype number is configured, decimals values cannot be entered and saved.
Resolution:	When a premium schedule line with dimensions of datatype number is configured, decimals values are shown properly
37156591	3-38290956121	POL-16039	Activity remains in IP status as the technical flag for submission isn’t cleared on TE activities
Description:	The activities remain stuck in IP status as the technical flag for submission (TEC_IND_SUBMISSION) flag was not cleared for the parent activities with status TE. These TE activities occupy the entire submission bucket, the size of which is determined by the property ohi.processing.max.concurrentparentactivities.size, which has a default value of 8. If the bucket is full, the newly submitted activity will remain in IP.
Resolution:	The query to fetch the count of currently submitted activity was modified to fix the issue.
Backports:	4.23.1.0.8
37204948	3-38073502601	POL-16139	Anomaly in generic patch operation for Time Valid dynamic records
Description:	When performing generic patch operation for a time valid dynamic record to update the endDate, the operation fails, getting a time valid error thrown. In some instances, when updating both startDate and endDate, other dynamic records are getting affected.
Resolution:	Generic patch operation on all resources is isolated from policies in IP patch operation. Apart from this a time validity check is added per dynamic records per resource which resolves the issue.
37200393	3-38363602931	POL-16131	Policies parameter values sequence incorrect when not using the toggle
Description:	Policies parameter values sequence incorrect when not using the toggle to expand view format
Resolution:	Policies parameter values are being sorted on display sequence and code in expanded and old view
37215139	3-38065813361	POL-16160	Calculation result lines are not displayed under each calculation period
Description:	Calculation result lines are not displayed under each calculation period. Calculation result (including all the calculation result lines under it) per calculation period is visible under the row displaying the member name (used for looking up products to be used for premium calculation)
Resolution:	Calculation result lines are getting displayed under each calculation period
37367133	3-38933143561	POL-16365	Query API returns partial JSON response when large volume of data is queried
Description:	When querying the policies API and fetching one or more dynamic fields/records of attached policy data, if the volume of dynamic records on attached policy data is high, the Query API may return a partial JSON response. This occurs when the memory consumption is high, leading to a TooManyRequestsException error on the server side, which interrupts the response generation.
Resolution:	The memory footprint when fetching attached policy data dynamic records is optimized.
37350510	3-38913319921	POL-16345	GEN-PROC-ERR is raised occasionally when accessing parameter values API
Description:	A GEN-PROC-ERR error intermittently occurs when accessing certain APIs. Once this error occurs, all subsequent API calls to the same resource fail with the same error. The only workaround is to restart the specific node/JVM.
Resolution:	To prevent the error when accessing certain APIs, the necessary initialization is now performed during startup instead of waiting for the first API call.
37211040		POL-16154	Policy - Premium bill allocation: JET UI is setting the active field by default to "false" whereas in ADF UI and API, the default is "true"
Description:	Navigate to policies page and click on create policy button click on add button in premium bill allocations section By default, active field should be true but its reflecting as false
Resolution:	The system floor-plan is updated with active indicator to true

BugDB

Internal

Summary

37231507

3-38581095771, 3-38556860431, 3-38933128751

POL-16187

Parent activity terminates or is marked as terminated (TE) prematurely, while its child activities are still under execution

Description:

While initializing one of the groups of activities, the parent activity is marked as 'TE' while the other groups (children) are still running.

Resolution:

If a group of activities fail to initialize, the system will automatically retry the initialization process up to a configurable maximum number of attempts. If all retries fail, the group of activities will be marked as Terminated (TE). This approach ensures that the parent activity remains active until all its child groups have been successfully processed, preventing premature termination

36547800

3-37468227341

POL-15064

Multiple issues while translating screens from English to Dutch

Description:

Translations not applied at several places when language is changed

Resolution:

Translation issues are fixed at few pages

37082021

3-37852540711

POL-15911

Global Activities page taking lot of time to retrieve results.

Description:

When a query is performed without any filters on the global activities page, it takes a lot of time to load the search results.

Resolution:

Updated the search criteria for the page to load results only when filters are applied.

37286658

3-37575580501

POL-16264

Field values are intermittently not being set when using the JET UI in version

Description:

Create dynamic fields, set a value for this field and save it. The updated value is not being saved properly.

Resolution:

Dynamic field values are updated properly using additional fields dialog

Backports:

4.23.1.0.9

37067536

3-36700304951

POL-15877

Processing of activities stuck with NPE on AggregateResumableActivityTask during node initialization

Description:

The Coherence service started processing activities too early, before the node was fully initialized, causing the ServiceLocator to initialize prematurely and resulting in a NullPointerException (NPE), which destabilized the entire application.

Resolution:

Delayed Coherence session creation until system initialization is complete, ensuring a stable environment for subsequent operations.

37287761

3-38222400721

POL-16265

Person details are not correctly copied with Policy In Patch integration point

Description:

Person details (like Assigned Providers, Contract Alignments, Person Covered Services etc.) were not correctly copied when using Policy In Patch IP. If change events are configured for create, delete and update operations then on updating any details corresponding create and delete events were getting registered instead of update events. This signifies that in Patch update operation too respective record was getting deleted and created instead of update.

Resolution:

Entity specification implementation has been changed to apply list behavior for Person details when using Policy In Patch IP. On doing update operations corresponding update change events are getting registered instead of create and delete events.

37038212

POL-15755

Batch jobs consisting extracts fails when OHI Extract purge runs concurrently

Description:

Policies daily exchange batch job fails when OHI policies extract data file purge is triggered concurrently because foreign key index for foreign key constraint on extract table was missing.

Resolution:

This issue was resolved by adding a foreign key index for the foreign key constraint on the extract table.

37146948

3-36913840401

POL-16003

Extract requests can have a limited number of characters in the condition

Description:

Extract request with a large query fails with activity message "ORA-06502: PL/SQL: numeric or value error ORA-06512: at line 1". This is because the selection is stored in a variable with a maximum of 32000 characters.

Resolution:

Selection is now stored as a clob of which the maximum size depends on environment settings: (4 GB - 1) * DB_BLOCK_SIZE initialization parameter (8 TB to 128 TB). Contact database administrator for more details if needed. This change allows for a more extensive query in the extract request and a lesser chance of running into the ORA-06502 error.

36943678

3-37715853681

POL-15680

ID of single value flex code is returned as "null" (String) in the generic API response

Description:

ID of single value flex code is returned as "null" (String) in the generic API response.

Resolution:

ID attribute of single value flex code is now excluded from the generic API response

36921293

3-37479307981

POL-15660

Decimals are not shown on premium schedule lines for dimensions of datatype number.

Description:

When a premium schedule line with dimensions of datatype number is configured, decimals values cannot be entered and saved.

Resolution:

When a premium schedule line with dimensions of datatype number is configured, decimals values are shown properly

37156591

3-38290956121

POL-16039

Activity remains in IP status as the technical flag for submission isn’t cleared on TE activities

Description:

The activities remain stuck in IP status as the technical flag for submission (TEC_IND_SUBMISSION) flag was not cleared for the parent activities with status TE. These TE activities occupy the entire submission bucket, the size of which is determined by the property ohi.processing.max.concurrentparentactivities.size, which has a default value of 8.

If the bucket is full, the newly submitted activity will remain in IP.

Resolution:

The query to fetch the count of currently submitted activity was modified to fix the issue.

Backports:

4.23.1.0.8

37204948

3-38073502601

POL-16139

Anomaly in generic patch operation for Time Valid dynamic records

Description:

When performing generic patch operation for a time valid dynamic record to update the endDate, the operation fails, getting a time valid error thrown. In some instances, when updating both startDate and endDate, other dynamic records are getting affected.

Resolution:

Generic patch operation on all resources is isolated from policies in IP patch operation. Apart from this a time validity check is added per dynamic records per resource which resolves the issue.

37200393

3-38363602931

POL-16131

Policies parameter values sequence incorrect when not using the toggle

Description:

Policies parameter values sequence incorrect when not using the toggle to expand view format

Resolution:

Policies parameter values are being sorted on display sequence and code in expanded and old view

37215139

3-38065813361

POL-16160

Calculation result lines are not displayed under each calculation period

Description:

Calculation result lines are not displayed under each calculation period. Calculation result (including all the calculation result lines under it) per calculation period is visible under the row displaying the member name (used for looking up products to be used for premium calculation)

Resolution:

Calculation result lines are getting displayed under each calculation period

37367133

3-38933143561

POL-16365

Query API returns partial JSON response when large volume of data is queried

Description:

When querying the policies API and fetching one or more dynamic fields/records of attached policy data, if the volume of dynamic records on attached policy data is high, the Query API may return a partial JSON response. This occurs when the memory consumption is high, leading to a TooManyRequestsException error on the server side, which interrupts the response generation.

Resolution:

The memory footprint when fetching attached policy data dynamic records is optimized.

37350510

3-38913319921

POL-16345

GEN-PROC-ERR is raised occasionally when accessing parameter values API

Description:

A GEN-PROC-ERR error intermittently occurs when accessing certain APIs. Once this error occurs, all subsequent API calls to the same resource fail with the same error. The only workaround is to restart the specific node/JVM.

Resolution:

To prevent the error when accessing certain APIs, the necessary initialization is now performed during startup instead of waiting for the first API call.

37211040

POL-16154

Policy - Premium bill allocation: JET UI is setting the active field by default to "false" whereas in ADF UI and API, the default is "true"

Description:

Navigate to policies page and click on create policy button click on add button in premium bill allocations section By default, active field should be true but its reflecting as false

Resolution:

The system floor-plan is updated with active indicator to true

Issues that were backported in previous Release / Patch

BugDB	Internal	Summary	Backport	BugDB	SR
37156591	POL-16039	Activity remains in IP status as the technical flag for submission isn’t cleared on TE activities	4.23.1.0.8	37156542	3-38290956121
37286658	POL-16264	Field values are intermittently not being set when using the JET UI in version	4.23.1.0.9	36930375	3-37575580501