Changelog

@usebridge/sdk is now available for running eligibility checks on the server or in API routes, without React.

Check out our Eligibility SDK documentation for installation and examples.

We’re excited to announce the launch of our official Bridge Python API Client!

The dashboard submit form and CSV for new providers have been updated so supervisor NPI is no longer collected there and is instead collected on the provider onboarding form.

There is a new POST endpoint for partner submissions. See Submit Provider for details.

Note.data now supports two new optional array fields:

• MEDICATIONS: a list of active medications documented for the patient.
• ALLERGIES: a list of known patient allergies.

Payer health monitoring is now available in the dashboard, with a network status view and change notifications via webhooks.

The Provider management page has been overhauled to provide better insights and controls.

The Bridge React SDK now supports an event-driven analytics system, allowing you to track user interactions throughout the eligibility flow.

We’re excited to announce the launch of our official Bridge React SDK! 🚀

Provider onboarding data that was previously available through the dashboard as the Eligibility Report is now available through API’s and Webhooks.

Use the Get Enrollment Status API to fetch a structured version of the report data.

Listen for the new provider.enrollment_status.updated Event to be notified when these values change.

Bridge now supports billing and management for Chronic Care Management (CCM) services.

Bridge now supports billing for Remote Patient Monitoring (RPM) services, including device setup and supply.

We’re excited to announce the launch of our official Bridge API SDK! 🚀

We’ve made some updates to how patient consent works in Bridge:

Support for multiple submissions: Patients can now submit more than one attestation per consent type if needed.

Simplified tracking: You’ll now see the latest consent for each type, along with a clear expiration date and current status (e.g., Active, Expiring Soon, Expired).

There is a new Triage Report available in the Bridge Dashboard.

This report provides a searchable list of all Services in the TRIAGE status, surfacing the triage task types.

It is now possible to search for Patients, Services and Providers using the field at the top of the dashboard.

These can be queried several fields including name, email, external ID’s, and more.

We’ll be rolling out improvements to this feature of the next few weeks, to include more controls/filtering.

The Provider Eligibility report in the Bridge dashboard now supports filtering to Providers with an Approved Credentialing Status.

This Credentialed filter can be applied from the Filters dropdown or by clicking on the menu button to the right of the Credentialed column header. Setting the filter to Credentialed is True will exclude all Providers whose credentialing has not yet been approved.

Bridge now automatically manages the timing of insurance revalidation.

Previously, partners were responsible for triggering revalidations by calling the Revalidate Patient endpoint at the right time. This is no longer required — Bridge handles it by default.

For partners already managing revalidation timing in production, this change will not take effect immediately. Our team will coordinate with you directly if and when it’s appropriate to transition.

Patient’s who have previously had denied claims, may be more reliably prevented from being given ELIGIBLE responses within ServiceEligibility. If this is patient-specific, there may be an explicit message in the messages array.

This will be detected across distinct Patient and Policy resources. If a Patient’s insurance policy changes, it will be evaluated independently.

Previously, enrollment issues found at billing fell under the PATIENT_INSURANCE triage task. If a Provider was not actively enrolled at the Date of Service, this will now be a specific PROVIDER_NOT_ENROLLED task. This is unusual, and should never be seen if hard eligibility checks are respected.

When a Service is billed beyond the agreed Timely Filing Limit, it will automatically be moved through to TRIAGE with a BILLING_TIME_LIMIT task. The time limit has increased to 75 days.