​

Group connections

Create a group connection to manage groups through Noyo.

In the group_data object for the create endpoint, use Ameritas’s 3-digit subsidiary number and 6-digit policy numbers for the carrier_group_id. These will be concatenated together using an underscore in the format “sub_pol”.

​

Sandbox testing

You may use the following special Ameritas carrier_group_id values in order to simulate different group connection statuses. If you use a value listed below, the group connection will asynchronously update with the corresponding status within 10 seconds of submission.

Only the first three characters of the policy ID are evaluated to figure out the target status (e.g. 989 means noyo_review). Since group connections should be unique by a carrier ID and carrier group ID combination, you may use the final characters to iterate and test this interaction.

• 010_989***: noyo_review
• 010_767***: waiting_on_carrier
• 010_545***: action_required
• 010_323***: unable_to_connect
• 010_212***: move_to_carrier_authorization

​

Carrier configurations

Group, plan, and member configurations are where Noyo shares and receives details that are unique to a carrier. Every other part of Noyo’s payloads are standardized, but the configurations hold the unique fields and classifications that change from connection to connection. As part of preparing to connect to a new carrier, you need to understand the contents of each configuration and be sure your system is able to send the required data for each member.

​

Get the group configuration from Noyo

The group carrier configuration endpoint returns information about how the group is labeled and categorized within the carrier’s system. You can also see this data in the Command Center on a group’s detail page by clicking one of their carrier connections.

Groups that have Ameritas coverage will be configured with a list of group_policies consisting of policy_number **and subsidiary_number strings, which are the primary group policy identifiers for Ameritas. In addition to the group_policies,** groups will also be configured with lists of one or more group_classes, one or more group_divisions, and zero or more group_departments. These fields will now also include the subsidiary_number ****and policy_number ****fields so that multi-policy groups can distinguish those between policies as well.

{
    "group_id": "57c49148-408c-476c-a3ed-93dd8a01027b",
    "carrier_id": "2d370e0e-fd73-45e0-8828-796d2cacaeef",
    "configuration": {
        "group_classes": [
            {
                "class_number": "01",
                "class_description": "ALL ELIGIBLE EMPLOYEES",
                "policy_number": "099012",
                "subsidiary_number": "010"
            }
        ],
        "group_divisions": [
            {
                "division_number": "00001",
                "division_name": "MAIN OFFICE",
                "policy_number": "099012",
                "subsidiary_number": "010"
            }
        ],
        "group_departments": [
            {
                "department_number": "000001",
                "department_name": "LOGISTICS",
                "policy_number": "099012",
                "subsidiary_number": "010"
            }
        ],
        "group_policies": [
            {
                "policy_number": "099012",
                "subsidiary_number": "010"
            }
        ]
    }
}

​

Get the plan configuration from Noyo

The details in the plan configuration should be used to map each Noyo plan to the corresponding plan in your own system.

{
    "plan": {
        "id": "73966f87-35d9-4236-8484-884170723725",
        "version": "cc642b9b-ff80-4d9e-9227-ec8088c50a45",
        "group_enrollment_id": "e247c353-22ba-4479-89f7-a68cbd7a9ffb",
        "carrier_id": "2d370e0e-fd73-45e0-8828-796d2cacaeef",
        "line_of_coverage": "vision",
        "name": "Vision Full",
        "code": "",
        "effective_start_date": "2023-01-01",
        "effective_end_date": "9999-12-31",
        "voluntary": false,
        "status": "active",
        "eligible_member_types": ["all"],
        "waiting_periods": [
            {
                "waiting_period_rule": "hire_date",
                "waiting_period_enrollment_type": "new_member"
            },
            {
                "waiting_period_amount": 0,
                "waiting_period_unit": "day",
                "waiting_period_rule": "after_waiting_period",
                "waiting_period_enrollment_type": "current_member"
            }
        ],
        "termination_policy": "last_work_date",
        "cobra_rules": {
            "eligible": false
        },
        "plan_configuration": {
            "division_number": "1",
            "class_number": "1",
            "division_name": "Division 1",
            "class_description": "First Class"
        },
        "created": 1695917445,
        "modified": 1705423250,
        "dependent_child_age_limits": []
    },
    "ge": {
        "id": "e247c353-22ba-4479-89f7-a68cbd7a9ffb",
        "version": "19b4be7d-9a5b-4414-9758-c71f61eda06d",
        "group_id": "26faa540-9ca3-454b-914e-a84701ea04cd",
        "carrier_id": "2d370e0e-fd73-45e0-8828-796d2cacaeef",
        "line_of_coverage": "vision",
        "status": "active",
        "open_enrollment_start_date": "2022-12-01",
        "open_enrollment_end_date": "2022-12-31",
        "open_enrollment_renewal_date": "2023-01-01",
        "effective_start_date": "2023-01-01",
        "effective_end_date": "9999-12-31",
        "created": 1695917445,
        "modified": 1705423250
    }
}

​

Send the member configuration to Noyo

Each member snapshot sent to Noyo can contain a configuration section. Depending on each carrier’s requirements, you may need to use this section to include carrier-specific identifiers like classes, subdivisions, or bill groups. These go in the coverage block’s carrier_config section and ensure that members are enrolled in the correct coverages. Member snapshots missing a carrier_config section or with incorrect config data will result in a 422 error.

