INTRO MISSING. Add in Atlas for Oracle Health Insurance Claims Adjudication 3.22.1.0.12.

Enhancements

ID Summary Patch

AUT-2954

Include JVM GC metrics in Prometheus

Metrics for GC monitoring have been added, controlled by a number of system properties:

JVM metrics are enabled by ohi.instrumentation.gather.jvm (this used to be ohi.instrumentation.gather.jvmtelemetry)

System metrics are enabled by ohi.instrumentation.gather.system (this used to be ohi.instrumentation.gather.jvmtelemetry)

Garbage Collection metrics are enabled by ohi.instrumentation.gather.gc

3.22.2.0.3

Upgrade Steps for Installation

To perform the upgrade, perform the following steps:

  1. Perform any pre-upgrade steps.

  2. Stop all the managed nodes running the .existing version of the application.

  3. Perform any pre-undeploy steps.

  4. Undeploy the existing version of the application.

  5. Back up the database.

  6. Perform any post-undeploy steps.

  7. Unpack the release bundle into a directory that we refer to as OHI_ROOT from now on.

  8. Change Installation Configuration: In <OHI_ROOT>/util/install, make a copy of ohi_install.cfg.template and name it ohi_install.cfg.

  9. Edit ohi_install.cfg to contain your specific database connection data and other configuration settings. The settings are explained in the file itself.

  10. Make sure NO connections are present to the database using the OHI_xxx_USER account (where xxx is the abbreviation of the application)

  11. Run the Upgrade script:

    1. Open a command window and browse to <OHI_ROOT>/util/install.

    2. Run the upgrade by executing ./ohi-update.sh .

  12. Make the required changes to the ohi properties file

  13. Perform any post-upgrade steps

  14. Start WebLogic application server

  15. Deploy the Application

  16. Perform any post-deploy steps

Configuration Properties

This section intentionally left blank.

Web Services

This section intentionally left blank.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref Action Description

NXT-26785

Added

Adjudication Limit Counters

Added new JET UI Page.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

This section intentionally left blank.

Bug Fixes

BugDB SR Internal BP Summary

34882273

3-31454344411

NXT-26038

BP

Covered Amount is set to null on claim line when line is denied with fatal message

Description:

Covered Amount set to null on claim line when line is denied with fatal message at Manual Adjudication

Resolution:

On a denied claim the total covered amount is set to zero in the default currency. On an approved claim that includes claim lines with covered amounts in different currencies, the total covered amount and currency is left empty, i.e., set to null.

35043763

3-31945494731

NXT-26346

BP

Time-Valid flex codes are not showing nested properties

Description:

Flex codes configured under procedure is not showing up in Claim lines.

Resolution:

Users can now configure a floorplan at claim lines level for flex codes configured under procedure level.

34979337

3-31477093221

NXT-26207

BP

Financial message not created for reversal transactions when covered amount on claim is null

Description:

If a claim processing involves currency conversion, a manual fatal message attached to the claim/claim lines can cause covered amount and covered amount currency (on claim and claim line) to be null.

Resolution:

Financial messages for reversal transactions are now created when covered amount on the claim is null.

35109398

3-32181209591

NXT-26501

BP

Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes

Description:

Assigned column name of flex code field usage when creating it from ADF UI is not correct sometimes

Resolution:

The column name which was assigned while creating a flex code field usage after an error message was thrown, was incorrect. After the correct columnName is assigned, the deletion of dynamic records using method deleteDynamicRecord on key value works fine.

35130259

3-32265793401

NXT-26533

BP

CLA - JET UI : The placing of decimal point is different in JET and ADF

Description:

For any scalar dynamic field in the response data for an entity, the value always came as a string "BigDecimalDynField": "12.34". but expected is "BigDecimalDynField": 12.34.

Resolution:

ScalarAttributeGetHandler did not resolve the value for the dynamicFieldObject earlier, now it extracts the value of from a dynamicFieldObject to basic datatype like BigDecimal, integer etc.

35175270

3-32295832461

NXT-26625

BP

Translatable attributes of flex codes are not migrated for all the installed languages using CMT

Description:

Translatable attributes of flex codes are not migrated for all the installed languages using CMT

Resolution:

Translatable attributes of flex codes for all the installed languages are now migrated using CMT. Earlier, these variables were updated based on their source language that was causing conflicts. The fix now updates variables based on their current language.

35233829

NXT-26703

BP

Dynamic records for Specialty is not working

Description:

Dynamic records for Specialty is not working due to which user cannot find it in view objects .

Resolution:

This is resolved and we can see the dynamic records for Specialty in view objects .

Issues that were backported in previous Release / Patch

No backports.