Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.11
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.11.
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. |
As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
35058192 |
3-32082556451 |
NXT-26373 |
BP |
Business rule OHI-ACRE-006 on Data Access Group for Update privilege is not preventing updates for all fields |
Description: |
When a user has retrieve rights on the access restriction on data access group attached to a claim, it is possible to update several fields. Error message OHI-ACRE-006 should be shown on all updates. |
|||
Resolution: |
When a user has retrieve rights on the access restriction on data access group attached to a claim, error message OHI-ACRE-006 is shown on all the updates. |
|||
35037673 |
3-29958611621 |
NXT-26313 |
BP |
Reprocessing locked claim line leads to CLA-CLLI-007 error |
Description: |
When we reprocess claim line which has either null covered amount or null covered number of units and system has an EIR configured at manual adjudication level , then benefits processing leads to CLA-CLLI-007 error . |
|||
Resolution: |
Reprocessing locked claim lines are processed without any error now . |
|||
35064167 |
3-32106750331 |
NXT-26389 |
BP |
Selecting all claimlines in a claim and resolve a pend for all the claimlines at once, doesn’t work |
Description: |
Resolving a Pend Reason for all the claimlines at once available for a claim is not working. |
|||
Resolution: |
Bulk claimline pend resolution feature is modified to resolve the specified pend on all the claim lines. Note that pend will get resolved on all the lines where it is present (irrespective of the lines selected by the user) . |
|||
35080994 |
3-31142348479; 3-32128672291 |
NXT-26430 |
BP |
Flexcodesystem and flexcodes imported through CMT set on a target environment are not correctly mapped for all the translations |
Description: |
When a CMT set having flexcodes values are imported, then flexcodes are not correctly mapped to their respective field usages for all the translations. They are working fine only for locale translation. |
|||
Resolution: |
After this fix, when importing flexcodesystem and flexcodes with CMT, flexcodes are correctly mapped to their respective field usages for all the translations. |
|||
35077782 |
3-32043583961 |
NXT-26417 |
BP |
Claim with multiple CTR versions should always show versions where reversal is false |
Description: |
A claim having multiple CTR versions sometimes display reversal amounts as negative number |
|||
Resolution: |
A claim having multiple CTR versions shows the amounts where the reversal is false. |
|||
34891410 |
3-30739647241 |
NXT-26022 |
BP |
Claims processing is slow during CMT import |
Description: |
If a CMT data set containing large number of items that execute dynamic logic (eg: to validate if the dynamic field is valid as per the field validation dynamic logic) are imported when claims are processed (which involves executing a number of dynamic logic during claims flow), both CMT import and claims processing become very slow because execution of dynamic logic in both CMT import and claims processing is handled inefficiently. |
|||
Resolution: |
The execution of dynamic logic in both CMT import and claims processing has been optimized. |
|||
35031395 |
3-31827806771 |
NXT-26306 |
BP |
Unable to update Activity status to 'TE' while handling unexpected exceptions |
Description: |
Activity status was not being updated as TE while getting unexpected exceptions during the progress of an activity. This was due to the application not being able to complete the previous transaction before updating error |
|||
Resolution: |
We are explicitly committing the previous transaction before moving to exception handling to resolve the lock issue. |