Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.7

This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.7.

Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.1.x is only compatible with other Oracle Health Insurance applications release version 3.22.1.x unless explicitly stated otherwise.

OHI applications expose the technical ID (created by sequence generator) in HTTP API and IP. This might be changed to an alternate technical ID (the data type might not be an integer) in a future release. Hence, it is advised to follow the generated HATEOAS links instead of hard-coding/bookmarking the IDs in the external integrations.

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

No enhancements.

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 of ohi_install.cfg.template and name it ohi_install.cfg.
Edit ohi_install.cfg to 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:
1. Open a command window and browse to <OHI_ROOT>/util/install.
2. 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

Additional Upgrade Steps for Installation

The following phases are defined:

pre-upgrade: Application is still running
pre-undeploy: Application is stopped, but not undeployed.
post-undeploy: Application is undeployed. Database is backed up
post-upgrade: Released upgrade script has run.
post-deploy: New application is deployed and is up and running.

Stage: pre-upgrade

Note: OHI delivers the new field N1202 with this patch. If record with the code N1202 found in the table cod_fields_b then below script will update the id with the new Id 169150 and its reference in the tables cod_flex_code_field_usages_b and cod_dynamic_field_usages_b.

It is recommended to take the DB backup before running the script.

Please execute the SQL statement with user: OHI_CLAIMS_OWNER.

declare
      l_cod_field_id cod_fields_b.id%type;
begin
      select id into l_cod_field_id from cod_fields_b where code='N1202';
      DBMS_OUTPUT.PUT_LINE ('Updating the id ' || l_cod_field_id || ' of table cod_fields_b for code N1202');
      execute immediate 'alter table cod_fields_tl disable constraint cod_field_tl_fk1';
      execute immediate 'alter table cod_flex_code_field_usages_b disable constraint cod_flex_code_field_use_fk3';
      execute immediate 'alter table cod_dynamic_field_usages_b disable constraint cod_dynamic_field_usage_fk1';
      update cod_fields_b set id = 169150 where id = l_cod_field_id;
      update cod_fields_tl set base_table_id = 169150 where base_table_id = l_cod_field_id;
      update cod_flex_code_field_usages_b set fiel_id = 169150 where fiel_id = l_cod_field_id;
      update cod_dynamic_field_usages_b set fiel_id = 169150 where fiel_id = l_cod_field_id;
      commit;
      execute immediate 'alter table cod_fields_tl enable constraint cod_field_tl_fk1';
      execute immediate 'alter table cod_flex_code_field_usages_b enable constraint cod_flex_code_field_use_fk3';
      execute immediate 'alter table cod_dynamic_field_usages_b enable constraint cod_dynamic_field_usage_fk1';
exception
      when no_data_found then
      DBMS_OUTPUT.PUT_LINE ('Update of the seed data id is skipped as no matching record was found. Please proceed with further upgrade step');
end;
/