Changelog

Bridge API SDK Launch

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

What’s New

Bridge API SDK (@usebridge/api) is now available on npm, providing a TypeScript client for seamless integration with the Bridge API.

Key Features

• Type Safety: Full TypeScript support with generated types from our API specification
• Request/Response Validation: Built-in validation for all API requests and responses
• Error Handling: Comprehensive error handling with detailed error messages

Getting Started

Install the SDK:

$
npm install @usebridge/api

Check out our SDK documentation for installation guides, examples, and API reference.

Support multiple attestations per consent type

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).

Improved dashboard visibility: Consent details now display directly on the patient’s record, so it’s easy to stay up to date.

Automatic routing for expired consent: If a consent expires, related services will automatically pause and move to triage until it’s renewed.

These changes make consent management more flexible and transparent — while helping you avoid billing delays.

Triage Report

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.

Dashboard Search

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.

Credentialed Filter in Eligibility Report

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.

Insurance Revalidation Now Managed by Bridge (GA)

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.

Partners must still handle revalidation results by subscribing to webhooks. See the Revalidation Webhook documentation for more.

Claim history considered during eligibility

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.

If you believe a patient is being incorrectly flagged, or the issue has been addressed without insurance changing, contact Bridge and these restrictions can be bypassed.

Distinct Provider Enrollment Triage

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.

Update TriageTask, BILLING_TIME_LIMIT

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.

New TriageTask, BILLING_TIME_LIMIT

When a Service is billed beyond the agreed Timely Filing Limit, it will automatically be moved through to TRIAGE with the new BILLING_TIME_LIMIT task.