Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.1.0.5

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

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.

As per the Service Description, you are obligated to request a service upgrade within 90 days of this release being generally available (GA). In line with the Oracle Cloud Services Pillar document, Section 4.2.2 End of Life, this release will be EOL in 12 months.

Enhancements

ID	Summary	Description	Included in Patch
POL-11138	Extend Extract Integration Point	This enhancement extends the extract Integration Point to include dynamic record identifiers.

Summary

Description

Included in Patch

POL-11138

Extend Extract Integration Point

This enhancement extends the extract Integration Point to include dynamic record identifiers.

Configuration Properties

Ref	Action	Subject	Description
NXT-25298	Added	ohi.datareplication.event.retrieval.max.numberofretries	The maximum number of times the target system will try to connect to the source system to retrieve the events. Default value is 3

Ref

Action

Subject

Description

NXT-25298

Added

ohi.datareplication.event.retrieval.max.numberofretries

The maximum number of times the target system will try to connect to the source system to retrieve the events. Default value is 3

Web Services

Ref	Action	Subject	Description
POL-11138	Modified	Extract Integration Point	The extract Integration Point now exposes the identifiers of the dynamic records.

Ref

Action

Subject

Description

POL-11138

Modified

Extract Integration Point

The extract Integration Point now exposes the identifiers of the dynamic records.

Data Conversion

This section intentionally left blank.

Dynamic Logic

This section intentionally left blank.

UI Changes

Ref	Action	Subject	Description
NXT-25334	Modified	claimline	Claimline page is not opening while viewing a ctr version

Ref

Action

Subject

Description

NXT-25334

Modified

claimline

Claimline page is not opening while viewing a ctr version

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
34113658		NXT-24625	BP	External consumptions updating counter periods erroneously
Description:	When there is an existing counter period for certain product/provider, creating a new external consumption without provider or product information and different service date year for limits that counts per provider and/or per product updates all the counter periods in the counter to count across provider/product. Additionally it deletes existing counter period which was counting per product/provider. Newly created counter period doesn’t count toward any provider/product and also doesn’t counter consumption of deleted counter period.
Resolution:	To avoid the deletion of counter period which count per product/provider and updating all the counter periods of different durations, added certain conditions before creating counter period: - When limits mentioned in external consumption counts per product and per provider and there is no matching counter periods for input data, then aggregation level (product) and provider must be passed as input to create new counter period. - When limit mentioned in external consumption counts per product and across provider and there is no matching counter periods for input data, then aggregation level (product) must be passed in consumption to create new counter period. - When limit mentioned in external consumption counts per provider and across product and there is no matching counter periods for input data, then provider must be passed in consumption to create new counter period. - When limit mentioned in external consumption counts across provider and across product, new counter period is created if there isn’t any matching counter period for given service date.
34560671	3-30514806081	NXT-25334	BP	Claimline page is not opening while viewing a ctr version
Description:	Claimline details page is not opening when we try to open the the claimline page for a CTR claim
Resolution:	Claim line detail page can be viewed without any issues for a CTR claim
34573913	3-30514720151	NXT-25357	BP	Version dropdown list is showing reversal versions in Claim Details page
Description:	In the Jet UI, on the claims page a version drop down list is shown. the dropdown showing all the transactions instead of showing only the non-reversed transactions. Showing reversal versions is redundant; the drop down list should not include reversals.
Resolution:	Versions dropdown shows only the non-reversal transactions in Claims page
34464604	3-30244018461	NXT-25207	BP	LOV values are not displaying comma separated in Edit mode
Description:	The Title property configured with sequence setting 2 in LOV is not showing up in Edit mode of the page.
Resolution:	LOV values are displayed as comma separated in Edit mode when there are more than 1 title properties configured in the LOV floorplan
34568511		NXT-25344	BP	In Tab Table, if multiple records are created by enabling deeplink on any column, save button freezes
Description:	In tab table, enabling deeplink and adding multiple records will not let the user to save the page and no error is thrown either.
Resolution:	The user is allowed to save tab table records with deeplink enabled in the properties, even when multiple rows added at a time
34464570	3-30244018461	NXT-25205	BP	Several issues with editing and submitting the claims
Description:	Not able to save a claim after editing the claim line, not able to add a new claimline. Attach and 'Attach and Next' buttons do not work. Not able to navigate from one claimline to another claimline using previous and next button.
Resolution:	Previous and Next buttons working fine in Claimlines page. Multiple claimlines can be added, edited. It is also possible to navigate without issues between claimlines. 'Attach' and 'Attach and Next' buttons are working in Claimlines page Note: sequence is not getting generated automatically as of now, will be fixed in next patch
34531522	3-29586002911	NXT-25298	BP	Data Replication target should check for the availability of the source system
Description:	When the source system is not available for a few milliseconds then the target system is responding with HTTP 503 which results in Service Unavailable and failing of the replication activities.
Resolution:	Now when the source system is not available for the first time target system will retry the connectivity for the Source based on a system property with a time interval.
34588062	3-30625249401	NXT-25391	BP	Reference Property defaults do not work with display type never setting
Description:	Reference Property defaults do not work with display type never setting. Setting default on a mandatory field like Languages in Persons page with display 'never' setting doesn’t work and on saving the record an error is thrown that Language is mandatory for Person entity
Resolution:	Reference Property defaults work with display type never setting on fixed fields related to an entity.

