> 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/doctor-validation.md).

# Doctor Validation

Add doctor review to your integration — results are verified by a physician before reaching the patient.

## What is Doctor Validation?

An optional mode where a doctor reviews every AI interpretation before the patient receives it. When enabled, the pipeline pauses after AI analysis and waits for a doctor to approve, edit, or reject the report. Only approved results are delivered — with a visible doctor verification stamp.

Doctor Validation works with any integration option (PDF-Only, Patient Portal, or Full API). It adds a review step without changing your existing integration.

## When You Need It

| Reason                    | Description                                                                    |
| ------------------------- | ------------------------------------------------------------------------------ |
| **Regulatory compliance** | Your jurisdiction requires a physician sign-off on lab interpretations         |
| **Quality assurance**     | You want a medical professional to verify AI output before delivery            |
| **Premium service**       | "Doctor-verified AI interpretation" builds trust and justifies premium pricing |
| **Risk management**       | Critical or abnormal values get human oversight before reaching patients       |

{% hint style="info" %}
**Not sure?** If your country or medical board requires a licensed professional to review interpretive reports before patient delivery, you need Doctor Validation. When in doubt, consult your compliance team.
{% endhint %}

## How It Works

{% @mermaid/diagram content="sequenceDiagram
participant Your System
participant BloodGPT
participant Doctor
participant Patient

```
Your System->>BloodGPT: Send test data (API)
BloodGPT->>BloodGPT: AI interpretation
BloodGPT->>Doctor: Review notification
Note over BloodGPT,Patient: Results held until approved
Doctor->>BloodGPT: Approve / Edit / Reject
BloodGPT->>Patient: Verified results + doctor stamp" %}
```

### Without Doctor Validation

```
Your System → BloodGPT AI → Patient gets results immediately
```

### With Doctor Validation

```
Your System → BloodGPT AI → Doctor reviews → Patient gets verified results
```

The only difference is the review step. Everything before (data submission, AI analysis) and after (PDF generation, portal delivery, webhooks) stays the same.

## What Your Patients Get

When Doctor Validation is enabled, reports include a **verification stamp** showing:

* Doctor's name and credentials
* Verification date
* That the report was reviewed by a licensed professional

This appears on both PDF reports and the patient portal.

## Doctor Dashboard

Doctors access a dedicated review dashboard where they can:

| Action      | What happens                                               |
| ----------- | ---------------------------------------------------------- |
| **Approve** | Results delivered to patient as-is                         |
| **Edit**    | Doctor modifies interpretation, then results are delivered |
| **Reject**  | Results are not delivered, test flagged for re-analysis    |

Reports in the queue are prioritized automatically — tests with more abnormal values appear first.

## Setup

### Step 1: Enable Doctor Validation

Contact BloodGPT support or go to **Dashboard → Settings → Validation** and set validation mode to **Required**.

### Step 2: Add Doctors

Register doctors who will review reports:

1. Navigate to **Dashboard → Team → Add Member**
2. Select role: **Doctor**
3. Enter doctor's credentials (name, specialty, license number)
4. Doctor receives an invitation email

### Step 3: Test the Flow

1. Submit a test via API (same as before)
2. Verify the test appears in the doctor's review queue
3. Approve the test
4. Verify the patient receives results with doctor stamp

### Timeline

Doctor Validation adds approximately **1 day** to your setup timeline for configuring doctors and testing the review flow:

| Base Integration | Without Validation | With Validation |
| ---------------- | ------------------ | --------------- |
| PDF-Only         | 1 day              | 2 days          |
| Patient Portal   | 2-3 days           | 3-4 days        |
| Full API         | 3-7 days           | 4-8 days        |

## Works With Any Integration

Doctor Validation is not a separate integration path — it's an add-on that works transparently with your chosen approach:

* **PDF-Only** — PDF is generated only after doctor approves
* **Patient Portal** — Magic link is sent only after doctor approves
* **Full API** — Webhook fires only after doctor approves; polling returns `pending_doctor_review` status until then

No changes to your API calls are required. The only difference is a new status (`pending_doctor_review`) that appears between `analyzing` and `completed`.

## Go-Live Checklist

* [ ] Validation mode enabled for your organization
* [ ] At least one doctor registered and tested
* [ ] Review queue tested with sample results
* [ ] Doctor stamp verified on PDF output
* [ ] Team trained on review workflow
* [ ] Response time expectations set (how quickly doctors should review)

{% hint style="success" %}
**Ideal for:** Diagnostic laboratories in regulated markets, clinics offering premium interpretation, any organization where physician oversight is required or valued.
{% endhint %}