Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.9
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.9.
| 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. |
| 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 |
|---|---|---|---|---|
34876660 |
3-31111068731 |
NXT-25991 |
BP |
"Add message" action on claim line level ( dialog) should not allow for empty message |
Description: |
"Add Message" action on claim line level ( dialog) should not allow for empty message. The add message functionality (that cannot be influenced on the floorplan) should require a message to be selected. |
|||
Resolution: |
"Add Message" action on claim line level ( dialog) will not allow for empty message. A message should be selected mandatorily |
|||
34679846 |
3-30739753241 |
NXT-25520 |
BP |
OHI allows to resolve pend while user does not have corresponding access restriction |
Description: |
OHI ADF screen allows to resolve claim line pend reason when user does not have access grants to resolve the pend. This happens only when the claim is re-processed. When the claim is processed for the 1st time, the applicable error message is shown. |
|||
Resolution: |
OHI ADF screen does not allow to resolve the claim line pend reason when user does not have access grants to resolve the pend even when the claim is processed for the 2nd time. |
|||
34835598 |
3-31264277391 |
NXT-25867 |
BP |
Claim pend history does not reflect the user that resolved the pend |
Description: |
When viewing the pend reason history of a claim, the "resolved by" does not reflect the user that actually resolved the pend. Instead it reflects the user that submitted the claim for further processing. |
|||
Resolution: |
PendReason 'resolvedBy' user information is displayed in history drawer for claim and claimline pendreason |
|||
34726395 |
3-29584669481,3-31267385791 |
NXT-25595 |
BP |
OptimisticLockingException when updating lastlogintimestamp of the user |
Description: |
Updating lastLoginTimestamp is controlled by a system property ohi.ws.last.login.update.threshold i.e the lastLoginTimestamp is not updated if the user logs-in multiple times with in the same hour.But if there are concurrent requests next second after this hour, both the API/IP requests try to update the same user record, system throws 500 error in this case. This causes problem in updating the LASTLOGINTIMESTAMP |
|||
Resolution: |
Error thrown by the system is ignored in case there are concurrent requests to update the same user record. The LASTLOGINTIMESTAMP will be set according to the first request that updates the user record amongst all the incoming concurrent requests. |
|||
34844254 |
3-30886340351 |
NXT-25893 |
BP |
JetUI- provider search is taking around 30sec average to load a provider in the claim form |
Description: |
Provider search which appears in several sections in the claim like service provider, referral provider (as applicable) takes an average of around 30sec ( 37sec-27sec) response time. |
|||
Resolution: |
Added function based index on REL_PROVIDERS table NAME column in claims application to improve performance. |
|||
34869983 |
3-31210906991 |
NXT-25962 |
BP |
Custom boilerplates are not working for claim line details view page |
Description: |
When user configures custom boilerplates for Claim line details view page floorplan, custom boilerplates are not getting rendered in the UI. |
|||
Resolution: |
Custom boilerplates configured in claimline floorplan are shown with proper text in UI |
|||