Data Intake Setup

Data Intake Definition

Data Intake provides the Group Customer with the ability to process intake files of data specific to employee or sponsor changes and additions of Policy Coverage data. The data intake files include both updates and new records. Initially, the files are received at a group/batch level via a transaction at the Group Customer level or from the group files processed by AsFile or a similar data intake utility. The requested changes are distributed within our system as individual transactions. The generated individual transactions will be easily identifiable to the intake file from which they were created. A multi-customer file received from a TPA will be split by Group Customer before being applied to OIPA.

How it Works

Data Intake allows navigation through the intake files received at the Group Customer level or through individual AsFile requests. Each Family Record contains the information that needs to be processed on an employee and dependents for a Group Customer. The file will contain an identifier for the Group Customer to easily identify the employee and related dependents for the Group Customer as well as an identifier for the Data Intake Agreement ID. The File ID provides a unique reference to the instance of the data intake Agreement ID and the Group Customer ID. The IDs are used to identify the file type from the Group Customer Data Intake Preferences (typically identified on the Group Customer Screen) and the identification of the file type being received.

You will have the ability to view the status of the client/policies linked to the files. In addition, you may view the number of individual policy/certificate level transactions expected, actual, pending, shadowed, and pending. The individual transactions will be linked to the intake file via a unique Source File ID. Displayed activities and values are displayed in an inquiry/view access and only in descending order (not configurable). Lastly, Activity Group provides the capability for the user to reverse all activities linked to a file - both pending and active.

Data Intake Setup:

Data Intake Setup is split into 3 logical steps. The first step involves configuring the Intake Profile Definition. There are many pieces of configuration to an Intake Profile Definition:

  1. The Intake Profile Definition Rule allows us to configure the fields that can be entered in the application, the processing configuration for files and records, and file level validations to run.
    • Record processing determines how we will calculate changes. Currently, we compare the current record to the last record to determine the differences.
    • File processing determines whether we will compare files to calculate missing records. It also sets the name of the Data Intake Transaction that will be used for processing records.
    • File Level Validation is comprised of a Math section and a Validate Expression section. Input to File Level Validation are metrics resulting from pre processing the file, including number of errors, number of removals, and number of file adds.
  2. The Record Xml Schema defines the structure of the fields that are coming in on a record. OIPA offers the choice of using either the OIPA standard schema, or any xml schema. The former requires no further configuration; the latter requires a Record XSLT to be defined that would transform the incoming record to the OIPA standard schema form.
  3. The Data Intake Transaction is responsible for mapping the changes that are calculated for a single record onto one or more activities that need to be run in the system. It supports MATH and Business Rules. Currently, the only business rules supported are Validate Expressions and Create Clients.

The Create Clients Business Rule is used to create client/person entities in the system. It can also create the Group Customer Relationship, Addresses, Class Membership, as well as activities to be run when the client is created.

Activity Sequence Processing runs the activities that are created in the MATH section of the Data Intake Transaction. The processing spans across levels in the system, so we can run any combination of policy, plan, client, group customer, and client transactions. Typically, client and/or policy level transactions will be run on part of record processing for members.

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us