Release Notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.9

This document contains the release notes for Oracle Health Insurance Product Definition Patch 4.25.1.0.9.

Version compatibility: Oracle Health Insurance Product Definition 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
NXT-33750	Enhance UI download functionality to include all search results based on query criteria. This enhancement extends the UI download feature to export the complete search result dataset matching the active query for select pages in claims and product definition application Claims Draft provider pricing clauses (worksheet and across) Pricing Option – Partial Provider Pricing Causes Tab Reference sheets Product benefit specification Benefit specifications Claims Search Authorization Search Claim Lines Tab Adjudication Limit Consumption Tab Fee schedule lines Procedure group details Diagnosis group details Product Definition Product service definition (product and across) Generated Benefits Specifications ( product ) Benefits Specification In addition, multiple pages based on floorpan templates 1) View and Edit Table, 2) Search Object - List, 3) Search Object - table and 4) Tab tables/list (exception dynamic records) within View and Edit HRR now support download API based download feature. Documentation Links: Developer Guide - Integration - HTTP API - Download API

Summary

Patch

NXT-33750

Enhance UI download functionality to include all search results based on query criteria.

This enhancement extends the UI download feature to export the complete search result dataset matching the active query for select pages in claims and product definition application

Claims

Draft provider pricing clauses (worksheet and across)
Pricing Option – Partial Provider Pricing Causes Tab
Reference sheets
Product benefit specification
Benefit specifications
Claims Search
Authorization Search
Claim Lines Tab
Adjudication Limit Consumption Tab
Fee schedule lines
Procedure group details
Diagnosis group details

Product Definition

Product service definition (product and across)
Generated Benefits Specifications ( product )
Benefits Specification

In addition, multiple pages based on floorpan templates 1) View and Edit Table, 2) Search Object - List, 3) Search Object - table and 4) Tab tables/list (exception dynamic records) within View and Edit HRR now support download API based download feature.

Documentation Links:
Developer Guide - Integration - HTTP API - Download API

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

Ref	Action	Description
NXT-33750	Added	ohi.api.download.max.rows The ohi.api.download.max.rows system property, which allows users to configure the maximum number of rows that can be downloaded through the Download API. By default, this property is set to 2,000 rows. The maximum supported value is capped at 10,000 rows.

Ref

Action

Description

NXT-33750

Added

ohi.api.download.max.rows

The ohi.api.download.max.rows system property, which allows users to configure the maximum number of rows that can be downloaded through the Download API.

By default, this property is set to 2,000 rows. The maximum supported value is capped at 10,000 rows.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Description
NXT-33750	Modified	Proddef - Product Service Definition (Products and Across) Boilerplate text value is updated for all the Regime fields to indicate the type of regime
NXT-33750	Modified	All floorplan based pages (and Reference Sheet Lines) API based download is enabled in UI pages. However, there is an exclusion list application wise: Claims - Object Navigation Links, Provider Pricing Clause, Payment Registrations, Field Definitions, System Events, Insurable Entity Types, Adjudication Limits Search Proddef - Object Navigation Links, Service Definitions, Product Export Sets, Global Activities, Field Definitions, System Events Also, UI based download is retained in Extensibility tabs and tabs of some Detail pages: Claims - Fee Schedules (Fee Schedule Lines), Transaction Sources (Transaction Source Usages), Products (Product Limits), Banks (Addresses, Bank Account Number Relations), tabs in all the Pricing Rule pages Proddef - Parameter Aliases (Parameter Alias Values), Products (Cost sharing, Product provider Group, Product Limit Renewal)

Ref

Action

Description

NXT-33750

Modified

Proddef - Product Service Definition (Products and Across)

Boilerplate text value is updated for all the Regime fields to indicate the type of regime

NXT-33750

Modified

All floorplan based pages (and Reference Sheet Lines)

API based download is enabled in UI pages.

However, there is an exclusion list application wise:

Claims - Object Navigation Links, Provider Pricing Clause, Payment Registrations, Field Definitions, System Events, Insurable Entity Types, Adjudication Limits Search
Proddef - Object Navigation Links, Service Definitions, Product Export Sets, Global Activities, Field Definitions, System Events

Also, UI based download is retained in Extensibility tabs and tabs of some Detail pages:

Claims - Fee Schedules (Fee Schedule Lines), Transaction Sources (Transaction Source Usages), Products (Product Limits), Banks (Addresses, Bank Account Number Relations), tabs in all the Pricing Rule pages
Proddef - Parameter Aliases (Parameter Alias Values), Products (Cost sharing, Product provider Group, Product Limit Renewal)

Breaking Changes

Ref	Action	Description
NXT-33750	Modified	Below breaking change will be observed for UI download enhancement. Date / date time fields are not formatted. For system enumerations ( example status field on claim) key will be download. For composite columns - example when two different fields were shown in one column in UI, download will have columns per value. Example instead of one column for formatted name, download will have separate columns for first name, middle name , last name and so on. Another example is maximum value / current value in counters, and setup pages, in download separate columns will be present for maximum/current days, units and amount. Product service definition - download will show separate columns for each regime. In UI if a custom list of value is added on a native field / string field using floorplan based configuration, only native data will be part of download - example - partial provider pricing clauses only method code will be download

Ref

Action

Description

NXT-33750

Modified

Below breaking change will be observed for UI download enhancement.

Date / date time fields are not formatted.
For system enumerations ( example status field on claim) key will be download.
For composite columns - example when two different fields were shown in one column in UI, download will have columns per value. Example instead of one column for formatted name, download will have separate columns for first name, middle name , last name and so on. Another example is maximum value / current value in counters, and setup pages, in download separate columns will be present for maximum/current days, units and amount.
Product service definition - download will show separate columns for each regime.
In UI if a custom list of value is added on a native field / string field using floorplan based configuration, only native data will be part of download - example - partial provider pricing clauses only method code will be download

Access Restrictions

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	Summary
39526138		PRD-5587	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.
39526241		PRD-5588	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.
39455923	4-0002788234	PRD-5566	The Universal Indicator condition is missing from the exported file
Description:	In BENEFITS_HTTP export, the Benefit Specification Condition is not included when the Universal Indicator is set to “Yes”.
Resolution:	Updated the logic so the BENEFITS_HTTP export now includes the benefit condition when “Universal” is set to Yes.

BugDB

Internal

Summary

39526138

PRD-5587

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.

39526241

PRD-5588

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.

39455923

4-0002788234

PRD-5566

The Universal Indicator condition is missing from the exported file

Description:

In BENEFITS_HTTP export, the Benefit Specification Condition is not included when the Universal Indicator is set to “Yes”.

Resolution:

Updated the logic so the BENEFITS_HTTP export now includes the benefit condition when “Universal” is set to Yes.

Issues that were backported in previous Release / Patch

No backports.