Release Notes for Oracle Health Insurance Authorizations Patch 4.25.1.0.5
This document contains the release notes for Oracle Health Insurance Authorizations Patch 4.25.1.0.5.
| Version compatibility: Oracle Health Insurance Authorizations 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 |
|---|---|---|
AUT-4851 |
Authorization Code Sequence This enhancement introduces an alternative way to generate authorization codes for newly created authorizations. It involves implementing a feature already present in Policies |
|
NXT-33004 |
Copy Action for Duplicating Records on HRR Pages The Copy Action is available when the metadata indicates that cloning is supported for a resource. It allows users to quickly duplicate an existing record by providing a new functional key. The system pre-fills the remaining values from the original record (excluding system-generated fields), allowing users to modify and save the new record while keeping the original record unchanged. During cloning, the following child entities are not copied: User Roles for Access Roles, Relation Identifiers for Persons, and Provider Limit Rules for Provider Limit Categories. Modifying individual child records during the clone operation is currently not supported for Access Restriction Grants under Access Roles, Partial Provider Pricing Clauses under Pricing Options, and Diminishing Rate Blocks, along with nested block amount and size lists, under Diminishing Rates. |
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
Web Services
| Ref | Action | Description |
|---|---|---|
AUT-4851 |
Added |
User Defined Sequences Resource to maintain user defined sequences. |
UI Changes
| Ref | Action | Description |
|---|---|---|
AUT-4851 |
Added |
User Defined Sequences UI page to define user defined sequences |
Access Restrictions
| Ref | Action | Description |
|---|---|---|
AUT-4851 |
Added |
CO0046 Access required for managing User Sequence |
Bug Fixes
| BugDB | SR | Internal | Summary |
|---|---|---|---|
38531048 |
AUT-4248 |
Data File Sets IP does not return the message text in the response for error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014 |
|
Description: |
When encountering error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014, the associated error messages are not being displayed in the response. The expected behaviour is that the error messages corresponding to these error codes should be returned in the response, providing more context and information about the error |
||
Resolution: |
The Data File Sets integration point returns the message text associated with error codes DAT-IP-DAFI-013 and DAT-IP-DAFI-014. |
||
39079661 |
4-0001784507 |
AUT-4646 |
System throwing NullPointerException when there is no value for EXCL_PHI_LOGGING in the OHI_REPORTING_VIEWS table |
Description: |
When invoking the Data Transfer IP, the system verifies if any PHI information is fetched and creates PHI log entries when needed. In case the EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table is empty, the system throws a NullPointerException. |
||
Resolution: |
The EXCL_PHI_LOGGING column in the OHI_REPORTING_VIEWS table gets a default value 'N' |
||
39828838 |
4-0003326305 |
AUT-4945 |
Reference sheet lines remain unavailable after creating flex codes removed through CMT |
Description: |
Reference sheet lines are not returned when they reference a flex code that was missing during an earlier lookup and is subsequently created. The missing lookup result remains cached, so the reference sheet lines remain unavailable until the affected application nodes are restarted. |
||
Resolution: |
When a previously missing flex code is created, its flex-code lookup is refreshed. Associated reference sheet lines are returned without restarting application nodes. |
||
39972542 |
4-0003656939 |
AUT-5042 |
File is not downloaded in Reference sheet lines page |
Description: |
Download option not working for Reference sheet lines. When clicking on Download option getting error and lines are not getting downloaded. |
||
Resolution: |
Able to download csv file in Reference sheet lines page. |
||
40088981 |
AUT-5152 |
Prevent application startup stall caused by Coherence cache initialization |
|
Description: |
During application startup, the plan manager could remain blocked while accessing a shared cache. This could prevent a node from completing startup and processing cluster communication. |
||
Resolution: |
The application now loads the plan cache only when needed, preventing startup stalls and allowing the node to process messages from other nodes and complete initialization. |
||
39834097 |
4-0003422821 |
AUT-4950 |
Cleared dynamic fields could still return the previous value during the same processing flow. |
Description: |
When a dynamic field was cleared by assigning null, the value was removed, but a cached copy could still be used for later reads in the same flow. As a result, the dynamic field could appear to still contain its old value immediately after being cleared. This could affect dynamic fields, including flex-code dynamic fields, across single-value time valid, multi-value non-time-valid & time-valid, configurations. |
||
Resolution: |
The cache is now invalidated when a dynamic field is cleared. After assigning null, later reads correctly and returns no value instead of the previously cached value. |
||
39835731 |
AUT-4953 |
Writing incident data files in Object Storage fails intermittently |
|
Description: |
Writing an incident data file in Object Storage fails intermittently with NoSuchElementException |
||
Resolution: |
The intermittent issue that prevented incident data files from being written to Object Storage has been resolved. The fix improves the reliability of file creation and storage operations. |
||
39020584 |
4-0002127328 |
AUT-4611 |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread |
Description: |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread. This resulted in import registration failures, failure observed at weblogic operation at time of publishing event. |
||
Resolution: |
Object storage operation cause assert or Weblogic asserts at event publishing time in absence of missing class loader context in underlying thread. Issue has been fixed by ensuring class loader context is always initialized |
||
40068236 |
4-0002548324 |
AUT-5076 |
Automatic recovery can fail to identify the latest errored task |
Description: |
When an earlier task has a higher identifier than a more recently created task, automatic recovery can fail to identify and recover the latest errored task. |
||
Resolution: |
Retrieval of errored tasks is optimized and based on latest creation date. |
||