Release Notes for Oracle Health Insurance Authorizations Release 3.21.2.0.0

This document contains the release notes for Oracle Health Insurance Authorizations Release 3.21.2.0.0.

NOTE: Version compatibility: Oracle Health Insurance Authorizations Release 3.21.2.x is only compatible with other Oracle Health Insurance applications release version 3.21.2.x unless explicitly stated otherwise.
NOTE: 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	Description
NXT-21417	PHI Audit logs must be written in the same transaction as PHI / PII access occurs	PHI logs were initially written to a local buffer file before being persisted in the database. For compliance it is required to persist PHI audit logs in the same transaction as PHI access occurs. If system property 'ohi.logging.target' is set to value 'database', OHI applications persist PHI access in the database as part of the HTTP API or ADF UI request in which PHI data was accessed. If the value for system property 'ohi.logging.target' is set to 'log', which is also the default if no value is specified, then PHI access continues to be logged using any configured Logback Appender for which the PHI filter is applied.
NXT-21687	Extend the length of Relation and Provider Identifier	This enhancement focuses on increasing the length of the Relation and Provider Identifiers from 30 to 100 char.Increased the length of the Identifier attribute from 30 to 100 char on the Relation Identifier entity. Increased the length of the Identifier attribute from 30 to 100 char on the Provider Identifier entity.
NXT-21831	CMT: Order of dynamic logic import	Before this release, in CMT, the dynamic logic were imported in a random order (because they all have the same execution rank). With the introduction of two new signatures "Extension" and "Reusable Code", it is important and also possible that the dynamic logic are imported in an order to prevent look up failures while importing. With this enhancement, dynamic logic will now be imported in the following order of signatures: 1) Reusable Code 2) All the other dynamic logic except "Extension" 3) Extension
POL-6890	Retire Address Type Domain	In release 3.21.1, the fixed address type domain was replaced by a user configurable address type domain as a separate entity. The integration points and API supported both versions. From this release, the type attribute is removed.
POL-7886	Extend dynamic Fields on Relation	The number of supported dynamic fields on relations entity are now increased from Small to Medium (which has - among others - 20 character dynamic fields)

Summary

Description

Included in Patch

NXT-21417

PHI Audit logs must be written in the same transaction as PHI / PII access occurs

PHI logs were initially written to a local buffer file before being persisted in the database. For compliance it is required to persist PHI audit logs in the same transaction as PHI access occurs. If system property 'ohi.logging.target' is set to value 'database', OHI applications persist PHI access in the database as part of the HTTP API or ADF UI request in which PHI data was accessed. If the value for system property 'ohi.logging.target' is set to 'log', which is also the default if no value is specified, then PHI access continues to be logged using any configured Logback Appender for which the PHI filter is applied.

NXT-21687

Extend the length of Relation and Provider Identifier

This enhancement focuses on increasing the length of the Relation and Provider Identifiers from 30 to 100 char.Increased the length of the Identifier attribute from 30 to 100 char on the Relation Identifier entity. Increased the length of the Identifier attribute from 30 to 100 char on the Provider Identifier entity.

NXT-21831

CMT: Order of dynamic logic import

Before this release, in CMT, the dynamic logic were imported in a random order (because they all have the same execution rank). With the introduction of two new signatures "Extension" and "Reusable Code", it is important and also possible that the dynamic logic are imported in an order to prevent look up failures while importing. With this enhancement, dynamic logic will now be imported in the following order of signatures:
1) Reusable Code
2) All the other dynamic logic except "Extension"
3) Extension

POL-6890

Retire Address Type Domain

In release 3.21.1, the fixed address type domain was replaced by a user configurable address type domain as a separate entity. The integration points and API supported both versions. From this release, the type attribute is removed.

POL-7886

Extend dynamic Fields on Relation

The number of supported dynamic fields on relations entity are now increased from Small to Medium (which has - among others - 20 character dynamic fields)

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.

