Auto Purge Configurations for Policies Application
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 purge options are available, which can be configured to remove operational data at specified intervals.
| 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. |
|
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. |
|
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. |
|
30 days |
Yes |
Outbound messages |
Outbound RESTful service invocations are used to call RESTful services from other applications or systems, or to send notifications and messages to external RESTful systems. This purge process is implemented to remove the outbound messages generated by the policies application. |
|
60 days |
Yes |
Aggregate change events |
Changes to operational data, particularly retroactive changes, can have a significant impact on operations. The application uses configurable change event rules to detect and process these changes. Any change to the tracked entity can result in the creation of policies event, along with more granular aggregate events, that is, for the change event rules of type Message. This process is used for purging these aggregated change events. |
|
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 |
PHI Audit Logs
Audit logs of protected health information (PHI) track user interactions. 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 |
|---|---|---|---|
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 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 generated during software operation.
| 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. |
|
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. |
|
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
Data Files and Import Data log include the following two types of data files:
-
Generated automatically by the system
-
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 |
|---|---|---|---|---|
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. |
|
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 |