Release Notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.2
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 4.24.1.0.2.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 4.24.1.x is only compatible with other Oracle Health Insurance applications release version 4.24.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 |
|---|---|---|
OIG-3474 |
Improve error messages on timeout When a timeout occurs, the error message will clearly state which timeout setting resulted in the timeout. We have had cases of long-running dynamic logic producing a timeout. It was not clear whether this was due to:
In this enhancement, we have addressed the following timeout errors:
An example error message that will be shown in the error log in case of a dynamic logic execution timeout scenario is: "Timeout error occurred at PayloadTransformer for step RNI_TRAFO_STEP of integration/subflow ID 400345758 due to execution timed out after 300 seconds. Start time: Thu Jul 18 21:14:56 IST 2024. You can configure this timeout limit by setting the property [ohi.dynamiclogic.timeout=100]." |
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 |
|---|---|---|---|
37033057 |
NXT-30283 |
Auto Fill Start Date/End Date on the Claim Line from any of the Claim Level Date Fields doesn’t work in Edit Mode |
|
Description: |
When in edit mode, the fields in tab table list can be defaulted to parent context property like claim region. But these values are not getting picked in edit mode although it works fine in create mode. |
||
Resolution: |
Auto Fill Start Date/End Date on the Claim Line From Any of the Claim Level Date Fields works in Edit Mode |
||
37072217 |
3-37897137551 |
NXT-30333 |
Deny message with overturned set to NO not working as expected |
Description: |
Deny message with overturned set to NO not working as expected when attached from Waiting period regime |
||
Resolution: |
Logic to decide on when should claim line be denied did not consider non-overturned deny messages attached on a claim line from a waiting period regime. We have modified the logic to check for the message severity and the origin and perform the action accordingly. |
||
37110332 |
3-37830283897 |
NXT-30432 |
Definition of flex codes under a dynamic record is not consisting of addtional fields |
Description: |
Definition of flex codes configured under a dynamic record does not contain additional fields (fields other than code and descriptor) |
||
Resolution: |
All fields configured on a flex code other than code and descriptor are available in the definition when the flex code is configured on a record definition |
||
37167370 |
NXT-30519 |
Toggle once set "ON" does not remain in the same state upon page refresh or reload. |
|
Description: |
The claim page when toggled to be viewed in new view mode does not retain the state on reload or refresh of the page. |
||
Resolution: |
The claim page will retain the state of the new view toggle on refreshing or reloading the claim in the current browser session. |
||
37033230 |
NXT-30286 |
Additional Flex Code fields cannot be used in flex code conditional checks. |
|
Description: |
Additional flex code fields when used as a part of conditional checks does not work. |
||
Resolution: |
Additional flex code fields can be used as a part of conditional checks and other condition driven updates in edit mode. |
||
37201571 |
NXT-30561 |
Context value not adding default values for LOV fields |
|
Description: |
The LOV fields are not getting populated with default context values, but if we hard code as value, it is working |
||
Resolution: |
The LOV fields are getting populated with default context value conditions |
||
37173496 |
NXT-30530 |
Claims Page - Pricing Section - Applied PPC tab - Quantifier value is not displaying |
|
Description: |
When opening a finalized claim with a covered amount and navigating to the Pricing section under the 'Applied Provider Pricing Clause' tab, the Quantifier value is not displayed. |
||
Resolution: |
The Quantifier value is displayed correctly in the 'Applied Provider Pricing Clause' tab. |
||
37122728 |
NXT-30453 |
The spacing between the currency code and the amount field is missing when there is only a single currency |
|
Description: |
When there is only one currency in system, there is no space showing between the currency code and amount field |
||
Resolution: |
The spacing is present between the currency code and the amount field even when there is a single currency |
||
37021861 |
NXT-30275 |
Exchange Rate: Decimal is not showing in rate field |
|
Description: |
Navigate to Exchange rate page. Click on add and enter any number with decimal like 12.345 or 12.789. Value is getting rounded up and decimal is not shown. It is displayed as 12 and 13 after round off |
||
Resolution: |
Exchange Rate: Decimals are displayed exactly without being rounded off in rate field |
||
37257360 |
NXT-30644 |
Sorting at tab table is not working |
|
Description: |
Create a Dynamic record. Add the record to tab table in floorplan. On Saving the data at tab table the records are not getting sorted as expected. |
||
Resolution: |
Sorting is now applied at tab table |
||
37153174 |
NXT-30479 |
Title is not coming in summary and detailed view of list view Tabs |
|
Description: |
Title property is not enhanced for the dynamic record when added as tab result. As well as in the title property of the corresponding detail page |
||
Resolution: |
Title property is now displayed for dynamic record when added as tab result |
||
37251078 |
NXT-30633 |
Query is not building correctly when % is being used in the filter condition. |
|
Description: |
When % is configured in the context based filter value which evaluates to a value with space the query is included with extra quotes. |
||
Resolution: |
When % is configured in the context based filter value which evaluates to a value with space the query is constructed correctly. |
||
37004602 |
NXT-30252 |
Linking Relation: A relation link is not deleted when a relation is deleted |
|
Description: |
When a relation link was deleted using the generic person API, the corresponding counterpart remains intact. |
||
Resolution: |
Deleting one of the relation links via the generic person API will now also remove its counterpart. |
||
37196935 |
NXT-30559 |
Auto Populate Is Not Working For New View Mode For Dynamic Tab Fields |
|
Description: |
Conditional setting of properties not working for dynamic record as a tab in new-view mode. |
||
Resolution: |
Conditional setting of properties works for a dynamic record which is configured as a tab in new-view mode. |
||
37203141 |
3-38478259058 |
NXT-30565 |
User is able to create boolean type dynamic field usages |
Description: |
Boolean type is not supported for any dynamic field usages. POST /generic/fields API allows boolean type field creation. Due to this it can be linked to any dynamic field usages. |
||
Resolution: |
Prevented boolean type field creation |
||
37151818 |
3-38218061471 |
NXT-30476 |
Filter condition with multiple contexts used is freezing the page. |
Description: |
Multiple context object when accessed in a single filter, the page becomes unresponsive. |
||
Resolution: |
Filter conditions with multiple context objects works without freezing the page. |
||
37228013 |
NXT-30601 |
Unable to reprocess a claim using reprocess button. |
|
Description: |
Claims page is not refreshing after performing the reprocess action. |
||
Resolution: |
Claims page refreshes to show the updated data after performing the reprocess action. |
||
37020553 |
3-37883444451 |
NXT-30273 |
Referencesheet query api works erroneously in some cases |
Description: |
Referencesheet query api did not return correct result set when a comparison operation like gte or lte was used because the passed value was being interpreted as a string instead of a number |
||
Resolution: |
Referenesheet query api now returns correct result set when a search operation is done using gte or lte comparison operators |
||
37088668 |
NXT-30394 |
Multivalue flexcodes are not working as labels |
|
Description: |
When user adds a multivalue flexcode in Labels section, it is listing blank occurrences instead of actual values |
||
Resolution: |
Multivalue fields can be configured as labels and actual values are shown |
||
37162813 |
NXT-30515 |
Dynamic field usage condition is not being invoked on patch API call |
|
Description: |
Dynamic Field (flex code) Usage Condition is not being invoked on PATCH API call. Creation API invokes successfully the configured Dynamic Field Usage Condition and works per expectation. |
||
Resolution: |
The Dynamic Logic mapped to Dynamic Field (flex code) Usage Condition should be invoked and show the Message mapped on the Dynamic Logic on PATCH API call. |
||