Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.18

This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.18.

Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise.

In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases.

Enhancements

ID	Summary	Patch
CPN-3775	Allow purging of data with a 7-day retention period in non-production environments The data purge process previously required a minimum retention period of 30 days. This enhancement allows to configure a lower retention period (eg: 7 days) specifically in non-production environments, while production environments maintain the 30-day policy. This change will help optimize disk space in non-production environments. Documentation Links: Administration Guide - Database - Purging - Auto Purge Installation Guide - Release Installation - Install Database Objects
NXT-26542	Exposed generic API for deployment metadata and extended User Preferences to support switching between customer and browser timezones Exposed generic API for deployment metadata to retrieve the customer timezone information. Introduced a new browserTimeZone flag in the User Preferences API, with a default value of false. When browserTimeZone is set to true, timestamps are displayed in the end user’s browser timezone. When browserTimeZone is set to false, timestamps are displayed in the configured customer timezone.
NXT-33004	Copy Action for Duplicating Records on HRR Pages The Copy Action is available when the metadata indicates that cloning is supported for a resource. It allows users to quickly duplicate an existing record by providing a new functional key. The system pre-fills the remaining values from the original record (excluding system-generated fields), allowing users to modify and save the new record while keeping the original record unchanged. During cloning, the following child entities are not copied: User Roles for Access Roles, Relation Identifiers for Persons, and Provider Limit Rules for Provider Limit Categories. Modifying individual child records during the clone operation is currently not supported for Access Restriction Grants under Access Roles, Partial Provider Pricing Clauses under Pricing Options, and Diminishing Rate Blocks, along with nested block amount and size lists, under Diminishing Rates. Documentation Links: Developer Guide - Clone API
NXT-33659	Disable user location based time conversion JET UI no longer relies only on the user’s browser timezone for datetime display. This helps prevent incorrect time conversion for customers operating across different geographic locations. The customerTimeZone, configured in the deployment metadata table during application installation, is used by default by JET UI. Users can override this through the "Use Browser Timezone?" option in the Preferences dialog, after which the UI will use the browser timezone. If customerTimeZone is not configured or is invalid/unsupported by JET, the UI falls back to the browser timezone. Documentation Links: Developer Guide - JET UI - References - Properties - Properties Security Guide - User Access - Function Access Restriction (JET)
NXT-33718	Extended user preference - Reorder and Auto-commit With this enhancement it is now possible to reorder table columns as per user’s preference. Also, the save button to store preference is replaced by auto commit feature. This feature is available for all pages based based on the following floor plan template : * View and Edit List table * List View - Table This feature is also available for select pages which are not floorplan based: Common Pages like Reference sheets Claims page claim line tab In Policies application, pages like Premium schedule lines, Adjustment lines, Fee schedule lines

Summary

Patch

CPN-3775

Allow purging of data with a 7-day retention period in non-production environments

The data purge process previously required a minimum retention period of 30 days. This enhancement allows to configure a lower retention period (eg: 7 days) specifically in non-production environments, while production environments maintain the 30-day policy. This change will help optimize disk space in non-production environments.

Documentation Links:
Administration Guide - Database - Purging - Auto Purge
Installation Guide - Release Installation - Install Database Objects

NXT-26542

Exposed generic API for deployment metadata and extended User Preferences to support switching between customer and browser timezones

Exposed generic API for deployment metadata to retrieve the customer timezone information. Introduced a new browserTimeZone flag in the User Preferences API, with a default value of false. When browserTimeZone is set to true, timestamps are displayed in the end user’s browser timezone. When browserTimeZone is set to false, timestamps are displayed in the configured customer timezone.

NXT-33004

Copy Action for Duplicating Records on HRR Pages

The Copy Action is available when the metadata indicates that cloning is supported for a resource. It allows users to quickly duplicate an existing record by providing a new functional key. The system pre-fills the remaining values from the original record (excluding system-generated fields), allowing users to modify and save the new record while keeping the original record unchanged.

