Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.6

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

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

OHI applications expose the technical ID (created by sequence generator) in HTTP API and IP. This might be changed to an alternate technical ID (the data type might not be an integer) in a future release. Hence, it is advised to follow the generated HATEOAS links instead of hard-coding/bookmarking the IDs in the external integrations.

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	Description	Included in Patch
POL-11121	Prevent leading or trailing spaces in user name	This enhancement prevents the use of leading or trailing spaces in the user’s login name. The provisioning integration point raises a fatal message when leading or trailing spaces are used in the login name. The enhancement supports a conversion script for existing login names with trailing spaces.
POL-11122	Optimize the performance of reference sheet lines queries	The performance of querying reference sheet lines from dynamic logic (using SearchBuilder) is optimized by caching the query results (controlled by a system property).

Summary

Description

Included in Patch

POL-11121

Prevent leading or trailing spaces in user name

This enhancement prevents the use of leading or trailing spaces in the user’s login name. The provisioning integration point raises a fatal message when leading or trailing spaces are used in the login name. The enhancement supports a conversion script for existing login names with trailing spaces.

POL-11122

Optimize the performance of reference sheet lines queries

The performance of querying reference sheet lines from dynamic logic (using SearchBuilder) is optimized by caching the query results (controlled by a system property).

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

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up
post-upgrade: Released upgrade script has run.
post-deploy: New application is deployed and is up and running.

Stage: pre-upgrade

1) Action: Run the following SQL update statement, to replace leading and trailing spaces in login_name with 'X' for all users with trailing spaces.

update ohi_users            -- replace leading spaces
set    login_name            = lpad(ltrim(login_name), length(login_name), 'X')
,      last_updated_date     = current_timestamp
,      last_updated_by       = -1
,      object_version_number = object_version_number + 1
where  login_name != ltrim(login_name);

update ohi_users            -- replace trailing spaces
set    login_name            = rpad(rtrim(login_name), length(login_name), 'X')
,      last_updated_date     = current_timestamp
,      last_updated_by       = -1
,      object_version_number = object_version_number + 1
where  login_name != rtrim(login_name);
commit;

If you run into the "ORA-00001: unique constraint violated" error, this means that there is already a user with the same login_name after replacing spaces with X. In this case, identify the offending login_names with the following query:

select  u1.login_name
from    ohi_users u1, ohi_users u2
where   u1.login_name != rpad(rtrim(u1.login_name), length(u1.login_name), 'X') -- u1: users whose login_name are renamed
and     u2.login_name = rpad(rtrim(u1.login_name), length(u1.login_name), 'X'); -- u2: users whose login name equals the renamed name

