Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.20.3.0.5

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

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

Enhancements

ID	Summary	Description	Included in Patch
NXT-21469	Post Benefit Callout	The End Benefit Callout enhancement NXT-20813 was completed in 3.20.3. However the precise timing of the callout needs to be one step earlier within the claims flow. One should be able to do the callout after the Benefits but before Adjudication. As part of this enhancement, check/performing of End Benfits Callout Rules is moved, from just before Finalization to immediately after setting the status to Benefits Done.
OIG-1366	Dynamic Logic Hooks/Extensions	Country packs involves delivering configuration. This configuration includes dynamic logic to process country specific usecases. These dynamic logic can be extended by customers to provide their specific changes/extensions. This enhancement allows to do that. This is enabled by introducing a new signature 'Extension' for all such extensions with a reference to the base dynamic logic that it is extending. At runtime, the application finds out all the extensions and invoked them.

Summary

Description

Included in Patch

NXT-21469

Post Benefit Callout

The End Benefit Callout enhancement NXT-20813 was completed in 3.20.3. However the precise timing of the callout needs to be one step earlier within the claims flow. One should be able to do the callout after the Benefits but before Adjudication. As part of this enhancement, check/performing of End Benfits Callout Rules is moved, from just before Finalization to immediately after setting the status to Benefits Done.

OIG-1366

Dynamic Logic Hooks/Extensions

Country packs involves delivering configuration. This configuration includes dynamic logic to process country specific usecases. These dynamic logic can be extended by customers to provide their specific changes/extensions. This enhancement allows to do that. This is enabled by introducing a new signature 'Extension' for all such extensions with a reference to the base dynamic logic that it is extending. At runtime, the application finds out all the extensions and invoked them.

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

Ref	Action	Subject	Description
OIG-1366	Modified	Dynamic Logic Page	Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable.

Ref

Action

Subject

Description

OIG-1366

Modified

Dynamic Logic Page

Added Base dynamic logic. This is done for both UI (ADF and Jet) where applicable.

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
32029774	3-24571978961	NXT-21317	BP	LOV not displayed for certain flexcodes for Dynamic records.
Description:	In the Dynamic Records popup, LOV is not displayed for flex codes field.
Resolution:	Fixed the refresh issue. Now user can launch and select value from LOV for flex code field.
32300941	3-23723613251	NXT-21773	BP	Descriptor is not found while unmarshalling reference sheet lines in multi node cluster setup
Description:	When dynamic field usage and reference sheets are created using API in a cluster setup and reference sheet line import activity is started on the node (not on which the dynamic field usage and reference sheets are created ), descriptor for reference sheet line is not found while unmarshalling.
Resolution:	Reference sheet lines are now imported successfully in multi node cluster setup and descriptor is present while unmarshalling reference sheet lines.
32404965	3-24944743701	NXT-21892	BP	ElementID missing in WriteConsumptionBatch error messages
Description:	ElementId is missing from error messages that are logged in ResultDataFileSet for writeConsumptionBatch.
Resolution:	ElementID is now added for all business errors.
32468968		NXT-21984	BP	Task is stuck in 'PROCESSING' status if the node leaves the cluster
Description:	When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the status of the task remains in 'PROCESSING' status. The other nodes in the cluster should have recovered/requeued that task.
Resolution:	When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster.
32506351		NXT-22047	BP	Unable to query claims on servicedMember.relationIdentifierList.identifier
Description:	Generic HTTP API search on <child>.relation(+)relationIdentifierList.identifier.like("123â€) gave error: An error occurred in processing the request; for more information about the error search the logging for occurrences of ;relationIdentifierList, is not a (dynamic) field for class <child> For example on claims: api/generic/claims?q=servicedMember.relationIdentifierList.identifier.like("123â€)
Resolution:	When a search is done on a relation child, like claims, addresses, using relationIdentifierList, this search is now properly executed.
31989244		NXT-21261		Issues with the Inbound Data Sets Page
Description:	Following issues have been observed on the Inbound Data Sets page after the newly added BENEFITS_HTTP and PRODUCTS_HTTP definitions : 1. File Upload Option is currently not supported. 2. The result messages are no longer shown for the newly added definitions due to the different technical implementation. Consequently the user now has to navigate to the activity messages in order to see how the product file processed. These message dialogs should show the activity messages for the appropriate activity.
Resolution:	File Upload option is now available for the new HTTP type definitions (BENEFITS_HTTP and PRODUCTS_HTTP). The Status column shows the status of the import along with the number of result messages. For the HTTP type definitions, clicking on the status link with the number of messages > 0, a dialog which contains the Activity Messages is shown.
32284837	3-24518747031	NXT-21755		Prevent: Claims Status out of Sync with claim status history after unfinalize claim
Description:	There are few instances of a situation that a claim was unfinalized, but claim status remained at Finalized. This situation needed a data repair script to continue.
Resolution:	The issue of claim status being out of sync is addressed in 2 ways: 1. An additional business CLA-CLAI-047 prevents the data corruption from happening. 2. Additional logging is added to diagnose the issue further. Logging setting they may be helpful: Logs UI actions so that the flow of a claim through UI can be followed: <logger name="com.oracle.healthinsurance.claims.interaction" level="debug"/> Logs when from a UI action, the status moves to Finalize: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/> If this setting results in log being written, further diagnosis is needed, as the UI typically does not set the status to Finalized. This is done by background processing. The logger above does show the complete stack trace, so is helpful to find out which code path is involved. Logs all status changes triggered by UI code: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/> The logger above does show the complete stack trace.

