> For the complete documentation index, see [llms.txt](https://docs.bloodgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloodgpt.com/integration-guides/integration-options.md).

# Integration Options

Compare four integration approaches and choose the one that fits your business.

BloodGPT offers four integration paths, from zero development to full customization.

## Comparison Table

| Feature                  | PDF-Only | Patient Portal   | Widgets                   | Full API         |
| ------------------------ | -------- | ---------------- | ------------------------- | ---------------- |
| **Setup time**           | 1 day    | 2-3 days         | 1-2 days                  | 3-7 days         |
| **Development required** | None     | Branding only    | Frontend (React)          | Backend + UI     |
| **Patient-facing UI**    | No       | Yes (our portal) | Yes (embedded components) | Yes (your UI)    |
| **Your branding**        | On PDF   | Full white-label | Your app + themable       | Complete control |
| **Real-time webhooks**   | Optional | Included         | Optional                  | Optional         |
| **Batch processing**     | Yes      | Yes              | Yes                       | Yes              |
| **Historical tracking**  | No       | Yes              | Yes                       | Your choice      |
| **Doctor validation**    | Optional | Optional         | Optional                  | Optional         |

## Which Option to Choose?

### PDF-Only

**Choose this if:**

* You want the fastest integration
* Your staff will manually deliver results to patients
* You don't need a patient-facing portal
* You're evaluating BloodGPT before deeper integration

**How it works:**

```
Your System → API Request → BloodGPT → PDF Report → You deliver to patient
```

[Learn more about PDF-Only →](/integration-guides/integration-options/pdf-only.md)

***

### Patient Portal

**Choose this if:**

* You want a ready-made patient experience
* Your patients should access results online
* You don't have development resources
* You want your branding without building UI

**How it works:**

```
Your System → API Request → BloodGPT → Patient receives magic link email → Views branded portal
```

[Learn more about Patient Portal →](/integration-guides/integration-options/patient-portal.md)

***

### Widgets

**Choose this if:**

* You already have a web app (React) and want results inside it
* You want a patient-facing UI without building report views from scratch
* You want more control than the hosted portal, but less work than the Full API
* You're comfortable minting a session token from your backend

**How it works:**

```
Your app (React) → embed <BloodGPTProvider> + widgets → BloodGPT report data → rendered in your UI
```

Drop in prebuilt React components (`<TestReport>`, `<ReportsList>`, …) from the `@bloodgpt/widgets` SDK. Your backend mints a short-lived, patient-scoped token; the browser never sees your API key.

[Learn more about Widgets →](/integration-guides/integration-options/widgets.md)

***

### Full API Integration

**Choose this if:**

* You have an existing platform or app
* You want complete control over the user experience
* You have development resources
* You need to integrate results into your workflow

**How it works:**

```
Your System → API Request → BloodGPT → JSON Response → You display in your UI
```

[Learn more about Full API →](/integration-guides/integration-options/full-api.md)

## Where It Runs

All four options run on our infrastructure in the EU — see [Privacy & Security](/getting-started/readme.md#privacy-and-security) for what that means in practice. If your security team or regulatory position rules that out entirely, the alternative is running the whole stack inside your own network: [On-Premises Deployment](/integration-guides/on-premises.md). It is a much larger project, delivered as a scoped engagement rather than a self-serve option — start with that page.

## Doctor Validation

All four options support optional [Doctor Validation](/integration-guides/doctor-validation.md) — a physician reviews every AI interpretation before the patient receives it. When enabled, results are held until a doctor approves, and reports include a verification stamp. No changes to your integration code are required.

## Migration Path

You can start simple and upgrade later:

```mermaid
flowchart LR
    A[PDF-Only] -->|Add portal| B[Patient Portal]
    A -->|Embed components| W[Widgets]
    A -->|Build custom UI| C[Full API]
    B -->|Want it in your app| W
    W -->|Need more control| C
```

{% hint style="info" %}
**Recommendation:** Start with PDF-Only or Patient Portal to validate the integration. Use **Widgets** to embed results in an existing React app, or **Full API** when you need complete control over the experience.
{% endhint %}