And similarly where rpad(rtrim(… has been replaced with lpad(ltrim(… for errors in login_names with leading spaces.

Manually replace these login_names with extra X’s to avoid the unique key violation, e.g. if user "login_with_space " was found with the previous query, copy it (including the space) and update it with the following statement:

update ohi_users
set    login_name            = 'login_with_spaceXX'      -- add an extra X
,      last_updated_date     = current_timestamp
,      last_updated_by       = -1
,      object_version_number = object_version_number + 1
where  login_name = 'login_with_space '                  -- the offending login_name
commit;

After this, run the first update statement again.

Configuration Properties

Ref	Action	Subject	Description
POL-11122	Added	ohi.referencesheetlines.query.results.cache.enabled	This is an optional property that controls if the reference sheet lines query results should be cached or not. The default value is true.
POL-11122	Added	ohi.referencesheetlines.query.results.cache.spec	A specification of Google Guava’s CacheBuilder configuration. It configures a cache for reference sheet lines query results. Defined as a string which is a series of comma-separated keys or key-value pairs, each corresponding to a CacheBuilder method. See Google Guava’s CacheBuilderSpec for additional detail. This is an optional property. Default value is "maximumSize=1000,softValues,recordStats"

Ref

Action

Subject

Description

POL-11122

Added

ohi.referencesheetlines.query.results.cache.enabled

This is an optional property that controls if the reference sheet lines query results should be cached or not. The default value is true.

POL-11122

Added

ohi.referencesheetlines.query.results.cache.spec

A specification of Google Guava’s CacheBuilder configuration. It configures a cache for reference sheet lines query results. Defined as a string which is a series of comma-separated keys or key-value pairs, each corresponding to a CacheBuilder method. See Google Guava’s CacheBuilderSpec for additional detail.

This is an optional property.

Default value is "maximumSize=1000,softValues,recordStats"

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

Ref	Action	Subject	Description
POL-11122	Modified	All	The dynamic logic will be re-compiled when the application starts up the first time after upgrading to this release. So, application startup could take more time than usual. This is an one time operation, so the dynamic logic are not re-compiled in the subsequent startup.

Ref

Action

Subject

Description

POL-11122

Modified

All

The dynamic logic will be re-compiled when the application starts up the first time after upgrading to this release. So, application startup could take more time than usual. This is an one time operation, so the dynamic logic are not re-compiled in the subsequent startup.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB	SR	Internal	BP	Summary
34597582		NXT-25389	BP	The change in currency value on Coverage Regime page is not reflecting after saving the record
Description:	Coverage Regimes doesn’t redirect properly to details page and the changes are not reflecting after a save operation is performed. Steps: Search for existing Coverage regime record. Click on Edit icon. Change the currency value from LOV. Save the record. The value for currency is showing blank
Resolution:	The change in currency value on Coverage Regime page gets reflected properly after saving the record
34607204		NXT-25413	BP	Conditional display is not working when it is applied on field which is in a separate tile
Description:	Configure a field which needs to be displayed based on a condition in a separate tile ex Messages in Dynamic Logic page. The field itself is not displayed even if the condition evaluates to true
Resolution:	Conditional display of fields works fine when it is applied on a field which is added in a separate tile
34674189		NXT-25511	BP	Display 'never' property is not working for Flex Code fields
Description:	If a property "display":"never" is configured for a flex code field, the field is still displayed.
Resolution:	Display 'never' property can be configured for Flex Code fields and the field is not shown in UI
34560311	3-30480654261	NXT-25331	BP	Cannot save the page when a single value type of record definition is configured
Description:	When a single value record definition is configured which further has some mandatory picklist or flex code fields, while creating and saving a policy, getting error for mandatory field even if value is selected
Resolution:	A single value record definition can be configured with a mandatory picklist or flex code field and it works fine
34485832	3-30287286671	NXT-25234	BP	Dynamics Fields in a FlexCode definition should be updated through CMT
Description:	The Field attribute in FlexCodeFieldUsage is not being updated using CMT import. It shows error with code GEN_RULE_023.
Resolution:	It is now allowed to update Field in a FlexCode Definition with certain conditions. It is allowed upgrade the size of a field of same datatype, but not downgrade of size, or in case of Number field it does not allow downgrade on decimal size as well. The exception is covered by the BR COD-FCFU-017
34608788	3-30244018461	NXT-25418	BP	Claim line sequence number is not being generated when user clicks on 'attach and next' button from claimline details page
Description:	Claim Line Sequence number is not being generated when user clicks on 'Attach and Next' button from claimline details page.
Resolution:	Claim Line Sequence number is auto generated when user clicks on 'Attach and Next' button from claim line details page.
34601970	3-30564858911	NXT-25408	BP	NullPointerException Occurred in Processing the claims request
Description:	If the policy products (from enrollment response) contain two products, one is the same as the product in the override and it has a previous product that has a different product that has a PostBenefits regime.
Resolution:	Fixed the NullPointerException, now the claim should be finalized without NPE
34460194	3-30242956101	NXT-25196	BP	Claims submission screen shows allowed and covered amounts without decimal places
Description:	Allowed amount and Covered amount fields don’t show decimal places
Resolution:	Allowed amount and Covered amount fields in Claims View-Edit screen shows decimal places now.
34464423	3-30244018461	NXT-25203	BP	Claim start and end date is not calculating correctly when 2 or more claim lines are present.
Description:	Claim start and end date is not calculating correctly when 2 or more claim lines are present.
Resolution:	Now, claim start and end date is getting calculated correctly when multiple claim lines are present.
34596559		NXT-25387	BP	Claim Line Summary does not display Pricing information
Description:	When a claim is priced successfully, it is expected that at claim line summary level, pricing details are displayed but it displays "No Pricing Data Available".
Resolution:	Claim Line Summary drawer now displays the Pricing information when a claim is priced
34714036	3-29505983391	NXT-25505	BP	Claims start and end date should be set based on claim line start and end dates when a claim is created or updated
Description:	Claim start and end date are not populated based on the claim line’s start end end date
Resolution:	Claim start and end date will be evaluated based on the minimum start date and maximum end date of the underlying claim lines when a claim is created or updated.
34612978	3-29584669481	NXT-25424	BP	Target events are duplicated or missed when created persons through persons IP
Description:	When there is a bulk load of persons happening concurrently (through persons IP), it is seen that in target events there are duplicate or missing records.
Resolution:	The query that fetches source events is now ordered by a deterministic field.
34607973		NXT-25415	BP	Default value on a field that has a flexcode is not working
Description:	The default value on a field that has a flexcode is not working
Resolution:	The default value on a field that has a flexcode is working, when the default value is set on keyValue or the descriptor only. Format: { "name": "keyValue","value": "2" }
34379335	3-30071968921	NXT-25075	BP	Unable to create numeric LOVs using custom floorplans
Description:	Users cannot set a picklist for Numeric fields on a dynamic record. Configuration of custom LOVs on numeric fields is not working
Resolution:	It is possible to create a picklist for numeric fields on a dynamic record in JET, provided users configure the key field of flex code the same as the numeric values. Also, support on custom LOVs on the 'Date' field is deprecated

BugDB

Internal

Summary

34597582

NXT-25389

The change in currency value on Coverage Regime page is not reflecting after saving the record

Description:

Coverage Regimes doesn’t redirect properly to details page and the changes are not reflecting after a save operation is performed. Steps: Search for existing Coverage regime record. Click on Edit icon. Change the currency value from LOV. Save the record. The value for currency is showing blank

Resolution:

The change in currency value on Coverage Regime page gets reflected properly after saving the record

34607204

NXT-25413

Conditional display is not working when it is applied on field which is in a separate tile

Description:

Configure a field which needs to be displayed based on a condition in a separate tile ex Messages in Dynamic Logic page. The field itself is not displayed even if the condition evaluates to true

Resolution:

Conditional display of fields works fine when it is applied on a field which is added in a separate tile

34674189

NXT-25511

Display 'never' property is not working for Flex Code fields

Description:

If a property "display":"never" is configured for a flex code field, the field is still displayed.

Resolution:

Display 'never' property can be configured for Flex Code fields and the field is not shown in UI

34560311

3-30480654261

NXT-25331

Cannot save the page when a single value type of record definition is configured

Description:

When a single value record definition is configured which further has some mandatory picklist or flex code fields, while creating and saving a policy, getting error for mandatory field even if value is selected

Resolution:

A single value record definition can be configured with a mandatory picklist or flex code field and it works fine

34485832

3-30287286671

NXT-25234

Dynamics Fields in a FlexCode definition should be updated through CMT

Description:

The Field attribute in FlexCodeFieldUsage is not being updated using CMT import. It shows error with code GEN_RULE_023.

Resolution:

It is now allowed to update Field in a FlexCode Definition with certain conditions. It is allowed upgrade the size of a field of same datatype, but not downgrade of size, or in case of Number field it does not allow downgrade on decimal size as well. The exception is covered by the BR COD-FCFU-017

34608788

3-30244018461

NXT-25418

Claim line sequence number is not being generated when user clicks on 'attach and next' button from claimline details page

Description:

Claim Line Sequence number is not being generated when user clicks on 'Attach and Next' button from claimline details page.

Resolution:

Claim Line Sequence number is auto generated when user clicks on 'Attach and Next' button from claim line details page.

34601970

3-30564858911

NXT-25408

NullPointerException Occurred in Processing the claims request

Description:

If the policy products (from enrollment response) contain two products, one is the same as the product in the override and it has a previous product that has a different product that has a PostBenefits regime.

Resolution:

Fixed the NullPointerException, now the claim should be finalized without NPE

34460194

3-30242956101

NXT-25196

Claims submission screen shows allowed and covered amounts without decimal places

Description:

Allowed amount and Covered amount fields don’t show decimal places

Resolution:

Allowed amount and Covered amount fields in Claims View-Edit screen shows decimal places now.

34464423

3-30244018461

NXT-25203

Claim start and end date is not calculating correctly when 2 or more claim lines are present.

Description:

Claim start and end date is not calculating correctly when 2 or more claim lines are present.

Resolution:

Now, claim start and end date is getting calculated correctly when multiple claim lines are present.

34596559

NXT-25387

Claim Line Summary does not display Pricing information

Description:

When a claim is priced successfully, it is expected that at claim line summary level, pricing details are displayed but it displays "No Pricing Data Available".

Resolution:

Claim Line Summary drawer now displays the Pricing information when a claim is priced

34714036

3-29505983391

NXT-25505

Claims start and end date should be set based on claim line start and end dates when a claim is created or updated

Description:

Claim start and end date are not populated based on the claim line’s start end end date

Resolution:

Claim start and end date will be evaluated based on the minimum start date and maximum end date of the underlying claim lines when a claim is created or updated.

34612978

3-29584669481

NXT-25424

Target events are duplicated or missed when created persons through persons IP

Description:

When there is a bulk load of persons happening concurrently (through persons IP), it is seen that in target events there are duplicate or missing records.

Resolution:

The query that fetches source events is now ordered by a deterministic field.

34607973

NXT-25415

Default value on a field that has a flexcode is not working

Description:

The default value on a field that has a flexcode is not working

Resolution:

The default value on a field that has a flexcode is working, when the default value is set on keyValue or the descriptor only. Format: { "name": "keyValue","value": "2" }

34379335

3-30071968921

NXT-25075

Unable to create numeric LOVs using custom floorplans

Description:

Users cannot set a picklist for Numeric fields on a dynamic record. Configuration of custom LOVs on numeric fields is not working

Resolution:

It is possible to create a picklist for numeric fields on a dynamic record in JET, provided users configure the key field of flex code the same as the numeric values. Also, support on custom LOVs on the 'Date' field is deprecated

Issues that were backported in previous Release / Patch

No backports.