Release Notes for Oracle Insurance Gateway Patch 4.25.1.0.10

This document contains the release notes for Oracle Insurance Gateway Patch 4.25.1.0.10.

Version compatibility: Oracle Insurance Gateway Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.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.

Enhancements

No enhancements.

Additional Upgrade Steps

Post-Deploy Phase

1) OHI Agent upgrade

Upgrade OHI Agent: Refer to Downloading and Running Oracle Health Insurance Agent for steps to perform the Agent upgrade.

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.

Breaking Changes

This section intentionally left blank.

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB SR Internal Summary

39436246

OIG-5161

Stash items are now read in a deterministic order

Description:

Stash items inserted in the same batch could have the same creation timestamp. Because unprocessed stash item reads were ordered only by creation date, items with the same timestamp could be returned in an intermittent order. If dynamic logic stopped processing after an error, this could leave expected earlier items unprocessed and cause intermittent status update failures.

Resolution:

Stash item reads now use the stash item ID to order by. This makes cursor-style reads, including readUnprocessed() and getFirstUnprocessed(), return stash items in a deterministic order.

38634119

4-0001407551

OIG-4749

Integration invocation with ZIP file fails

Description:

When an integration is invoked with a ZIP file, it fails with an error code GEN-PROC-ERR and exchange is not triggered.

Resolution:

Integration can be successfully invoked with a ZIP file. When exchange starts processing the Trigger step, the file is unzipped to data files and can be used in further processing.

38774365

4-0001329840

OIG-4839

Exchange recovery fails for Fusion job timeouts

Description:

While processing fusion steps in an exchange,

  1. If Load job ends with TIMEDOUT status in fusion portal, the exchange fails and recovery is not possible.

  2. If Load job is still in RUNNING status at the end of polling timeout (configured in the fusion destination), the exchange fails and recovery is not possible.

Resolution:

While processing fusion steps in an exchange,

  1. If fusion job ends with TIMEDOUT status in fusion portal,

    1. For Import job or Submit job, the exchange continues processing without any failure, similar to other error scenarios.

    2. For Load job, the exchange is marked Failed.

      1. The Load job has to be manually recovered by customer in fusion portal.

      2. Then, the exchange can be recovered to start polling the status of the Load job again and continue processing as usual.

  2. If fusion job is still in RUNNING status at the end of polling timeout (configured in the fusion destination),

    1. For all fusion jobs (Load job, Import job and Submit job), the exchange is marked Timed Out.

    2. Then, the exchange can be recovered to start polling the status of the fusion job again and continue processing as usual.

39444641

OIG-5164

PHI logging includes unmatched 'left joins' rows

Description:

When a query selects a PHI column from the right side of a LEFT JOIN, PHI logging is created for all rows from the left-side table, including rows where the joined row does not exist. In those cases the PHI column is effectively null, but a PHI log event is still written. This leads to incorrect PHI audit entries for rows that did not actually expose PHI.

Resolution:

When the joined column is marked as PHI but there is no match, no PHI Event is logged for that missing column.

39526236

OIG-5191

PHI audit logs corrected for aliased base views in data transfer payloads

Description:

In specific data transfer scenarios, when a base view is queried through an alias and the Base View is outside of the Relation context, PHI logging was not generated correctly.

Resolution:

The system now generates the PHI audit logs correctly for these aliased base view scenarios.

39741614

OIG-5252

ZIP files are not scanned during exchange invocation

Description:

Previously, an on-demand antivirus scan for a data file set with ZIP content but no extracted data files could return a successful result without scanning the ZIP content. The on-demand scan decision only evaluated child data file scan statuses and did not consider the parent data file set status used for ZIP content.

Resolution:

The on-demand antivirus scan flow now considers the parent data file set scan status when ZIP content is present.

39099774

OIG-5008

Correcting the Notification IP response error message when exchange is not in WaitingOnExternalSystem(W) status

Description:

Oracle Insurance Gateway now returns HTTP 409 Conflict with error code OIG-GATE-066 when a notification is received for an exchange that is no longer in WaitingOnExternalSystem (W) status, instead of returning HTTP 204 No Content in the Notification IP.

Resolution:

When the exchange is not in WaitingOnExternalSystem(W) status, a HTTP 409 Conflict response is returned with error code OIG-GATE-066. Example error message:

OIG-GATE-066: Exchange with id {exchangeId} for integration code {integrationCode} received notification for step {exchangeStepId} with code {integrationStepCode}, which could not be parsed properly due to: Exchange {exchangeId} is in state {exchangeStatus} (incorrect state for receiving a notification)

Issues that were backported in previous Release / Patch

No backports.