Auto Purge Configurations for the Claims Application

Health and Financial Data

Purge Category Description Entities Removed Retention Period Default Enabled

Purge Category	Description	Entities Removed	Retention Period	Default Enabled
Claims	Claims represents a number of healthcare services provided to a patient. This process purges claims that are older than seven years, along with their corresponding records in the claims-transaction repository. This process also removes any associated entities, such as notes.	`Claim` `CtrClaim` `Note` `FinancialHold` `AuthorizationConsumption`	7 years	No
Authorization Operational Data	An insurance carrier can require the insured individual or healthcare provider to get the carrier’s approval before a specific service is rendered. In the Claims, such requests for approval are stored as authorization records. This process includes the removal of authorization records that are older than seven years.	`Authorization`	7 years	No

Claims

Claims represents a number of healthcare services provided to a patient.

This process purges claims that are older than seven years, along with their corresponding records in the claims-transaction repository.

This process also removes any associated entities, such as notes.

Claim
CtrClaim
Note
FinancialHold
AuthorizationConsumption

7 years

Authorization Operational Data

An insurance carrier can require the insured individual or healthcare provider to get the carrier’s approval before a specific service is rendered.

In the Claims, such requests for approval are stored as authorization records.

This process includes the removal of authorization records that are older than seven years.

Authorization

7 years

Operational Data

Internal technical tables can contain personally identifiable information (PII) or protected health information (PHI). This category of data cannot be retained for longer than the retention period for financial or health data. The following are purge options that can be configured to remove operational data at specified intervals:

Purge Category Description Entities Purged Default Retention Period Enabled by Default

Purge Category	Description	Entities Purged	Default Retention Period	Enabled by Default
Activities	An activity is an action or set of actions performed by the application. This purge process removes completed activities along with their associated dynamic data, activity messages, and any related information from technical tables.	`Activity` `ActivityMessage`	60 days	Yes
Tasks and Interfaced Messages	A task represents a unit of work within the system. The application uses a queue-based task distribution and processing mechanism for various processes. Each task is associated with interfaced messages that provide an audit trail for tracking message-based interactions with OHI applications. The purge process removes the tasks, task attributes, and any related interfaced messages.	`Task` `TaskAttribute` `InterfacedMessage` `InterfacedMessageDetail` `DataSetProcess`	60 days	Yes
Replication events	Data replication is the process of synchronizing or duplicating data between two applications. For example, this process is used to replicate a person’s details across applications, with the Policies application serving as the source. Whenever a change occurs, the source application generates a replication event. The target application subscribes to receive these replication events to replicate the changes. This process also purges the replication events from both the source and target applications.	`SourceReplicationEvent` `TargetReplicationEvent`	30 days	Yes
Claims Technical Tables	This process purges technical tables that track external callouts, claims payment statuses, pricing draft provider-pricing clause selections, and fee-schedule lines.		60 days	Yes
Financial technical tables	Generating financial messages and accounting details involves processing financial data derived from the premium calculation and fee generation processes, as well as creating sets of financial transactions. The purge process is used to remove data from technical tables that are used during the generation of financial messages, accounting details, invoices, and invoice lines.		60 days	No

Activities

An activity is an action or set of actions performed by the application.

This purge process removes completed activities along with their associated dynamic data, activity messages, and any related information from technical tables.

Activity
ActivityMessage

60 days

Yes

Tasks and Interfaced Messages

A task represents a unit of work within the system.

The application uses a queue-based task distribution and processing mechanism for various processes.

Each task is associated with interfaced messages that provide an audit trail for tracking message-based interactions with OHI applications.

The purge process removes the tasks, task attributes, and any related interfaced messages.

Task
TaskAttribute
InterfacedMessage
InterfacedMessageDetail
DataSetProcess

60 days

Yes

Replication events

Data replication is the process of synchronizing or duplicating data between two applications.

For example, this process is used to replicate a person’s details across applications, with the Policies application serving as the source.

Whenever a change occurs, the source application generates a replication event.

The target application subscribes to receive these replication events to replicate the changes.

This process also purges the replication events from both the source and target applications.

SourceReplicationEvent
TargetReplicationEvent

30 days

Yes

Claims Technical Tables

This process purges technical tables that track external callouts, claims payment statuses, pricing draft provider-pricing clause selections, and fee-schedule lines.

60 days

Yes

Financial technical tables

Generating financial messages and accounting details involves processing financial data derived from the premium calculation and fee generation processes, as well as creating sets of financial transactions.