BugDB

Internal

Summary

32029774

3-24571978961

NXT-21317

LOV not displayed for certain flexcodes for Dynamic records.

Description:

In the Dynamic Records popup, LOV is not displayed for flex codes field.

Resolution:

Fixed the refresh issue. Now user can launch and select value from LOV for flex code field.

32300941

3-23723613251

NXT-21773

Descriptor is not found while unmarshalling reference sheet lines in multi node cluster setup

Description:

When dynamic field usage and reference sheets are created using API in a cluster setup and reference sheet line import activity is started on the node (not on which the dynamic field usage and reference sheets are created ), descriptor for reference sheet line is not found while unmarshalling.

Resolution:

Reference sheet lines are now imported successfully in multi node cluster setup and descriptor is present while unmarshalling reference sheet lines.

32404965

3-24944743701

NXT-21892

ElementID missing in WriteConsumptionBatch error messages

Description:

ElementId is missing from error messages that are logged in ResultDataFileSet for writeConsumptionBatch.

Resolution:

ElementID is now added for all business errors.

32468968

NXT-21984

Task is stuck in 'PROCESSING' status if the node leaves the cluster

Description:

When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the status of the task remains in 'PROCESSING' status. The other nodes in the cluster should have recovered/requeued that task.

Resolution:

When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster.

32506351

NXT-22047

Unable to query claims on servicedMember.relationIdentifierList.identifier

Description:

Generic HTTP API search on <child>.relation(+)relationIdentifierList.identifier.like("123â€) gave error:
An error occurred in processing the request; for more information about the error search the logging for occurrences of ;relationIdentifierList, is not a (dynamic) field for class <child>
For example on claims:
api/generic/claims?q=servicedMember.relationIdentifierList.identifier.like("123â€)

Resolution:

When a search is done on a relation child, like claims, addresses, using relationIdentifierList, this search is now properly executed.

31989244

NXT-21261

Issues with the Inbound Data Sets Page

Description:

Following issues have been observed on the Inbound Data Sets page after the newly added BENEFITS_HTTP and PRODUCTS_HTTP definitions :
1. File Upload Option is currently not supported.
2. The result messages are no longer shown for the newly added definitions due to the different technical implementation. Consequently the user now has to navigate to the activity messages in order to see how the product file processed. These message dialogs should show the activity messages for the appropriate activity.

Resolution:

File Upload option is now available for the new HTTP type definitions (BENEFITS_HTTP and PRODUCTS_HTTP).
The Status column shows the status of the import along with the number of result messages. For the HTTP type definitions, clicking on the status link with the number of messages > 0, a dialog which contains the Activity Messages is shown.

32284837

3-24518747031

NXT-21755

Prevent: Claims Status out of Sync with claim status history after unfinalize claim

Description:

There are few instances of a situation that a claim was unfinalized, but claim status remained at Finalized. This situation needed a data repair script to continue.

Resolution:

The issue of claim status being out of sync is addressed in 2 ways:
1. An additional business CLA-CLAI-047 prevents the data corruption from happening.
2. Additional logging is added to diagnose the issue further.

Logging setting they may be helpful: Logs UI actions so that the flow of a claim through UI can be followed: <logger name="com.oracle.healthinsurance.claims.interaction" level="debug"/>

Logs when from a UI action, the status moves to Finalize: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/>
If this setting results in log being written, further diagnosis is needed, as the UI typically does not set the status to Finalized. This is done by background processing. The logger above does show the complete stack trace, so is helpful to find out which code path is involved.

Logs all status changes triggered by UI code: <logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/>
The logger above does show the complete stack trace.

Issues that were backported in previous Release / Patch

No backports.