The OHI Logback Database Appender can no longer be configured for logType 'phi'. Remove any appender of class 'com.oracle.healthinsurance.loggingsupport.appender.impl.OhiAppender' for logType 'phi' from the Logback configuration. To continue persisting PHI access in the database, set system property 'ohi.logging.target' to value 'database'. Note that use of the appender of class 'com.oracle.healthinsurance.loggingsupport.appender.impl.OhiAppender' for logType 'application' or logType 'dylo' is unaffected.

Run the following SQL statement as ohi_auths_owner and commit any changes:

update log_phi_events
set    event_doc =
json_mergepatch(
json_mergepatch(
nvl(event_doc, '{}'), json_object('sourceapp' value nvl(json_value(event_doc, '$.sourceapp' returning varchar2(30 char)), 'authorizations'))
), json_object('sourceappversion' value nvl(json_value(event_doc, '$.sourceappversion' returning varchar2(60 char)), 'pre-3.21.1.0.0'))
)
where  virtual_application is null
or     virtual_application_version is null;

Configuration Properties

Ref	Action	Subject	Description
NXT-21417	Added	ohi.logging.target	Defines the target for logging PHI access. Possible values are 'database', for logging to the database, or 'log' for logging PHI access to the Logback appender configured for it. Default value is 'log'.

Ref

Action

Subject

Description

NXT-21417

Added

ohi.logging.target

Defines the target for logging PHI access. Possible values are 'database', for logging to the database, or 'log' for logging PHI access to the Logback appender configured for it. Default value is 'log'.

Web Services

Ref	Action	Subject	Description
NXT-21417	Modified	logphievents API	The following attributes are removed: eventDoc; eventTimestamp; eventLevel; eventThread; contextItemId; contextItemType
NXT-21687	Modified	Relation Integration Point	The length of identifier attribute of relation identifier is extended to 100 characters
NXT-21687	Modified	Provider Integration Point	The length of identifier attribute of provider identifier is extended to 100 characters
POL-6890	Modified	relations API	The type attribute is removed
POL-6890	Modified	addresses API	The type attribute on address is removed
POL-6890	Modified	Relation Integration Point	The type attribute on address is removed

Ref

Action

Subject

Description

NXT-21417

Modified

logphievents API

The following attributes are removed: eventDoc; eventTimestamp; eventLevel; eventThread; contextItemId; contextItemType

NXT-21687

Modified

Relation Integration Point

The length of identifier attribute of relation identifier is extended to 100 characters

NXT-21687

Modified

Provider Integration Point

The length of identifier attribute of provider identifier is extended to 100 characters

POL-6890

Modified

relations API

The type attribute is removed

POL-6890

Modified

addresses API

The type attribute on address is removed

POL-6890

Modified

Relation Integration Point

The type attribute on address is removed

Data Conversion

Ref	Action	Subject	Description
NXT-21417	Modified	Log PHI Events	Newly added attributes are derived from event_doc

Ref

Action

Subject

Description

NXT-21417

Modified

Log PHI Events

Newly added attributes are derived from event_doc

Dynamic Logic

This section intentionally left blank.

UI Changes

This section intentionally left blank.

Deprecated items (to be removed in future release)

This section intentionally left blank.

Breaking Changes

Ref	Action	Subject	Description
NXT-21417	Modified	log_phi_events	Column event_doc is removed
POL-6890	Modified	relations API	The type attribute on address is removed
POL-6890	Modified	addresses API	The type attribute is removed
POL-6890	Modified	Relation Integration Point	The type attribute on address is removed

Ref

Action

Subject

Description

NXT-21417

Modified

log_phi_events

Column event_doc is removed

POL-6890

Modified

relations API

The type attribute on address is removed

POL-6890

Modified

addresses API

The type attribute is removed

POL-6890

Modified

Relation Integration Point

The type attribute on address is removed

Bug Fixes

