Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.6
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.25.1.0.6.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.25.1.x is only compatible with other Oracle Health Insurance applications release version 4.25.1.x unless explicitly stated otherwise. |
| In accordance with the OHI error correction policy (Document 1494031.1 on My Oracle Support), error correction support will be provided for this release and the previous two releases. |
Enhancements
| ID | Summary | Patch |
|---|---|---|
NXT-32307 |
UI: Ability to search for a claim based on code from claim page This enhancement adds the ability to search for a claim using the claim code directly from the claims page. A new search field is introduced on the claim page, allowing users to enter a claim code and quickly find the matching claim. |
Upgrade Steps for Installation
To perform the upgrade, perform the following steps:
-
Perform any pre-upgrade steps.
-
Stop all the managed nodes running the existing version of the application.
-
Perform any pre-undeploy steps.
-
Undeploy the existing version of the application.
-
Back up the database.
-
Perform any post-undeploy steps.
-
Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.
-
Change Installation Configuration: In
<OHI_ROOT>/util/install, make a copy ofohi_install.cfg.templateand name itohi_install.cfg. -
Edit
ohi_install.cfgto contain your specific database connection data and other configuration settings. The settings are explained in the file itself. -
Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)
-
Run the Upgrade script:
-
Open a command window and browse to
<OHI_ROOT>/util/install. -
Run the upgrade by executing
./ohi-update.sh .
-
-
Make the required changes to the ohi properties file
-
Perform any post-upgrade steps
-
Start WebLogic application server
-
Deploy the Application
-
Perform any post-deploy steps
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38412369 |
NXT-32505 |
Date format for English language setting is set to MM/DD/YYYY |
|
Description: |
The Date format for English language setting is set to MM/DD/YYYY instead of DD/MM/YYYY. Unsupported browser locale falls back to default en-US setting. |
||
Resolution: |
An application property 'ohi.ui.default.locale' is introduced to set the locale for unsupported language-country setting. Users can set this property if their locale setting is not supported by JET framework and if it should not fallback to default en-US setting |
||
38488187 |
NXT-32678 |
Rename 'amount' column to 'total_claimed_amount' in Claims in Progress reporting view. |
|
Description: |
The Claims in Progress reporting view contains a column representing the total claimed amount on a specific claim. This column is named 'amount', but that could cause issues if there is a dynamic field usage on claims with the same name 'amount'. |
||
Resolution: |
The 'amount' column in Claims in Progress reporting view is renamed to 'total_claimed_amount'. |
||
36946582 |
3-41621149821 |
NXT-30147 |
Index.html is added to URL after login with IDCS config |
Description: |
Post login, index.html is getting appended to application URL. This is observed in SAML authentication flow |
||
Resolution: |
index.html is not observed in the application URL in SAML authentication flow post fix. |
||
38446638 |
NXT-32589 |
In-active coverage regimes are shown in the regimes LOV on the Benefit Specifications page. |
|
Description: |
Only Active Regimes should be shown in regimes LOV of Benefit specifications page |
||
Resolution: |
System floorplan is modified to filter only active regimes for coverageregime, authorizationregime, postbenefitsregime, reservationregime, waitingperiodregime in benefit specification page |
||
38539741 |
NXT-32779 |
Access Restriction to Enable 'Benefits only' button on claim needs delete access |
|
Description: |
Delete access on claims is not needed for enabling 'Benefit Only' Button. |
||
Resolution: |
Delete access is not required for 'Benefit Only' action. |
||
38533294 |
NXT-32763 |
Financial holds on claims page should not be dependent the claims page create access. |
|
Description: |
The Add button is not displayed on the Financial Holds page when the user does not have Create access on the Claims page. |
||
Resolution: |
Add button on the Financial Holds page is displayed if the user has Create access on Financial Holds instead of claims page |
||
38519784 |
NXT-32844 |
Fee Schedules - Line Condition dropdown is showing all the dynamic logic |
|
Description: |
Line condition LOV is showing all the dynamic logic instead of only Fee schedule signature dynamic logic |
||
Resolution: |
System floorplan is updated with a filter for specific dynamic logic (Fee schedule). Only Fee Schedule signature dynamic logics is shown in the LOV |
||
38526433 |
NXT-32734 |
Provider Pricing Clause Page - For PPC record with Reimbursement method as 'Diminishing Rates', object navigation page 'Diminishing Rates overrides' is not loading |
|
Description: |
Diminishing Rates Overrides object navigation page is not loading in Provider Pricing Clause Page. |
||
Resolution: |
Diminishing Rates Overrides page loads without any issues |
||
38543545 |
NXT-32785 |
Pricing worksheets 'Last Build By' field shows Login Name instead of Display Name |
|
Description: |
After building the pricing worksheet the 'Last Build By' shows login name instead of Display Name. |
||
Resolution: |
Last Build By field now shows the Display Name in advance search, search results as well as detail page |
||
38592491 |
NXT-32850 |
Conditional value auto population and resetting using a triggering condition with property "default" is not working |
|
Description: |
Conditional display of a field’s value is not working when a default value is set in the floorplan |
||
Resolution: |
The field is now populating and updating its value correctly based on the triggering conditions when default is set in floorplan |
||