For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SandboxDashboard
DocumentationAPI ReferenceChangelog
  • Getting Started
    • Overview
    • API Client
      • Installation
      • Setup
      • Payer Autocomplete
      • Eligibility Input
      • Soft Check
      • Hard Check
      • Existing Patients
      • Analytics
        • Conditional Patient Responsibility
        • Multiple Provider Types
        • ServiceEligibility Objects
  • Concepts
    • Eligibility
    • Providers
    • Patients
    • Notes
    • Services
    • Revalidation
    • Consent
  • Eligibility
    • Soft Eligibility
    • Hard Eligibility
    • Policy Errors
    • Conditional Patient Responsibility
  • Guides
    • Enrollment Status
    • Monitoring Payer Health
    • Webhook Behavior
  • Integrations
LogoLogo
SandboxDashboard
On this page
  • Providers
  • Estimates
Getting StartedReact SDKAdvanced

Multiple Provider Types

Was this page helpful?
Previous

ServiceEligibility Objects

Next
Built with

It is very common to support multiple ProviderType’s (MD, NP, PA, etc.) for a common type of visit (eg, “Initial Telehealth Visit”). These are configured as individual ServiceType’s within Bridge (eg, “Initial Visit with MD”, “Initial Visit with NP”).

Often, the desire is that the patient has no distinction between the two, and is able to run one eligibility check, and see a combined set of providers.

Without the SDK, the recommendation is to call the Create ServiceEligibility API multiple times, in parallel, and combine the results.

The SDK simplifies this. The input to both createSoftEligibilitySession and createHardEligibilitySession includes an array of ServiceType ID’s.

1createHardEligibilitySession({
2 serviceTypeIds: ["svt_xxx", "svt_yyy"],
3})

Providers

The default behavior is to combine the lists of providers returned at the end of an eligible check. If the patient is eligible for any of the ServiceTypes, they’ll be considered eligible.

Estimates

For some patients, their cost share responsibility will vary between provider types. To minimize surprises and limit additional charges post-adjudication, default behavior is to return the highest estimate value.

This can be configured when creating the session, using the estimateSelection parameter. This example selects the lowest value.

1createHardEligibilitySession({
2 serviceTypeIds: ["svt_xxx", "svt_yyy"],
3 estimateSelection: { mode: "LOWEST" },
4})