Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.10
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.10.
| 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 |
|---|---|---|
AUT-3010 |
Activity Framework and Extract Metrics added to the applications. The following new metrics have been added to the applications: Activity Framework Metrics: ohi.activityprocessing.activities.started.count - Monitors number of activities started. ohi.activityprocessing.activities.completed.timer - Monitors duration of a completed activity. Extract Metrics: ohi.extract.extracts.started.count - Monitors number of extracts started. ohi.extract.entities.processed.count - Monitors number of processed (root) entities. |
Bug Fixes
| BugDB | SR | Internal | BP | Summary |
|---|---|---|---|---|
35471491 |
3-33307073211 |
NXT-27079 |
BP |
Reference Sheet Lines page is not loading all the results |
Description: |
Reference Sheet Lines page is not loading more than 50 records even when there are more than 50 records present in the database |
|||
Resolution: |
Reference Sheet Lines page loads records as per expected behavior since it uses a generic API now and also quick search is made based on Query API and advance search is removed from the page |
|||
35434715 |
3-33158060141 |
NXT-27020 |
BP |
Java.sql.sqlsyntaxerrorexception: ora-01795: maximum number of expressions in a list is 1000 |
Description: |
In ADF UI, while adding "Diagnosis Group Details" under "Diagnosis Group", when user click on Definition LOV to select value and if list of values have more than 1000 values, exception will be logged and user won’t be able to see data in UI. |
|||
Resolution: |
||||
35471850 |
3-31569988441 |
NXT-27081 |
BP |
Delete icon is shown in table row even if user doesn’t have access to delete |
Description: |
Table pages showed the delete icon despite using a user access role where the specified table page is configured with delete permission set to false. |
|||
Resolution: |
On configuring a page with no user access to delete/remove, the user does not see the delete icon on the page. |
|||
35472542 |
NXT-27089 |
BP |
Default value not shown for a flex code with descriptor and read-only=true |
|
Description: |
Default Value not shown for a flex code with Descriptor and floorplan property read-only set to true |
|||
Resolution: |
Default Value shows for a flex code with descriptor and read-only=true in floorplan |
|||
35487778 |
NXT-27112 |
BP |
Claim line resolve pend created on claim line not working |
|
Description: |
Claim line resolve pend not working when custom floorplan with multivalue field on claim line pend reason list is configured on the claims floorplan. |
|||
Resolution: |
Claim lines can be resolved without errors by selecting few claim lines from the claim lines tab and using the resolve pend reason button |
|||
35573745 |
NXT-27257 |
BP |
When Dynamic record is configured as Tab-List, getting error after filling the records and saving the claim |
|
Description: |
When Dynamic record is configured as Tab-List in claims floorplan, attaching a new record is not letting the claim to be saved and gives Business Rule errors. |
|||
Resolution: |
Claims can be saved without error when dynamic records are configured as tab in claims floorplan and with new values added for the dynamic record. |
|||
35441659 |
3-33085914661 |
NXT-27042 |
BP |
Tagging not working, system claim line floorplan do not get loaded when tagged with system claim floorplan. |
Description: |
The user is not able to add tagging to the system claim line floorplan (CLAIMLINESVIEWONLY), which is causing issues related to tagging on the claims page. Also, the proper floorplan is not getting loaded for claim lines while performing the 'ADD' action in the claim line tab. |
|||
Resolution: |
Floorplan will be loaded as per specifications while performing tab ADD action and when tagging is enabled. 'ADD' button at tab level will also be disabled when no applicable floorplans are present. |
|||
35472078 |
NXT-27087 |
BP |
In JET UI same list of additional columns is displayed in dynamic record tabs |
|
Description: |
When a dynamic record is configured as tab, additional fields are being added to that dynamic record from the parent resource when auto include extensibility is set to true for that floorplan. |
|||
Resolution: |
With auto include extensibility set to true, the dynamic records which are added to a floorplan as a tab table and tab list with detail page will show only the fields configured for the dynamic record and not include other fields from the parent resource. |
|||
35603385 |
3-33578720361 |
NXT-27318 |
BP |
Enable edit operation on 'financials' page if user has read access for claims(cl0172) and edit access for financials(cl0126) |
Description: |
User should be able to edit the financial transaction process data even though user has read access for claims. Edit action should be enabled if the below conditions are satisfied. 1. At least read access to the claims page. 2. Edit access to financial transaction process data page (this data is accessible from the claims page in the side menu "Financials") |
|||
Resolution: |
Edit action on FinancialTransactionProcessData page is now controlled with access restriction code CL0126. This page is editable if user has update access to CL0126, and it becomes non-editable when user has only read access to CL0126. |
|||
35481932 |
3-33328591481 |
NXT-27105 |
BP |
Records are not sorted even if default sort is defined in payload for widgets |
Description: |
Create/update any widget to have default sort section added in payload. Add the widget as a card/dashboard. Records are not sorted in widgets |
|||
Resolution: |
Records are sorted properly as defined in the payload for widgets |
|||