COBRA Enrollments and Terminations
Many carriers have special handling for COBRA enrollments or modifications, and it’s important that requests to Noyo are properly flagged as relating to COBRA members. It’s best practice to provide all COBRA details whenever a request includes a member enrolled in COBRA.
Each member snapshot should contain a cobra_details
block, as shown below. Full details for COBRA submissions can be found in the Member Snapshot API Reference.
To ensure a carrier is able to process your COBRA requests correctly, all COBRA enrollments must be sent with cobra_enrolled= true
, an eligibility_start_date
, and an eligibility_end_date
.
Noyo recommends always including the qualifying_event_reason
and qualifying_event_date
when available, as some carriers may request it.
cobra_details.eligibility_start_date
field should be the first day without regular coverage, as COBRA coverage must be continuous with regular coverage. For example, if a member’s regular coverage ends 11/30, the COBRA coverage would start on 12/1.cobra_details.eligibility_end_date
should reflect the final day of the member’s maximum COBRA-eligible period (usually 18 months).enrolled_member.effective_start_date
field should reflect the start date prior to COBRA coverage unless otherwise indicated by carrier requirements.enrolled_member.effective_end_date
field should be sent as datemax (9999-12-31
).enrolled_member.latest_change_effective_date
field should reflect the member’s first day of COBRA coverage.cobra_details.cobra_enrolled
field should remain = true
.enrolled_member.effective_end_date
field should reflect the last day of the member’s COBRA coverage.cobra_details.eligibility_end_date
field should be updated if the member is no longer eligible for COBRA.cobra_details
element.enrolled_member.effective_start_date
field should reflect the start of the new active (non-COBRA) coverage period.enrolled_member.effective_end_date
field should be sent as datemax
(9999-12-31
).COBRA Enrollments and Terminations
Many carriers have special handling for COBRA enrollments or modifications, and it’s important that requests to Noyo are properly flagged as relating to COBRA members. It’s best practice to provide all COBRA details whenever a request includes a member enrolled in COBRA.
Each member snapshot should contain a cobra_details
block, as shown below. Full details for COBRA submissions can be found in the Member Snapshot API Reference.
To ensure a carrier is able to process your COBRA requests correctly, all COBRA enrollments must be sent with cobra_enrolled= true
, an eligibility_start_date
, and an eligibility_end_date
.
Noyo recommends always including the qualifying_event_reason
and qualifying_event_date
when available, as some carriers may request it.
cobra_details.eligibility_start_date
field should be the first day without regular coverage, as COBRA coverage must be continuous with regular coverage. For example, if a member’s regular coverage ends 11/30, the COBRA coverage would start on 12/1.cobra_details.eligibility_end_date
should reflect the final day of the member’s maximum COBRA-eligible period (usually 18 months).enrolled_member.effective_start_date
field should reflect the start date prior to COBRA coverage unless otherwise indicated by carrier requirements.enrolled_member.effective_end_date
field should be sent as datemax (9999-12-31
).enrolled_member.latest_change_effective_date
field should reflect the member’s first day of COBRA coverage.cobra_details.cobra_enrolled
field should remain = true
.enrolled_member.effective_end_date
field should reflect the last day of the member’s COBRA coverage.cobra_details.eligibility_end_date
field should be updated if the member is no longer eligible for COBRA.cobra_details
element.enrolled_member.effective_start_date
field should reflect the start of the new active (non-COBRA) coverage period.enrolled_member.effective_end_date
field should be sent as datemax
(9999-12-31
).