BugDB	SR	Internal	BP	Summary
32334690	3-24738743651	AUT-1973		Dynamic records not exported in excel
Description:	Dynamic column value at column level not displayed in exported excel
Resolution:	Dynamic record columns will now be listed in excel.
32469420		AUT-2023		Task is stuck in 'PROCESSING' status if the node leaves the cluster
Description:	When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the status of the task remains in 'PROCESSING' status. The other nodes in the cluster should have recovered/requeued that task.
Resolution:	When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster.
32477035		AUT-2027		With clicking Next button dialog button not refreshed
Description:	In Popup dialogs, Next and previous button doesn’t work due to refresh issue.
Resolution:	With the refresh issue fix, Next and Previous button displays appropriate results.
32525615		AUT-2042		Usage Names with a reserved SQL word result in view generation failure
Description:	A usage name like "level" (which is a SQL reserved word) results in a failure in the view generator for the table where this usage is used.
Resolution:	Usage name like "level" which are SQL reserved words no longer create failure in view generation.
32555703		AUT-2057		Baseview generation sometimes might result in error: ORA-01461
Description:	This happens occasionally when generating baseviews. An error similar to the one described below is emitted to the application logfile: java.sql.SQLException: ORA-12801: error signaled in parallel query server P007 ORA-01461: can bind a LONG value only for insert into a LONG column
Resolution:	There is a workaround for this. In the event that this happens, typically resubmitting the generation process resolves the problem.
32567704		AUT-2060		Configure ohi.resource.client.timer Resource Tag construction
Description:	For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).
Resolution:	The new system property "ohi.instrumentation.resourceclienttimer.segment.prefixes" provides control in determining the resource tag value for an "ohi.resource.client.timer".
32581680		AUT-2061		Create-form link shall not be available for baseviews, baseviewgeneration and baseviewcolumn resources
Description:	Before this release, create-form link is visible for baseviews, baseviewgeneration and baseviewcolumn resources. Also baseviewerrors is not listed as a resource.
Resolution:	Create-form links for baseviews, baseviewgeneration and baseviewcolumn resources are removed. Baseviewerrors resource is now listed as a resource.
-		AUT-2069	BP	CMT data set containing flex codes systems and flex codes take more time than 3.20.2.0.0
Description:	CMT data set containing flex codes systems and flex codes take more time than 3.20.2.0.0 release.
Resolution:	The performance of importing flex codes through CMT is optimized now.
32638193		AUT-2071		CMT-Code and Descriptions fields values were getting cleared While Creating new set With Multiple configuration Items with Exclude Option.
Description:	Code and Descriptions fields values were getting cleared if we select an exclude option and then select something in the Configuration Items
Resolution:	partial trigger was not handled properly , now the ui doesn’t get reloaded partially every time we select the new Configuration item

BugDB

Internal

Summary

32334690

3-24738743651

AUT-1973

Dynamic records not exported in excel

Description:

Dynamic column value at column level not displayed in exported excel

Resolution:

Dynamic record columns will now be listed in excel.

32469420

AUT-2023

Task is stuck in 'PROCESSING' status if the node leaves the cluster

Description:

When the node processing a task leaves the cluster or if the node is stopped while the task is being processed, then the status of the task remains in 'PROCESSING' status. The other nodes in the cluster should have recovered/requeued that task.

Resolution:

When a node leaves the cluster, then the tasks that are currently being processed by that node are now recovered by the other node(s) in the cluster.

32477035

AUT-2027

With clicking Next button dialog button not refreshed

Description:

In Popup dialogs, Next and previous button doesn’t work due to refresh issue.

Resolution:

With the refresh issue fix, Next and Previous button displays appropriate results.

32525615

AUT-2042

Usage Names with a reserved SQL word result in view generation failure

Description:

A usage name like "level" (which is a SQL reserved word) results in a failure in the view generator for the table where this usage is used.

Resolution:

Usage name like "level" which are SQL reserved words no longer create failure in view generation.

32555703

