Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.1
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.1.
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. |
Bug Fixes
BugDB | SR | Internal | BP | Summary |
---|---|---|---|---|
34650859 |
3-30727204301 |
NXT-25488 |
BP |
Custom lov poceduregroupdetails is not working in claimlines page |
Description: |
Create a record definition (ex: medication) with record-fields (medicationName, otherMedication of type char-100). Create ProcedureGroupDetailsLOV floorplan with title property Procedure.descr3. Use the record field medicationName as LOV on proceduregroupdetails. It is not saving the medication name |
|||
Resolution: |
The dynamic record usage values are saved and works as expected when it is configured as LOV on proceduregroupdetails |
|||
34791257 |
NXT-25720 |
BP |
Claim Line Summary for Approved claimline shows Fatal error for 1-2 seconds if opened after Denied Claim line Summary and then the respective drawer gets mis-aligned |
|
Description: |
Click on Claim Line Summary of 'Denied' claim line, which will show FATAL errors. Then click on Claim Line Summary of 'Approved' claim line, which displays FATAL error for sometime and then in 1-2 seconds, error goes away but respective drawer is mis-aligned |
|||
Resolution: |
Claim Line Summary drawer for Approved claim lines behaves consistently when switching between denied claim lines |
|||
34866934 |
NXT-25951 |
BP |
Display never not working for dynamic fields mentioned in floorplan when autoinclude is set to yes |
|
Description: |
Dynamic field is shown in persons page UI and able to edit it in extensibility drawer, even though the property is added to the floorplan and display attribute is set to never. |
|||
Resolution: |
Dynamic field is not shown in extensibility drawer when configured in the floorplan and display 'never' is set |
|||
34868046 |
NXT-25959 |
BP |
Additional Fields: Apply and Cancel buttons are shown in View mode |
|
Description: |
Apply and Cancel buttons are shown in View mode in additional fields drawer |
|||
Resolution: |
Apply button is not shown in view mode in additional fields drawer |
|||
34868555 |
NXT-25961 |
BP |
Zip files cannot be imported on Mac and Linux |
|
Description: |
File cannot be imported using Mac and Linux. This is a common issue observed with file upload component |
|||
Resolution: |
It is possible to import Zip files on Mac and Linux. |
|||
34870001 |
3-31210906991 |
NXT-25963 |
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 |
|||
34871347 |
NXT-25970 |
BP |
Additional Fields: Cancel button is saving the data. |
|
Description: |
Create a new claim and click on additional fields. Save few additional fields. Now edit the additional fields and click on cancel. New changes are getting saved |
|||
Resolution: |
On click of cancel, the values in the additional fields drawer move back to prior state if there are any changes made. |
|||
34871991 |
NXT-25974 |
BP |
Add to Floorplan - Next button is not responding |
|
Description: |
Create a usage Field and click on add to floor plan. Select custom Floor plan and click on next. Select the set and select 'Create new tile'. Now Next button is not responding |
|||
Resolution: |
Next button is working fine in Usages page when Add To Floorplan action is performed |
|||
34872470 |
NXT-25979 |
BP |
Delete on a new row should remove additional fields overflow section as well |
|
Description: |
Product Limits tab: Add new row. Then click on Delete. It should additional fields overflow section as well. |
|||
Resolution: |
Delete on a new row removes additional fields overflow section as well |
|||
34872502 |
NXT-25980 |
BP |
Episodes page - pop-up alignment issue |
|
Description: |
Episodes page - If you hover over an insurable entity the pop-up shows in left corner and outside the page |
|||
Resolution: |
Episodes page - hovering over insurable entity, the pop-up shows in the page and not outside the page context |
|||
34873114 |
NXT-25984 |
BP |
Additional Fields Drawer in JET pages : Single value non-time valid fields are not persisting after save |
|
Description: |
SVNTV fields are not getting saved when values are provided in Additional Fields drawer |
|||
Resolution: |
Single value non-time valid fields in Additional Fields drawer in JET screens are persisted with values specified by user, on save action. |
|||
34874801 |
NXT-25986 |
BP |
Unsaved pop up message is showing when we click on add button in few pages |
|
Description: |
On clicking of add button unsaved pop up showing. Pop-up is also shown while scrolling to fetch more rows. The issue doesn’t occur if we add new rows without doing a blank search |
|||
Resolution: |
Unsaved pop up message doesn’t show when we click on add button in table pages |
|||
34885737 |
3-31391733371 |
NXT-26003 |
BP |
OHI accepts dynamic field numeric content of 13 digits while 12 is defined as max. length |
Description: |
When a Field Definition is created as type 'Number' with a specific length, with no Decimal value, and when value is assigned to it from the specific page, it accepts a number of lengths one more than the specified value. |
|||
Resolution: |
Field Definition of type 'Number' accepts correct length even with no Decimal value. |
|||
34887120 |
3-31111068731 |
NXT-26012 |
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 |
|||
34888776 |
3-31414189871 |
NXT-26013 |
BP |
Advanced search on 'createdBy' not working in claims page |
Description: |
When trying to implement advanced search for a claim based on the claim created by. After developing the LOV on users, which will show displayName when id of the user will passed. Query API created is not correct and returns error. |
|||
Resolution: |
Advanced search on 'createdBy' works fine in claims page |
|||
34888865 |
3-31264277391 |
NXT-26014 |
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 |
|||
34891400 |
3-30739647241 |
NXT-26021 |
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. |
|||
34894812 |
3-31049172121 |
NXT-26027 |
BP |
Error while processing a claim in manual benefits status from postman |
Description: |
While processing a claim, 'IllegalArgumentException: AddMessage function unavailable in the current context' error is raised on derivation rule dynamic logic execution if dynamic logic calls addMessage predefined method internally. |
|||
Resolution: |
Added message context before executing derivation rule. |
|||
35026279 |
3-31464688761 |
NXT-26030 |
BP |
Claim history panel issues for ctr version of claim. |
Description: |
There are few issues around the claim history panel such as CTR history not showing all the statuses and the time stamp shown for the status for CTR claim is wrong. |
|||
Resolution: |
Claim history panel changes done as part of this bug: • Records are ordered by field "dateTime". • Removed claim status history selector. • The default behavior is to show recent cycles. • Prior cycle selector is the first selector. • Date time : timestamp is shown Ctr History panel changes as part of this bug: • Removed status history selector. • All statuses are shown as returned by API. • Removed prior cycle selector. Records are ordered by statusDateTime descending. |
|||
34907854 |
NXT-26045 |
BP |
Procedure Group Page: Table is not loading when navigating to object navigation 'Procedure Group Details' |
|
Description: |
The table is not loading when navigating to object navigation 'Procedure Group Details' on the 'Procedure Group' page. |
|||
Resolution: |
'Procedure Group Details' on the 'Procedure Group' page is loaded when navigating between object navigation links |
|||
34909767 |
NXT-26050 |
BP |
Context string enclosed in single quote gives API error |
|
Description: |
Search query formed when context string has a trailing space leads to API error. Search Query Expected is for example "q": "groupClient.code.eq('TEST ')" but actually is 'q": "groupClient.code.eq(''TEST '')" |
|||
Resolution: |
Search performed without errors when context string has a trailing space as well |
|||
34911396 |
NXT-26053 |
BP |
Apply button is not responding in additional fields drawer when mandatory dynamic records are configured |
|
Description: |
Make a Dynamic Record as mandatory from usages page. Create a new claim and click on additional fields drawer. Apply button is not responding, when checked the console we have a error to fill in the Extensibility tab level |
|||
Resolution: |
Apply button in additional fields drawer works fine with mandatory dynamic records configured |
|||
34911610 |
NXT-26055 |
BP |
Field with SVTV Flex code & mandatory are not responding in additional fields drawer |
|
Description: |
Create SVTV Flex code which is mandatory for Enrollment products and fill the data for this field in the additional fields drawer, still we get the error to fill the data |
|||
Resolution: |
SVTV Flex code field values can be added without any error in additional fields drawer |
|||
34921600 |
3-29584669481,3-31267385791 |
NXT-26080 |
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. |
|||
34942494 |
3-30886340351 |
NXT-26093 |
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. |
|||
34950188 |
3-30739753241 |
NXT-26109 |
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. |
|||
34954899 |
NXT-26117 |
BP |
Contracted procedures are not sorted on code if number of records are less than 150. |
|
Description: |
Contracted procedures are not sorted on code if number of records are less than 150. |
|||
Resolution: |
Sorting is applied now. |
|||
34962689 |
NXT-26138 |
BP |
typeJET field in product limits tab of products page doesn’t display value |
|
Description: |
typeJET custom property in product limits tab of products page doesn’t display value and leads to console error |
|||
Resolution: |
typeJET field in product limits tab of products page displays proper value |
|||
34974184 |
3-31809029671 |
NXT-26186 |
BP |
ClaimStatusHistory API doesn’t return any response for the claims created from JET UI |
Description: |
'claimstatushistory' API returns response for the claims created from ADF UI but not for the claims created from JET-UI. created a claim from JET UI with the below payload and 'claimstatushistory' API for the created claim responds with 204. |
|||
Resolution: |
ClaimStatusHistory for a claim in ENTRY state is now created from the backend. |
|||
34974818 |
NXT-26189 |
BP |
When the value of claim is undefined in adjudication cases, the user is unable to download the file. |
|
Description: |
When the value of claim is undefined, the user is unable to download the file. |
|||
Resolution: |
The download feature in adjudication details is working as expected. |
|||
34977394 |
NXT-26196 |
BP |
Floorplan changes for Auto Include Extensibility. |
|
Description: |
The floorplan page allows auto include extensibility to set to be true and also existing floorplans have auto include extensibility set to true for templates other than SEARCH TABLE, VIEW EDIT LIST and VIEW EDIT HIERARCHICAL RECURSIVE. |
|||
Resolution: |
All the existing floorplans of templates other than SEARCH TABLE, VIEW EDIT LIST and VIEW EDIT HIERARCHICAL RECURSIVE have auto include extensibility flag set to false and also while creating new floorplan, it conditionally displays the auto include extensibility based on the template. |
|||
34981363 |
NXT-26219 |
BP |
Boolean fields with NULL value should display blank in UI |
|
Description: |
Boolean fields are not getting downloaded when displayed as No in UI but are blank when downloaded. Boolean fields with NULL values needs to be displayed as blank rather than 'No' in UI |
|||
Resolution: |
Boolean fields with NULL values are displayed as blank rather than 'No' in UI |
|||
34982463 |
3-30270443091 |
NXT-26228 |
BP |
Table stats for pri$fee_schedule_lines is gathered for all child activities concurrently |
Description: |
Table stats for pri$fee_schedule_lines is gathered for all child activities concurrently . |
|||
Resolution: |
Gather table stats once for all the child activities . |
|||
34987897 |
NXT-26248 |
BP |
Internal caching has been optimized |
|
Description: |
Internal caching structures were holding references to other structures too long, leading to too much memory consumption |
|||
Resolution: |
The references are removed, making it possible to reuse the memory |
|||
35013727 |
3-30452029991 |
NXT-26270 |
BP |
Limit from product benefit specification is not selected on recalculation of coverage from manual benefits. |
Description: |
Limit from product benefit specification is not selected on recalculation of coverage from manual benefits . |
|||
Resolution: |
Now this will be resolved. We are adding the limits during recalculation and limit consumptions are updated accordingly . |
|||
35037750 |
3-29958611621 |
NXT-26314 |
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 . |
|||
35058181 |
3-32082556451 |
NXT-26372 |
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. |
|||
35064157 |
3-32106750331 |
NXT-26388 |
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) . |
|||
35077779 |
3-32043583961 |
NXT-26416 |
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. |