You may specify a department_number, division_number, and class_number in the carrier config. The division number and class number will help identify the plan for the enrollment in cases where it cannot be determined in your system. If division number and class number are supplied, a plan_name from your system may be included on the coverage in lieu of a Noyo plan ID.

{
    "division_number": "00004",
    "class_number": "02",
    "department_number": "000006"
}

If you are still using member requests, include a department_number string matching one of the department options listed in the group carrier configuration. A department_number can be thought of as situationally required. We will need a department number to facilitate enrollments at a member level. Otherwise, if the group does not have any departments configured, the caller may leave the carrier_config empty.

{
    "department_number": "000001"
}

​

Carrier-specific validations

None.

​

Connection Basics

​

Getting groups connected

After receiving a signed application from a net-new group, it takes Ameritas about 10 business days to install it in their system. After the group is installed, a group connection request can be successfully completed.

Groups are generally connected in 1-5 business days. For existing groups switching off of EDI, the EDI feed must be fully disabled after the group connection request is sent. To get a new or existing group connected to Noyo, simply request a group connection with the group name, subsidiary number, and policy number as detailed in the Technical Spec.

As with all other Sync carriers, we process a group connection by pulling all plan, member, and group structure data from Ameritas to populate our system.

​

Groups are considered fully connected when:

• Noyo returns the connection status as “completed.”
• You’ve linked Noyo’s IDs for account structure information, plans, members, and coverages to your own, and established an account structure mapping process.
• You’ve deactivated previous forms of data exchange and are ready to send all enrollment changes through Noyo.

​

Processing member changes

Each member snapshot is broken into one or more individual “transactions” for the changes that need to be made with each carrier. Our integrations with API-enabled Sync carriers generally result in 90% of member transactions arriving at the carrier within 10 minutes of being sent to Noyo, and 95% of transactions being confirmed by Noyo within 4 business days of original receipt.

​

Round-trip confirmation

As with other Sync carriers, Noyo is able to read data directly from Ameritas’s system. Noyo monitors each transaction with round-trip confirmation, which triggers a check in the carrier’s system after the change is sent and again on the change’s effective date to ensure that enrollments go through as expected. Any issues that are surfaced during one of the round-trip confirmation checks are handled by the Noyo team or surfaced as discrepancies in the Command Center.

Use the Tracking API to see the results of round-trip confirmation and get a granular view of how each change is being processed.

​

Managed changes

Our goal is to confirm all member changes within 4 business days. However, some transactions cannot be confirmed automatically after being submitted through our API because special handling is required: we call these “managed” transactions. Ameritas managed transactions are generally resolved in 5-10 business days. Note that when broker involvement is required, the turnaround time is dependent on how quickly the broker can provide information.

Types of managed changes:

• SSN changes Updating a member’s social security number.
• Removing aged-out dependents Changes that remove a dependent from coverage who has aged out and already been removed from Ameritas’s system.
• Duplicate dependents Changes to a name, SSN, or DOB that accidentally create a duplicate dependent.
• USPS-validated address Submission of an address that does not match the USPS validated version. Noyo will confirm the correct address with Ameritas before completing the transaction.

​

Retroactive changes

Transactions with an effective date of more than 90 days prior to the date of receipt are considered retroactive transactions. All retroactive transactions are manually reviewed and updated by Ameritas, so they will be in a processing state for 5-10 business days until completed.

​

Far-future changes

Far-future dated transactions will remain open with a status of processing in Noyo’s system until the effective date can be confirmed with Ameritas (this occurs when the effective date of the change is 90 or fewer days away). Members will not experience any delays in obtaining coverage, but these far-future dated transactions may impact some Noyo-reported metrics.

Example scenario: A ben-admin sends a new hire election to Noyo on 4/10/2024 with an effective date of 9/1/2024.

1. Noyo transmits the change on the day of receipt
2. The member is updated in the Ameritas system but the data available to us will not reflect the new date
3. The transaction remains processing until 90 days prior to the 9/1/2024 effective date (6/3/2024). At that point, Ameritas updates the data for the member.
4. On 6/3/2024, Noyo performs round-trip confirmation to verify the status of the enrollment. The transaction will be marked as complete.

​

Other scenarios

• Legally disabled dependents who are over the age limit but are continuing coverage must be sent with a disability object in the member snapshot. We will work with Ameritas to ensure these dependents are properly enrolled.
• Dependents cannot be enrolled in coverages that the member is not enrolled in. Noyo will cancel transactions that attempt to do this.
• Dependents and members cannot have the same SSN. Transactions containing this duplication will be canceled within 1 business day of receipt.

​

Open enrollment

You can send the group’s plan-level renewal decisions to Noyo once they’ve been officially communicated to Ameritas. Noyo will check Ameritas’s system daily until the new plans are available to ensure that they are installed correctly.

When the plans in Ameritas’s system match the expectations you submitted, the renewal decision status will move to “ready” and you will be able to send member snapshots with each member’s open enrollment elections for the new plan year.