AUT-2057

Baseview generation sometimes might result in error: ORA-01461

Description:

This happens occasionally when generating baseviews.

An error similar to the one described below is emitted to the application logfile:

java.sql.SQLException: ORA-12801: error signaled in parallel query server P007 ORA-01461: can bind a LONG value only for insert into a LONG column

Resolution:

There is a workaround for this. In the event that this happens, typically resubmitting the generation process resolves the problem.

32567704

AUT-2060

Configure ohi.resource.client.timer Resource Tag construction

Description:

For gathering metrics, it must be possible to control the resource tag for an "ohi.resource.client.timer" to point to the name of the resource (and not be more specific than that).

Resolution:

The new system property "ohi.instrumentation.resourceclienttimer.segment.prefixes" provides control in determining the resource tag value for an "ohi.resource.client.timer".

32581680

AUT-2061

Create-form link shall not be available for baseviews, baseviewgeneration and baseviewcolumn resources

Description:

Before this release, create-form link is visible for baseviews, baseviewgeneration and baseviewcolumn resources. Also baseviewerrors is not listed as a resource.

Resolution:

Create-form links for baseviews, baseviewgeneration and baseviewcolumn resources are removed. Baseviewerrors resource is now listed as a resource.

AUT-2069

CMT data set containing flex codes systems and flex codes take more time than 3.20.2.0.0

Description:

CMT data set containing flex codes systems and flex codes take more time than 3.20.2.0.0 release.

Resolution:

The performance of importing flex codes through CMT is optimized now.

32638193

AUT-2071

CMT-Code and Descriptions fields values were getting cleared While Creating new set With Multiple configuration Items with Exclude Option.

Description:

Code and Descriptions fields values were getting cleared if we select an exclude option and then select something in the Configuration Items

Resolution:

partial trigger was not handled properly , now the ui doesn’t get reloaded partially every time we select the new Configuration item

Issues that were backported in previous Release / Patch

No backports.

Known Issues

BugDB	SR	Internal	Summary
26392920		AUT-1041	ACCESS - Focus does not reach the overflow icon
Description:	On navigating via the keyboard on persons page, the focus does not reach the overflow icon for existing records.
26392938		AUT-1042	ACCESS : Unopened child sections are not accessible using keyboard
Description:	The user is not able to access unopened child sections using only the keyboard. The user should be able to use all the links, sections and functionalities just by a keyboard.
26393635		AUT-1044	ACCESS - ALT text is missing for all the images in the documentation. And hence the images are not recognized by JAWS screen reader.
Description:	ALT text is missing for all the images in the document. And hence the images are not recognized by JAWS screen reader.
31533939		AUT-1764	ACCESS : Application does not support the portrait mode of the screen.
Description:	The application needs to support portrait mode as well as landscape mode. Currently, the application does not support when the application is used in portrait mode of the screen.
32477606		AUT-2029	No Base View generated for Reference Sheet Lines
Description:	Reference sheet(line)s use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So the reference sheet line columns can’t be queried using base views.
26391698		AUT-680	Access : Documentation : No summary was defined for data table
Description:	No summary defined for the data table in the documents.
26391717		AUT-681	Access - Documentation - Header cell is not the First row and not scoped
Description:	The header cell is not the first row/column and is not scoped for the documents
25437440		AUT-690	ACCESS : Focus should first come to the left hand side menu
Description:	When using the tab the focus should come to the left-hand side menu first instead It’s going towards the right
25437457		AUT-691	ACCESS : CTRL+INS+I shortcut for list items does not work
Description:	List items on the page are not displayed using the CTRIL+INS+I shortcut.
25466241		AUT-716	ACCESS: The Close tab 'X' icon is not accessible via keyboard navigation
Description:	The 'x' icon of any opened page is not accessible if using only Tab (keyboard) navigation.
25466259		AUT-721	ACCESS: Jump to line functionality of JAWS (Screen reader) doesn’t work.
Description:	The user is not able to use the Jump to line functionality of JAWS which enables the user to navigate to a specific line/attribute based on its unique number.
25466274		AUT-722	ACCESS: DOCUMENT TESTING: The page address link is read as page title using assistive technology (JAWS)
Description:	The assistive technology (JAWS) should read 'OHI Authorizations' as the title instead it’s reading the page address link as the title.
25466289		AUT-725	ACCESS: Persons and Organizations page overflow icon is not accessible
Description:	Persons and organizations page overflow icon is not accessible using only a keyboard.
25466288		AUT-726	ACCESS : DOCUMENTATION TESTING : The table is showing rows with the headers
Description:	The documents are showing the rows without the headers for a table. For some of the tables, a header is not defined.
25466283		AUT-727	ACCESS : Documentation testing : Graphical images are not detected by assistive technology (JAWS)
Description:	Assistive technology (JAWS) is not able to detect available graphical images on any page in the documents.

