Skip to content

Bridge Health API Overview

The Bridge Health API is integral to the efficient delivery of virtual metabolic health and weight-loss programs. These programs are conducted in collaboration with telehealth companies (TH Co) and Community-Based Organizations (CBOs). The primary objectives of this API include streamlining the patient enrollment process, verifying patient eligibility for various program offerings, and ensuring accurate and secure matching of prescribers to patients for GLP-1 based weight-loss therapies. It uses JSON over HTTPS with bearer‑token authentication, ensuring that only authorized telehealth applications can access and manipulate program, CBO, pharmacy, and patient records.

Base URL

https://api.bridgehealthhub.com/

Key Stakeholders

  • Patient: Individuals participating in the weight-loss program who seek effective medical intervention and guidance.

  • Telehealth Company (TH Co): Entities responsible for managing the patient-facing interactions, initial data gathering, patient education, and ongoing digital engagement.

  • Community-Based Organizations (CBOs): Local or regional clinics offering comprehensive weight-loss programs, patient support, and associated healthcare resources.

  • Prescribers: Licensed healthcare professionals (doctors, nurse practitioners) authorized by CBOs to prescribe and manage patient medication regimens.

Business Workflow Alignment

The API closely aligns with the comprehensive operational requirements defined by Bridge Health and the CBO, ensuring regulatory compliance (AKS, HIPAA, 340B), precise patient-provider matching, and rigorous financial tracking. Key operational procedures supported by the API include:

  • Provider Credentialing and Roster Management: Ensures prescriber validity via the API, reducing compliance risks and audit discrepancies.

  • Program Availability Determination: Automates geographic and insurance-based eligibility checks, aligning with CBO's defined service criteria.

  • Enrollment Management: Integrates seamlessly with Stripe and pharmacy systems for secure financial transactions, accurate prescription processing, and timely patient onboarding.

  • Patient Disenrollment and Cancellation Management: Clearly defines processes for handling various cancellation scenarios, ensuring compliance and accurate system updates.

API Integration Points and Workflow

1. Advertisement and Welcome Screen

  • Objective: Provide an initial introduction to the program, guiding prospective patients through the preliminary enrollment stages.

  • API Call Triggered: None

  • Business Impact:

    • Enhances the accuracy of program-to-patient associations based on criteria established by the CBOs.

    • Optionally utilizes a unique CBO ID, when available, to streamline patients into an enrollment workflow specific to a single CBO program. This is particularly relevant when the advertisement the program member interacts with is specific to the CBO's program.

2. Patient Program Availability Confirmation

  • Objective: Verify availability of specific CBO programs for a patient based on geographic ZIP code location and insurance type.

  • API Call Triggered: checkProgramAvailability

  • Business Impact:

    • Eligible patients are guided seamlessly to the next phase, including detailed medical questionnaires focused on GLP-1 therapies.

    • Ineligible patients receive immediate redirection to alternative suitable CBO programs, facilitating access to alternative treatment resources and transparent pricing information.

    • API responses for available programs will include participating pharmacies and out-of-pocket cost of medications in the response to help patients select a preferred pharmacy and medication therapy.

Bridge Health Operations - Program Availability

3. Medical Questions for GLP-1 Eligibility

  • Objective: Gather detailed health and medical history information to confirm a patient's clinical suitability for GLP-1 weight-loss treatment. These questions and clinical determinations are owned entirely by the TH Co.

  • API Call Triggered: None

  • Business Impact:

    • Ensures rigorous assessment of patient eligibility, reducing potential medical risks.

    • Improves clinical outcomes by matching patients accurately with appropriate therapeutic options.

Bridge Health Operations - GLP-1 Candidacy Questions

4. Medication and Pharmacy Preference Selection

  • Objective: Allow patients to select their medication preference and pharmacy, ensuring patient autonomy without inducement towards specific pharmacies or medications.

  • API Call Triggered: None

    Business Impact:

    • Supports regulatory compliance by ensuring transparency and patient-driven selection, reducing risk of inducement accusations.

    • Displays medication options, pharmacies, addresses, and transparent out-of-pocket price points derived from CBO Pharmacy and Drug data received from the response of the checkProgramAvailability API call.

Bridge Health Operations - Medication and Pharmacy Preference

5. Enrollment Process

  • Objective: Formally enroll the patient into the chosen weight-loss program, securely capturing comprehensive personal details and insurance information.

  • API Call Triggered: enroll

  • Business Impact:

    • Conclusively formalizes patient enrollment, activating their participation.

    • Provides patients immediate and continuous access to essential resources, tools, and education needed for successful weight management and ongoing health monitoring.

    • Ensures accurate tracking of patient status for compliance and billing purposes.

Bridge Health Operations - Enroll and Checkout

6. Prescriber Verification

  • Objective: Authenticate prescriber credentials and confirm their official association with specific CBOs prior to matching those prescribers with a patient who is a member of that CBO program.

  • API Call Triggered: verifyProviderCBOCredentialing

  • Business Impact:

    • Ensures all prescriptions are valid, compliant with regulatory standards, and directly linked to properly credentialed providers.

    • Supports seamless prescription processing, reducing administrative burdens and improving medication delivery accuracy.

Bridge Health Operations - Provider Credentialing

7. Cancellation and Disenrollment

  • Objective: Facilitate patient or administrative disenrollment from the program based on patient decision, medical necessity, or administrative criteria.

  • API Call Triggered: disenroll

  • Business Impact:

    • Provides a structured process for disenrolling patients, ensuring clear and auditable reasons for cancellation with reasoning.

    • Maintains accurate and up-to-date records, vital for program integrity and financial reporting.

    • Supports prompt updates to pharmacy and prescriber records, ensuring medication dispensing and follow-up care are accurately discontinued.

Conclusion

The Bridge Health API is strategically designed to facilitate operational efficiency and alignment between the requirements of CBOs and the workflows of TH Co applications in maintaining virtual metabolic health and weight-loss programs. By automating critical processes such as patient eligibility verification, prescriber credentialing, enrollment management, and compliant disenrollment, the API ensures patients are matched with the right program and the right provider while maintaining regulatory compliance, auditability and financial oversight.