# New Group Installment

## Overview

Ideon supports the application of a group for the first time with Carrier partners, we refer to this process as "Group Installment". The new group installment process allows an employer to offer insurance plans to employees. Group setup typically occurs after an employer has worked with a carrier/broker to receive a quote regarding the costs associated with a specific carrier, types of coverage, and plan selection. Once the employer has selected the carrier and plan(s) they will offer to employees, they can begin the group setup process to establish a new group with the carrier and begin enrolling employees.&#x20;

The following steps can be used to install a group with a Carrier:

1. Create the Group Installment
2. Add the Coverage Period
3. Add the Plans that are being offered
4. (Optional) Add Employment Classifications
5. Add the Subscribers and Dependents
6. Add Qualifying Life Events
7. Complete the Setup

## 1. Create the Group Installment <a href="#create-the-group-installment" id="create-the-group-installment"></a>

The first step is to send over the information relating to the Group, or Employer. This information includes the name, tax number, address locations, and Carrier for which to initiate coverage. This information is sent via the POST /group\_installments endpoint. Note that some information could be conditionally required based on the Carrier, which we will cover in the carrier-specific sections below.

{% code title="POST /group\_installments" %}

```yaml
{
    "group": {
        "external_identifier": "Group1",
        "insurance_market": "small_group",
        "employer": {
            "organization_name": "Acme Ins Co",
            "fein": "222222222",
            "established_date": "1999-08-13",
            "employer_type": "corporation",
            "census": {
                "employees": 25,
                "full_time_equivalent_employees": 20,
                "eligible_employees": 18
            }
            ...
        },
        "group_setup": {
            "carrier_name": "humana"
            ...
        },
        "primary_location": {
            "external_identifier": "Location1",
            "type": "physical",
            "employer_address": {
                "address_line_1": "30 W Live Oak Ave",
                "city": "Defuniak Springs",
                "state": "FL",
                "zip": "32435",
                "fips_county_code": "12131"
                ...
            }
            ...
        }
        ...
    }
}
```

{% endcode %}

### Producer Information

#### Producer(s) of Record

Producers help sell and manage plans and products that groups choose to buy, and are eligible to receive a commission. The producer(s) sign the master employer / group application in order to place the business. As part of group setup, the details about the producer(s) and their producer agency (if applicable) are sent to the carrier. A carrier will confirm the identity of both producer(s) and producer agencies to confirm they are licensed and authorized to sell various products. Producer(s) of record have the ability to manage the group and the groups employees on their behalf after the initial group setup is completed. There are two scenarios in which producer information is sent to carriers:&#x20;