BugDB

Internal

Summary

26392920

AUT-1041

ACCESS - Focus does not reach the overflow icon

Description:

On navigating via the keyboard on persons page, the focus does not reach the overflow icon for existing records.

26392938

AUT-1042

ACCESS : Unopened child sections are not accessible using keyboard

Description:

The user is not able to access unopened child sections using only the keyboard. The user should be able to use all the links, sections and functionalities just by a keyboard.

26393635

AUT-1044

ACCESS - ALT text is missing for all the images in the documentation. And hence the images are not recognized by JAWS screen reader.

Description:

ALT text is missing for all the images in the document. And hence the images are not recognized by JAWS screen reader.

31533939

AUT-1764

ACCESS : Application does not support the portrait mode of the screen.

Description:

The application needs to support portrait mode as well as landscape mode. Currently, the application does not support when the application is used in portrait mode of the screen.

32477606

AUT-2029

No Base View generated for Reference Sheet Lines

Description:

Reference sheet(line)s use a different storage structure (JSON) for the dynamic fields. The base view generator does not support that yet. So the reference sheet line columns can’t be queried using base views.

26391698

AUT-680

Access : Documentation : No summary was defined for data table

Description:

No summary defined for the data table in the documents.

26391717

AUT-681

Access - Documentation - Header cell is not the First row and not scoped

Description:

The header cell is not the first row/column and is not scoped for the documents

25437440

AUT-690

ACCESS : Focus should first come to the left hand side menu

Description:

When using the tab the focus should come to the left-hand side menu first instead It’s going towards the right

25437457

AUT-691

ACCESS : CTRL+INS+I shortcut for list items does not work

Description:

List items on the page are not displayed using the CTRIL+INS+I shortcut.

25466241

AUT-716

ACCESS: The Close tab 'X' icon is not accessible via keyboard navigation

Description:

The 'x' icon of any opened page is not accessible if using only Tab (keyboard) navigation.

25466259

AUT-721

ACCESS: Jump to line functionality of JAWS (Screen reader) doesn’t work.

Description:

The user is not able to use the Jump to line functionality of JAWS which enables the user to navigate to a specific line/attribute based on its unique number.

25466274

AUT-722

ACCESS: DOCUMENT TESTING: The page address link is read as page title using assistive technology (JAWS)

Description:

The assistive technology (JAWS) should read 'OHI Authorizations' as the title instead it’s reading the page address link as the title.

25466289

AUT-725

ACCESS: Persons and Organizations page overflow icon is not accessible

Description:

Persons and organizations page overflow icon is not accessible using only a keyboard.

25466288

AUT-726

ACCESS : DOCUMENTATION TESTING : The table is showing rows with the headers

Description:

The documents are showing the rows without the headers for a table. For some of the tables, a header is not defined.

25466283

AUT-727

ACCESS : Documentation testing : Graphical images are not detected by assistive technology (JAWS)

Description:

Assistive technology (JAWS) is not able to detect available graphical images on any page in the documents.