BugDB

Internal

Summary

34113658

NXT-24625

External consumptions updating counter periods erroneously

Description:

When there is an existing counter period for certain product/provider, creating a new external consumption without provider or product information and different service date year for limits that counts per provider and/or per product updates all the counter periods in the counter to count across provider/product. Additionally it deletes existing counter period which was counting per product/provider. Newly created counter period doesn’t count toward any provider/product and also doesn’t counter consumption of deleted counter period.

Resolution:

To avoid the deletion of counter period which count per product/provider and updating all the counter periods of different durations, added certain conditions before creating counter period: - When limits mentioned in external consumption counts per product and per provider and there is no matching counter periods for input data, then aggregation level (product) and provider must be passed as input to create new counter period. - When limit mentioned in external consumption counts per product and across provider and there is no matching counter periods for input data, then aggregation level (product) must be passed in consumption to create new counter period. - When limit mentioned in external consumption counts per provider and across product and there is no matching counter periods for input data, then provider must be passed in consumption to create new counter period. - When limit mentioned in external consumption counts across provider and across product, new counter period is created if there isn’t any matching counter period for given service date.

34560671

3-30514806081

NXT-25334

Claimline page is not opening while viewing a ctr version

Description:

Claimline details page is not opening when we try to open the the claimline page for a CTR claim

Resolution:

Claim line detail page can be viewed without any issues for a CTR claim

34573913

3-30514720151

NXT-25357

Version dropdown list is showing reversal versions in Claim Details page

Description:

In the Jet UI, on the claims page a version drop down list is shown. the dropdown showing all the transactions instead of showing only the non-reversed transactions. Showing reversal versions is redundant; the drop down list should not include reversals.

Resolution:

Versions dropdown shows only the non-reversal transactions in Claims page

34464604

3-30244018461

NXT-25207

LOV values are not displaying comma separated in Edit mode

Description:

The Title property configured with sequence setting 2 in LOV is not showing up in Edit mode of the page.

Resolution:

LOV values are displayed as comma separated in Edit mode when there are more than 1 title properties configured in the LOV floorplan

34568511

NXT-25344

In Tab Table, if multiple records are created by enabling deeplink on any column, save button freezes

Description:

In tab table, enabling deeplink and adding multiple records will not let the user to save the page and no error is thrown either.

Resolution:

The user is allowed to save tab table records with deeplink enabled in the properties, even when multiple rows added at a time

34464570

3-30244018461

NXT-25205

Several issues with editing and submitting the claims

Description:

Not able to save a claim after editing the claim line, not able to add a new claimline. Attach and 'Attach and Next' buttons do not work. Not able to navigate from one claimline to another claimline using previous and next button.

Resolution:

Previous and Next buttons working fine in Claimlines page. Multiple claimlines can be added, edited. It is also possible to navigate without issues between claimlines. 'Attach' and 'Attach and Next' buttons are working in Claimlines page Note: sequence is not getting generated automatically as of now, will be fixed in next patch

34531522

3-29586002911

NXT-25298

Data Replication target should check for the availability of the source system

Description:

When the source system is not available for a few milliseconds then the target system is responding with HTTP 503 which results in Service Unavailable and failing of the replication activities.

Resolution:

Now when the source system is not available for the first time target system will retry the connectivity for the Source based on a system property with a time interval.

34588062

3-30625249401

NXT-25391

Reference Property defaults do not work with display type never setting

Description:

Reference Property defaults do not work with display type never setting. Setting default on a mandatory field like Languages in Persons page with display 'never' setting doesn’t work and on saving the record an error is thrown that Language is mandatory for Person entity

Resolution:

Reference Property defaults work with display type never setting on fixed fields related to an entity.

Issues that were backported in previous Release / Patch

No backports.