1. Producer is writing the business on behalf of an agency that they work for and is affiliated with a [Producer Agency](#producer-agency)
2. Producer is independent and does not work on behalf of an agency&#x20;

In both cases the same information is required by carriers as part of the group setup process. The scenarios below showcase how producer information is sent as part of group setup via a [POST to /groups](https://app.swaggerhub.com/apis-docs/VericredEnrollments/Enrollments/0.1.2#/Groups/createGroupInstallment). As a general rule, if there are multiple producers, the commission split between them should sum to 100.&#x20;

{% tabs %}
{% tab title="Single Writing Producer" %}
The information for the producer of record includes details about the producer including the date the producer signed the master employer application.

{% code title="POST /group\_installments" %}

```yaml
{
    "group": {
        ...
        "producers_of_record": [{
            "first_name": "Arya",
            "last_name": "Stark",
            "national_producer_number": "12345678",
            "social_security_number": "222222222",
            "fein": "222222222",
            "state_license_number": "12345678",
            "carrier_producer_identifier": "87654321",
            "signature_date": "2001-01-01"
            ...
        }]
        ...
    }
}
```

{% endcode %}
{% endtab %}

{% tab title="Two Writing Producers" %}
If two writing producers are associated with writing the business for the group they should be provided together as producers of record. When providing the two writing agents be sure to include the commission split.

```yaml
{
    "group": {
        ...
        "producers_of_record": [{
                "first_name": "Arya",
                "last_name": "Stark",
                "national_producer_number": "12345678",
                "state_license_number": "12345678",
                "carrier_producer_identifier": "87654321",
                "primary": false,
                "commission_split": 25,
                "signature_date": "2021-11-01"
                ...
            },
            {
                "first_name": "Brandon",
                "last_name": "Stark",
                "state_license_number": "87654321",
                "carrier_producer_identifier": "A123132",
                "primary": true,
                "commission_split": 75,
                "signature_date": "2021-11-01"
                ...
            }
        ],
        ...
    }
}
```

{% endtab %}
{% endtabs %}

## 2. Add the Coverage Period

The Coverage Period is a representation of the plan year that the group has with a Carrier. This information lets the Ideon team know when the coverage will begin and with which Carrier.

{% code title="POST /coverage\_periods" %}

```yaml
{
    "coverage_period": {
        "external_identifier": "CUSTOM_COVERAGE_PERIOD",
        "carrier_name": "humana",
        "enrollment_type": "initial_installment",
        "coverage_start_date": "2022-01-01",
        "coverage_end_date": "2022-12-31",
        "open_enrollment_start_date": "2021-12-15",
        "open_enrollment_end_date": "2022-12-31"
        ...
    }
}
```

{% endcode %}

### Employer's Signature

As part of a coverage period, an employer may need to sign-off on the information they are providing to the carrier. Traditionally a paper Master Employer Application or Master Group Application is provided to a carrier on behalf of the employer with the employer's group setup information. The application includes the `name`, `title`, and `date` of an authorized employer representative. This signature serves as an acknowledgement that the information provided about the group and its employees is accurate.

{% tabs %}
{% tab title="Employer's Signature" %}
An authorized employer representative:

{% code title="POST /coverage\_periods" %}

```yaml
{
    "coverage_period": {
        ...
        "group_application_signature": {
            "name": "Jon Snow",
            "title": "Director of Human Resources",
            "date": "2021-10-01"
        }
        ...
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

## 3. Add the Plans that are being offered

When the employer creates the group with the carrier they will need to provide the plans they intend to offer their employees. Each plan that is offered also needs to have a `policy_premium_method` that determines member premiums.

[API Documentation for Creating Plans](https://app.swaggerhub.com/apis-docs/VericredEnrollments/Enrollments/0.1.2#/Plans/createCoveragePeriodPlan)

{% tabs %}
{% tab title="Age Banded" %}
Indicate the premium rating method as "age\_banded"

{% code title="POST /coverage\_periods/:id/plans" %}

```yaml
{
  "plan": {
    "external_identifier": "ppo_high_plan",
    "description": "Medical PPO - High",
    "product_line": "medical",
    "product_type": "preferred_provider_organization",
    "premium_level": "high",
    "policy_premium_method": "age_banded"
    ...
  }
}
```

{% endcode %}
{% endtab %}

{% tab title="Composite" %}
Indicate the policy\_premium\_method as "4\_tier\_composite"

{% code title="POST /coverage\_periods/:id/plans" %}

```yaml
{
    "plan": {
        "external_identifier": "ppo_high_plan",
        "description": "Medical PPO - High",
        "product_line": "medical",
        "product_type": "preferred_provider_organization",
        "premium_level": "high",
        "policy_premium_method": "4_tier_composite",
        "composite_rate_premiums": {
            "employee_only": 100000,
            "employee_plus_children": 150000,
            "employee_plus_spouse": 120000,
            "family": 200000
        }
        ...
    }
}
```

{% endcode %}
{% endtab %}

{% tab title="Riders" %}
Plans can be offered along with rider(s).

{% code title="POST /coverage\_periods/:id/plans" %}

```yaml
{
  "plan": {
    "external_identifier": "ppo_high_plan",
    "description": "Medical PPO - High",
    "plan_identifier": "44147126",
    "product_line": "medical",
    "product_type": "preferred_provider_organization",
    "premium_level": "high",
    "policy_premium_method": "age_banded",
    "riders": [
      {
        "identifier": "587AR"
      }
    ]
    ...
  }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

## 4. (Conditional) Add Employment Classifications

Employment Classifications can be set up in order to create classes, divisions, departments, or subgroups that represent different groupings for which employees may be grouped. These groups or 'buckets' are often created to allow for segmenting plan offerings or benefits, or simply as a means of making invoicing and billing easier.

{% code title="POST /groups/:id/employment\_classifications" %}

```javascript
{
    "employment_classification": {
        "external_identifier": "Class1",
        "description": "All Eligible Employees in California",
        "start_date": "2022-01-01",
        "end_date": "2022-12-31",
        "type": "class"
        ...
    }
}
```

{% endcode %}

## 5. Add the Subscribers and Dependents

Subscribers and dependent information can be loaded in together in a single request to Ideon.&#x20;

{% code title="POST /groups/:id/subscribers" %}

```yaml
{
    "subscriber": {
        "external_identifier": "ABC-132A54",
        "location_id": "LOCATION_UUID",
        "first_name": "John",
        "last_name": "Smith",
        "social_security_number": "222222222",
        "gender": "male",
        "marital_status": "registered_domestic_partner",
        "birth_date": "1991-01-01",
        "class": {
            "employment_classification_id": "EMPLOYMENT_CLASSIFICATION_UUID",
            "effective_date": "2022-01-01"
        },
        "employment_details": {
            "start_date": "2019-01-01",
            "status": "full_time",
            "annual_earnings": 230000,
            "earnings_effective_date": "2019-11-13",
            "wage_frequency": "annually",
            "hours_per_week": 40.0
            ...
        },
        "residential_address": {
            "address_line_1": "50 Orchard Street",
            "city": "Kansas City",
            "state": "MO",
            "zip": "64108"
            ...
        },
        "dependents": [{
            "external_identifier": "Dependent1",
            "first_name": "Joanna",
            "last_name": "Smith",
            "social_security_number": "333333333",
            "gender": "female",
            "subscriber_relationship": "registered_domestic_partner",
            "birth_date": "1992-02-03"
            ...
        }]
        ...
    }
}
```

{% endcode %}

## 6. Add Qualifying Life Events

A qualifying life event allows Ideon to enroll or manage the product lines and effective dates of an enrolled family. This qualifying life event likely will be initiated by a standard life-event e.g. new hire, birth, death, termination of employment, or open enrollment. For purposes of the initial installment with the Carrier, the first Qualifying Life Events should have a `type` of `initial_enrollment or newly_eligible`.

{% tabs %}
{% tab title="Qualifying Life Event" %}
{% code title="POST /subscribers/:id/qualifying\_life\_events" %}

```yaml
{
    "qualifying_life_event": {
        "type": "initial_enrollment",
        "date": "2021-12-01",
        "eligibility_start_date": "2022-01-01",
        "coverage_period_id": "COVERAGE_PERIOD_UUID",
        "plan_elections": {
            "medical": {
                "plan_id": "PLAN_UUID",
                "type": "election",
                "coverages": [
                    {
                        "member_id": "SUBSCRIBER_UUID",
                        "status": "employer_sponsored",
                        "start_date": "2022-01-01"
                    },
                    {
                        "member_id": "DEPENDENT_UUID",
                        "status": "employer_sponsored",
                        "start_date": "2022-01-01"
                    }
                ]
            }
            ...
        }
        ...
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

#### Providers

Depending on the member's coverages, first-time HMO enrollments may require the member's Primary Care Physician (PCP) selection.&#x20;

{% tabs %}
{% tab title="PCP - Initial Selection" %}
A PCP selection can be provided for a member when enrolling in an HMO health plan.

{% code title="POST /subscribers/:id/qualifying\_life\_events" %}

```yaml
{
    "qualifying_life_event": {
        ...
        "plan_elections": {
            "medical": {
                ...
                "coverages": [{
                    ...
                    "providers": [{
                        "type": "primary_care_provider",
                        "first_name": "Indiana",
                        "last_name": "Jones",
                        "service_provider_identifier": "1234ABC"
                        ...
                    }]
                }]
            }
            ...
        }
    }
}
```

{% endcode %}
{% endtab %}
{% endtabs %}

## 7. Complete the Setup

Notifying Ideon that you've loaded in all of the necessary information is the final step in the process. The Complete Setup endpoint will create the work order in the Ideon system, notifying the team to configure the data, QA it, and send it over to the Carrier for enrollment.&#x20;

The Ideon Operations team will coordinate with the Carrier in case any additional information is needed due to policy requirements.&#x20;

Once the group has been installed with the carrier, Ideon will update the Coverage Period automatically and the Group could be eligible to move to the [Member Management](https://ideonapi.gitbook.io/enrollment/existing-business) phase, depending on the carrier connected. From that point, your system only has to keep the member and election information in sync (see [Continued Maintenance](https://ideonapi.gitbook.io/enrollment/existing-business/enrollment-features/member-management)) and Ideon will deliver that information to the Carrier.

{% code title="POST /coverage\_periods/:id/setup\_complete" %}

```javascript
{}
```

{% endcode %}
