Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.2
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.2.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.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. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
NXT-26366 |
POST, PUT, PATCH, DELETE on Episode details This enhancement removes the restriction on the Episode details resource that prevents creates, updates and deletes through the generic API. |
Bug Fixes
| BugDB | SR | Internal | BP | Summary |
|---|---|---|---|---|
34697777 |
NXT-25535 |
BP |
Money fields where amount has decimal value with .9999 getting rounding off to whole number |
|
Description: |
At various pages, the money field is getting rounding off. Example- Charged amount was mentioned as "123.9999", but on claimline, it is showing '124' |
|||
Resolution: |
||||
34979425 |
3-31477093221 |
NXT-26208 |
BP |
Financial message not created for reversal transactions when covered amount on claim is null |
Description: |
If a claim processing involves currency conversion, a manual fatal message attached to the claim/claim lines can cause covered amount and covered amount currency (on claim and claim line) to be null. |
|||
Resolution: |
Financial messages for reversal transactions are now created when covered amount on the claim is null. |
|||
34982451 |
3-31454344411 |
NXT-26225 |
BP |
Covered Amount is set to null on claim line when line is denied with fatal message |
Description: |
Covered Amount set to null on claim line when line is denied with fatal message at Manual Adjudication |
|||
Resolution: |
On a denied claim the total covered amount is set to zero in the default currency. On an approved claim that includes claim lines with covered amounts in different currencies, the total covered amount and currency is left empty, i.e., set to null. |
|||
35031394 |
3-31827806771 |
NXT-26305 |
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: |
Previous transaction is now explicitly committed before moving to exception handling to resolve the lock issue. |
|||
35031420 |
3-31827806771 |
NXT-26308 |
BP |
Reference sheet import activity terminates due to technical error and status remains in 'In Process' status |
Description: |
Some times Reference sheet import activity terminates due to technical error and status remains in 'In Process' status. Technical error occurs because the import type domain enum for reference sheet is not registered in time on all the nodes in a multi cluster setup. |
|||
Resolution: |
Reference sheets should be completed with 'CO' status without any technical error |
|||
35063554 |
3-31977844691 |
NXT-26382 |
BP |
HTTP api metadata caches url from the first api request to get the metadata of a resource |
Description: |
When metadata of any entity is accessed first time using generic API, it’s generated with absolute URLs and gets cached. Subsequent requests to the same metadata is served from the cache. In multi-node system, accessing metadata from different nodes will return already cached metadata and base URL (hostname and port) mentioned there won’t match with current requests' base URL. |
|||
Resolution: |
Instead of caching generic API metadata request response with absolute URLs, it gets cached by replacing base URL by placeholder. While returning response for each generic API metadata, cached metadata is processed and placeholder gets replaced by base URL of current request. |
|||
35076450 |
NXT-26403 |
BP |
New episode is getting created for overlapping claim lines |
|
Description: |
When an episode exists and incoming claim line overlaps with it in such a way that start date of claim line is less than episode start date and claim line end date is between episode start and end date, claim line isn’t getting included in that episode. |
|||
Resolution: |
Applicability of claim line for given episode is verified by checking the start date or end date of claim line between episode start and end date. |
|||
35080990 |
3-31142348479; |
NXT-26429 |
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. |
|||
35109399 |
3-32181209591 |
NXT-26502 |
BP |
Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes |
Description: |
Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes |
|||
Resolution: |
The column name which was assigned while creating a flex code field usage after an error message was thrown, was incorrect. After the correct columnName is assigned, the deletion of dynamic records using method deleteDynamicRecord on key value works fine. |
|||
35119649 |
NXT-26521 |
BP |
Activity recovery at startup time does not set process_stop_datetime |
|
Description: |
When an activity in 'Initial' or 'In process' status was set to 'Technical Error' status, process_stop_datetime was not set accordingly hence giving an impression that the activity’s elapsed time keeps increasing. |
|||
Resolution: |
The update query which sets the 'Technical Error' status has been modified to set the correct process_stop_datetime as well. |
|||
35130250 |
3-32265793401 |
NXT-26532 |
BP |
CLA - JET UI : The placing of decimal point is different in JET and ADF |
Description: |
For any scalar dynamic field in the response data for an entity, the value always came as a string "BigDecimalDynField": "12.34". but expected is "BigDecimalDynField": 12.34. |
|||
Resolution: |
ScalarAttributeGetHandler did not resolve the value for the dynamicFieldObject earlier, now it extracts the value of from a dynamicFieldObject to basic datatype like BigDecimal, integer etc. |
|||
35162571 |
3-32225018171 |
NXT-26607 |
BP |
Excess from previous product is not applied when member upgrades the product and serving waiting period for new one . |
Description: |
Excess from previous product is not applied when member upgrades the product and serving waiting period for new one . This happens when both the current policy product and previous policy product with the same product are included in enrollment response . |
|||
Resolution: |
Upgrades with same product is processed with previous product |
|||