The purge process is used to remove data from technical tables that are used during the generation of financial messages, accounting details, invoices, and invoice lines.

60 days

PHI Audit Logs

Audit logs of protected health information (PHI) track user interactions with the application. For cloud customers, after 60 days, these logs move to Oracle-managed object storage and remain there for 7 years.

Purge Category Description Retention Period Default Enabled

Purge Category	Description	Retention Period	Default Enabled
PHI Logs	The application monitors user access and updates to protected health information (PHI) and personally identifiable information (PII) through the HTTP APIs. All HTTP resources that link a person to PHI and all resources that contain PII are monitored. Whenever a user or client application retrieves one of these resources or issues an operation on one of these resources, the application creates an entry in a dedicated PHI log. Instead of purging, this process involves moving the PHI audit logs from the entity `logphievents` to the object storage. After the set retention period, PHI events are purged from the database and moved to a JSON file within OHI managed object storage, where they are retained for seven years.	60 days	Yes

PHI Logs

The application monitors user access and updates to protected health information (PHI) and personally identifiable information (PII) through the HTTP APIs.

All HTTP resources that link a person to PHI and all resources that contain PII are monitored.

Whenever a user or client application retrieves one of these resources or issues an operation on one of these resources, the application creates an entry in a dedicated PHI log.

Instead of purging, this process involves moving the PHI audit logs from the entity logphievents to the object storage.

After the set retention period, PHI events are purged from the database and moved to a JSON file within OHI managed object storage, where they are retained for seven years.

60 days

Yes

Customer Diagnostic Logs

Customer Diagnostic logs contain messages that are generated during software operation.

Purge Category Description Entities Removed Retention Period Default Enabled

Purge Category	Description	Entities Removed	Retention Period	Default Enabled
Application Logs	Application logs contain informational messages, warnings, and errors generated by the Oracle Health Insurance application. This log includes all messages that are not found in the Security log, the PHI log, or the Dynamic Logic log. The process is used to purge application event logs that exceed the set retention period.	`logapplicationevents`	30 days	Yes
Dynamic Logic Logs	The application stores logs created during dynamic logic executions, that is, the logs generated by debug statements within the dynamic logic. This process is used to purge the logs generated during dynamic logic execution.	`logdynamiclogicevents`	30 days	Yes
Operational Reports	The Data Transfer feature enables users to download operational reports in various formats, including CSV, XML, JSON, and Parquet. This process is used to purge any logs generated during this data transfer process for operational reports.		30 days	Yes

Application Logs

Application logs contain informational messages, warnings, and errors generated by the Oracle Health Insurance application.

This log includes all messages that are not found in the Security log, the PHI log, or the Dynamic Logic log.

The process is used to purge application event logs that exceed the set retention period.

logapplicationevents

30 days

Yes

Dynamic Logic Logs

The application stores logs created during dynamic logic executions, that is, the logs generated by debug statements within the dynamic logic.

This process is used to purge the logs generated during dynamic logic execution.

logdynamiclogicevents

30 days

Yes

Operational Reports

The Data Transfer feature enables users to download operational reports in various formats, including CSV, XML, JSON, and Parquet.

This process is used to purge any logs generated during this data transfer process for operational reports.

30 days

Yes

Data Files and Import Data

This log includes two types of data files: those generated automatically by the system and those uploaded by users. The uploaded files are used as inputs to initiate long-running operations within the system.

Purge Category Description Entities Removed Retention Period Default Enabled

Purge Category	Description	Entities Removed	Retention Period	Default Enabled
Data Files	A data file is used to store raw data, which can be either files imported or uploaded by a user or an external application or files created during a process within the application. Examples include files used for file-based import operations such as provider import, financial processing activities, and writing financial messages to a data file set. This process is designed for purging data files that are outside the retention period.	`DataFile` `ImportPolicy` `ImportPolicyUpdateRequest` `ConnectorConfigurationActivity`	60 days	Yes
Import Data	This process is used for purging the technical data generated during the relations and providers import process.		60 days	Yes

Data Files

A data file is used to store raw data, which can be either files imported or uploaded by a user or an external application or files created during a process within the application.

Examples include files used for file-based import operations such as provider import, financial processing activities, and writing financial messages to a data file set.

This process is designed for purging data files that are outside the retention period.

DataFile
ImportPolicy
ImportPolicyUpdateRequest
ConnectorConfigurationActivity

60 days

Yes

Import Data

This process is used for purging the technical data generated during the relations and providers import process.

60 days

Yes