Revalidation

Bridge requires that a patient’s insurance be revalidated within 72 hours of a scheduled Service.

Bridge will initiate this process automatically and notify you of the outcome via webhook. You may also trigger revalidation manually using the Revalidate Patient endpoint.

Once revalidation begins, you’ll observe the following state transitions:

1. Policy.status changes to REVALIDATING
2. Policy.status updates to either CONFIRMED or INVALID
3. Service.coverageStatus changes to REVALIDATING
4. If the Policy is INVALID, Service.coverageStatus updates to INVALID_COVERAGE
5. If the Policy is CONFIRMED, Service.coverageStatus becomes one of:

• VALID
• INVALID_COVERAGE
• INVALID_PROVIDER

Each transition emits a policy.updated, service.updated, or service_eligibility.updated event, triggering the corresponding webhook. Webhooks are asynchronous and can arrive out of order, so for critical decisions we recommend fetching the current resource state from the API.

Outcomes

If revalidation completes successfully and coverageStatus becomes VALID, the Service may proceed as planned.

If not, Bridge treats the result as a coverage issue. The Service should be canceled, rescheduled, or followed up with the patient for correction. Bridge does not auto-cancel Services.

Policy.status = INVALID, Service.coverageStatus = INVALID_COVERAGE

The patient’s insurance could not be verified—typically indicating that coverage has lapsed or been terminated.

Policy.status = CONFIRMED, Service.coverageStatus = INVALID_COVERAGE

The insurance is active, but the ServiceType is not covered by the patient’s plan.

Policy.status = CONFIRMED, Service.coverageStatus = INVALID_PROVIDER

The policy and ServiceType are valid, but the Provider is now out of network. This usually signals a change in the provider network. Reach out to the patient to confirm, and contact Bridge if this appears to be in error.