Release Notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.11
This document contains the release notes for Oracle Health Insurance Claims Adjudication Patch 3.22.2.0.11.
| Version compatibility: Oracle Health Insurance Claims Adjudication Release 3.22.2.x is only compatible with other Oracle Health Insurance applications release version 3.22.2.x unless explicitly stated otherwise. |
| 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 | Patch |
|---|---|---|
NXT-25239 |
Non-Unique Relation Identifiers This enhancement introduces a new configuration setting that controls whether a relation identifier is unique across relations. Documentation Links: |
4.23.1.0.0 |
Web Services
| Ref | Action | Description |
|---|---|---|
NXT-25239 |
Modified |
identifiertypes API An identifier type cannot be set to unique when identifiers exist |
NXT-25239 |
Modified |
relationidentifiers API Identifier must be unique when identifier type is set to be unique |
NXT-25239 |
Modified |
Relations IP If more than 1 relation is matched to an identifier, then an error message is thrown |
Data Conversion
| Ref | Action | Description |
|---|---|---|
NXT-25239 |
Added |
Identifier types New column IND_UNIQUE added to REL_IDENTIFIER_TYPES_B with default value set to 'Y' in all the applications except for Policies. |
NXT-25239 |
Removed |
Relation Identifiers Unique constraint on identifier and identifier type is dropped in all the applications except for policies as in policies it was already dropped earlier. |
Bug Fixes
| BugDB | SR | Internal | BP | Summary |
|---|---|---|---|---|
35665839 |
NXT-27416 |
BP |
Creating claims fails when "Claim Code Generation" dynamic logic is executed first time after invalidating dynamic logic cache. |
|
Description: |
Creating claims fails when "Claim Code Generation" dynamic logic is executed first time after invalidating dynamic logic cache. |
|||
Resolution: |
After dynamic logic is invalidated, dynamic logic is queried by code and that does not do an implicit flush. Code will be created with the dynamic logic provided in "Claim Code Generation" |
|||