​
Dynamic Config (Automatic mapping)

Dynamic config is recommended for all new Noyo integrations and makes carrier-specific config values no longer required.
Dynamic configuration is a new Noyo feature where the Noyo system automatically maps most values and surfaces any remaining unknown logic to you in the UI for your input. While this may present an extra step when connecting some groups to new carriers, it allows the initial integration to member snapshot to support all carriers and removes the need for carrier-specific fields to be passed in snapshots. Noyo recommends that you capture as much demographic information about employees and dependents as possible to ensure compatibility with potential future carriers, as different carriers can require different information about employees in order to process enrollments. Noyo creates rules based on the standard set of fields passed in the member snapshot and any relevant values included in the employee.classifications object. Recommended information for the classifications object includes:
  • Division, branch, team, or department info
  • Company location/office name
  • Leveling info (management, supervision, director, executive, key person, etc.)
  • Subsidiary number or name
If there are any subgrouping that determine the benefits a given employee is eligible for, make sure that information is supplied on your snapshots. The classifications block does not have a defined schema as it is designed to accept any relevant data: 
"classifications": {
  "job_title": "Executive Ruler",
  "is_executive": true,
  "random_fact": "I'm from the midwest",
  "custom_field_19": 2025,
  "favorite_pilot": "Nathan Fielder"
}

​
Pre-release Caveats

  • When using sandbox/test groups, explicit configuration may be required until rules are written. Your implementation team will provide guidance on how to structure snapshots for testing.

​
Explicit Config

In previous versions of Noyo, member snapshots required explicit carrier configuration to be defined on every incoming snapshot as detailed in Mapping plans and account structures. This is a multi-step process that involves:
  1. Pulling down the carrier’s view of the group
  2. Mapping your system’s stored information to the carrier’s group structure (benefit classes, subgroups, bill groups, divisions, locations, etc.) along with plans
  3. Sending the correct values on every snapshot
Using explicit carrier configurations will avoid any mapping tasks when connecting a group, but the structures and required fields differ by carrier and often require carrier-by-carrier engineering work. Sample snapshot carrier configuration blocks: 
{
    "benefit_class_identifier": "0001",
    "benefit_subclass_identifier": "0001-01",
    "bill_group_identifier": "0000",
    "bill_subgroup_identifier": "0000",
    "work_location_text": "ABCD1234"
}
For a fully enumerated list of per-carrier fields, see the Carriers page in the Command Center.