> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tagada.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tagada Rx — Overview

> The telehealth layer of the Tagada OS: intake, clinician review, e-prescribing, pharmacy fulfillment, and ship-day rebilling — orchestrated on top of your Tagada store.

# Tagada Rx

<Note>
  **Who this is for** — Brands selling prescription-based treatments online (weight management, hair loss, skin care, hormones…). Tagada Rx turns a regular Tagada store into an **asynchronous telemedicine pharmacy**: the patient answers a medical intake, pays, a licensed clinician reviews the case, a partner pharmacy ships the treatment, and the subscription rebills on the day the pharmacy actually ships.

  Tagada Rx is an **opt-in add-on** — activated per store. On TagadaRx the sold price is **6.9% of GMV** (processing included), with **\$0 setup**. Clinician and pharmacy costs pass through at cost. See [Activation](/developer-tools/rx/crm-activation).
</Note>

***

## What is Tagada Rx?

Everything you already know from Tagada — products, checkout, payments, subscriptions, CRM — plus a **clinical layer**:

<CardGroup cols={2}>
  <Card title="Clinical network" icon="stethoscope">
    A pre-integrated network of US-licensed clinicians (all 50 states). Tagada submits patient intakes as **cases**; clinicians review asynchronously, approve or decline, and e-prescribe.
  </Card>

  <Card title="Pharmacy fulfillment" icon="truck-medical">
    Approved prescriptions are routed to a partner pharmacy. Shipment and delivery events flow back into your Tagada order timeline automatically.
  </Card>

  <Card title="Ship-day rebilling" icon="rotate">
    Recurring treatments rebill **the day the pharmacy ships** — not on an arbitrary calendar date. No "charged but never shipped" revenue.
  </Card>

  <Card title="Patient portal" icon="comments">
    A ready-made patient area: case timeline, secure messaging with the care team, and photo-ID upload for identity verification.
  </Card>
</CardGroup>

<Info>
  **PHI never touches Tagada storage.** Patient identity and intake answers transit through the API straight to the clinical network. Tagada persists only non-PHI routing data: case ids, statuses, timestamps, and event metadata.
</Info>

***

## How a sale works, end to end

```
Patient                     Tagada                        Clinical network / Pharmacy
  │                           │                              │
  │ 1. Quiz + checkout        │                              │
  ├──────────────────────────►│  card authorized (hold)      │
  │                           │                              │
  │ 2. thank-you intake +     │  3. create patient + case    │
  │    rx.submitCase()        │                              │
  ├──────────────────────────►├─────────────────────────────►│
  │                           │                              │ 4. clinician reviews
  │                           │◄─────────────────────────────┤    (webhooks)
  │  "Approved!" email        │  approve → capture hold      │
  │◄──────────────────────────┤  decline → void hold         │
  │                           │                              │ 5. pharmacy ships
  │                           │◄─────────────────────────────┤    (webhook)
  │  tracking email           │  shipment.shipped            │
  │◄──────────────────────────┤  → schedule rebill at        │
  │                           │    ship day + cycle          │
  │                           │                              │
  │ 6. next cycle: rebill fires on the actual ship day       │
```

1. **Checkout first, clinical second.** The patient completes a marketing quiz (no PHI) and authorizes a card hold. The hold is *not* clinical approval — the storefront copy must make that clear.
2. **Case submission.** On the thank-you page the storefront collects the network questionnaire and calls `rx.submitCase()` with the patient identity and intake answers. Tagada forwards everything to the clinical network and records a case (`rxcase_xxx`).
3. **Clinician review.** A licensed provider in the patient's state reviews asynchronously. Approval, decline, prescription, shipment, and delivery all arrive as **webhooks** which Tagada normalizes into case events.
4. **Capture or void — never a refund.** Approve captures the hold. Decline voids it. Money never leaves the card if the clinician does not prescribe.
5. **Recurring refills.** On every shipment, Tagada schedules the next charge at `ship day + cycle` (30 days by default). An hourly job scans due cases and fires the rebill.

***

## The case lifecycle

Every clinical case (`rxcase_xxx`) moves through a strict state machine:

```
requested → submitted → in_review → approved → shipped → delivered
                 │            │          │
                 └── declined ┘          │
                 └── cancelled ──────────┘        (error: from any non-terminal state)
```

| Status                             | Meaning                                                   |
| ---------------------------------- | --------------------------------------------------------- |
| `requested`                        | Case created locally, not yet accepted by the network     |
| `submitted`                        | Intake accepted by the clinical network                   |
| `in_review`                        | A clinician has the case                                  |
| `approved`                         | Prescription issued                                       |
| `shipped`                          | Pharmacy shipped (tracking attached, rebill scheduled)    |
| `delivered`                        | Carrier delivered — resting state of an active subscriber |
| `declined` / `cancelled` / `error` | Terminal states                                           |

Each transition is recorded as an append-only **case event** (`case.approved`, `shipment.shipped`, `message.created`, …) that you can read from the API, the CRM, or the patient portal timeline.

***

## The three integration surfaces

| Surface                                        | Auth                                                          | Use it for                                              |
| ---------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------- |
| **Storefront API** — `/api/public/v1/rx/*`     | No API key — per-resource proof (`orderId` + `checkoutToken`) | Submitting cases and polling status from the browser    |
| **Merchant API** — `/api/v1/rx/*`              | Tagada API key (Node SDK: `tagada.rx.*`)                      | Activation, config, product mapping, listing cases, ops |
| **Patient portal API** — `/api/v1/rx/portal/*` | Customer CMS session (email OTP)                              | Patient case list, messaging, photo-ID upload           |

You never talk to the clinical network directly — Tagada owns that integration, its credentials, and its webhooks.

***

## Choose your track

<CardGroup cols={2}>
  <Card title="How it works (deep dive)" icon="diagram-project" href="/developer-tools/rx/how-it-works">
    Architecture, PHI handling, webhooks, rebilling — the mental model in one page.
  </Card>

  <Card title="Operating modes" icon="scale-balanced" href="/developer-tools/rx/operating-modes">
    Merchant of Record (affiliate) vs Direct Merchant — who is the seller, who pays whom.
  </Card>

  <Card title="Activate in the CRM" icon="toggle-on" href="/developer-tools/rx/crm-activation">
    Request activation, pay the setup fee, map your products.
  </Card>

  <Card title="End-to-end tutorial" icon="graduation-cap" href="/developer-tools/rx/tutorial">
    From empty store to first prescription — the complete flow, step by step.
  </Card>

  <Card title="Building blocks" icon="cubes" href="/developer-tools/rx/building-blocks">
    The decoupled architecture: every storefront is a facade over the same Rx bricks.
  </Card>

  <Card title="Storefront templates" icon="palette" href="/developer-tools/rx/storefront-templates">
    Three funnel archetypes, one skeleton — with live demos.
  </Card>
</CardGroup>