During cloning, the following child entities are not copied: User Roles for Access Roles, Relation Identifiers for Persons, and Provider Limit Rules for Provider Limit Categories. Modifying individual child records during the clone operation is currently not supported for Access Restriction Grants under Access Roles, Partial Provider Pricing Clauses under Pricing Options, and Diminishing Rate Blocks, along with nested block amount and size lists, under Diminishing Rates.

Documentation Links:
Developer Guide - Clone API

NXT-33659

Disable user location based time conversion

JET UI no longer relies only on the user’s browser timezone for datetime display. This helps prevent incorrect time conversion for customers operating across different geographic locations. The customerTimeZone, configured in the deployment metadata table during application installation, is used by default by JET UI. Users can override this through the "Use Browser Timezone?" option in the Preferences dialog, after which the UI will use the browser timezone. If customerTimeZone is not configured or is invalid/unsupported by JET, the UI falls back to the browser timezone.

Documentation Links:
Developer Guide - JET UI - References - Properties - Properties
Security Guide - User Access - Function Access Restriction (JET)

NXT-33718

Extended user preference - Reorder and Auto-commit

With this enhancement it is now possible to reorder table columns as per user’s preference. Also, the save button to store preference is replaced by auto commit feature.

This feature is available for all pages based based on the following floor plan template : * View and Edit List table * List View - Table

This feature is also available for select pages which are not floorplan based:

Common Pages like Reference sheets

Claims page claim line tab

In Policies application, pages like Premium schedule lines, Adjustment lines, Fee schedule lines

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

Ref	Action	Description
NXT-26542	Added	deploymentmetadata API New read-only generic API is added.
NXT-26542	Modified	userpreferences API Added a new attribute browserTimeZone to the user preferences API.

Ref

Action

Description

NXT-26542

Added

deploymentmetadata API

New read-only generic API is added.

NXT-26542

Modified

userpreferences API

Added a new attribute browserTimeZone to the user preferences API.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Description
NXT-33659	Modified	Preferences Dialog A new checkbox - "Use Browser Timezone?" has been introduced in Preferences which can be used to override the customer’s configured timezone.

Ref

Action

Description

NXT-33659

Modified

Preferences Dialog

A new checkbox - "Use Browser Timezone?" has been introduced in Preferences which can be used to override the customer’s configured timezone.

Breaking Changes

Ref Action Description

Ref	Action	Description
CPN-3775	Modified	Installer The installer is enhanced to automatically create or update deployment metadata in the OHI$DEPLOYMENT_METADATA database table during installation or upgrade operations. As part of this enhancement, the `ohi_install.cfg` template now includes the following new configuration parameters: timeZoneOverride deploymentType isEnvironmentProduction

CPN-3775

Modified

Installer

The installer is enhanced to automatically create or update deployment metadata in the OHI$DEPLOYMENT_METADATA database table during installation or upgrade operations. As part of this enhancement, the ohi_install.cfg template now includes the following new configuration parameters:

timeZoneOverride
deploymentType
isEnvironmentProduction

Access Restrictions

Ref	Action	Description
NXT-33659	Modified	CO0019 The 'deploymentmetadata API' access restriction has been added to function code CO0019.

Ref

Action

Description

NXT-33659

Modified

CO0019

The 'deploymentmetadata API' access restriction has been added to function code CO0019.

Bug Fixes

BugDB	SR	Internal	Summary
39212174		NXT-34011	When CTR claim message list is configured as tab table, only code is visible
Description:	When user configures ctrClaimMessageList as tab table in CTR Claims page, only code is displayed and rest of the fields are empty
Resolution:	All the fields configured are visible in CTR claim message list tab table and ctrClaimMessage is displayed as header banner for CTR claims similar to claims page

BugDB

Internal

Summary

39212174

NXT-34011

When CTR claim message list is configured as tab table, only code is visible

Description:

When user configures ctrClaimMessageList as tab table in CTR Claims page, only code is displayed and rest of the fields are empty

Resolution:

All the fields configured are visible in CTR claim message list tab table and ctrClaimMessage is displayed as header banner for CTR claims similar to claims page

Issues that were backported in previous Release / Patch

No backports.