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. |
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. |
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: |
|||
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 : |
|||
Resolution: |
|
|||
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: 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"/> Logs all status changes triggered by UI code:
<logger name="com.oracle.healthinsurance.claims.domain.internal.entities.ClaimDomain" level="debug"/> |