Technical documentation for integrating with Premera BlueCross through Noyo
c09b0a82-309d-44bf-9430-856c3c6027cd
group_data
object for the create endpoint, use the Premera group ID (also called the master agreement number) for the carrier_group_id
.
carrier_group_id
s to simulate different group connection statuses. Test group connections with these IDs will asynchronously update with the corresponding status within 10 seconds of submission.
Only the first three characters 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 further.
989*****: noyo_review
767*****: waiting_on_carrier
545*****: action_required
323*****: unable_to_connect
212*****: move_to_carrier_authorization
master_agreement_number
string, which is the primary group identifier, along with a list of one or more groups
(8-digit numeric code) to categorize employees enrolling in coverage.
plan_configuration
****block with subgroup_identifiers
and benefit_class_identifiers
fields containing lists of string identifiers. The identifiers will match the subgroups and benefit classes in the carrier configuration respectively, and describe which subgroups and benefit classes are eligible to enroll in the plan.
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.
Snapshots with Premera coverage may include an optional subgroup_identifier
and benefit_class_identifier
that matches the corresponding values in the group carrier configuration.
For Premera, there may often be only one of each respective identifier allowed for a plan. If the caller omits any values, Noyo will attempt to resolve the correct identifier in cases where only one option is available for the member’s enrollment.