Associate your employee and dependent records to ours
id
is a member identifier defined by Noyo, and is assigned to each employee and dependent when their record is created in the Noyo system. The custom_individual_id
field in the Noyo system is available to store a unique identifier defined by you. Members do not have a custom ID until you assign one. All custom_individual_id
values should be unique within each group and fixed so that they will not change over time. Social security numbers should not be used as custom identifiers.custom_individual_id
for each member; the success responses for your snapshots will contain each person’s Noyo ID, which you should store.
Otherwise, if employee records are already in Noyo, as is typical with groups who are moving to Noyo mid-year, you’ll use the custom_individual_id
to establish a link between your own records of those members and ours (see below).
If you’d like, you can check for employee data before sending the census snapshots by using the Get Group Employee List endpoint.
enable_member_auto_link
flag set to true
and the custom_individual_id
set to your own unique identifier.
When a snapshot is sent to Noyo tied to an existing group, we search for that member in the group using a combination of Name, DOB, and SSN. If there is a match, Noyo saves your custom identifier on that member the first time we see it, and any future snapshots with that custom ID will automatically be associated with the linked member. We also recommend saving our associated Noyo ID to use elsewhere in our API.
Because it’s likely that your records and the carrier’s records won’t have the exact same data, Noyo’s search algorithm is flexible and does not require strict matching of all demographic information in order to assign a custom ID and create a link. For example, if you have a member’s name as “Jimmy” but it is “James” in our records, we will still match the member as long as the /* glossary */DOB/* glossary */ and /* glossary */SSN/* glossary */ are the same.
custom_individual_id
, you can send a snapshot for that person that includes both their Noyo id
and the new custom_individual_id
. We will update the record in our system to associate the person with the new custom_individual_id
.
name
and date_of_birth
fields to filter members. The name field should receive a whitespace-separated combination of a first name, middle name, last name, and suffix, depending on what you have. For example, ?name=Peggy%20C%20Johnson
. If multiple employees are returned, you can then compare other data points to select the right employee from a small set of matches.individual_id
, individual_type
, line_of_coverage
, and plan_id
that link to the member and plan in Noyo. The API also returns an effective start and effective end date when the coverage is active, and other important details like volume amounts and COBRA status.
If you identify any data mismatches, including missing employees or incorrect demographic or coverage data at the carrier, sending a member snapshot with all of their dependent and enrollment information will push those updates or corrections to the carrier, since the group is already live on the connection.