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

# How It Works

MD Integrations connects your storefront to a physician network. Eligible purchases receive clinical oversight without adding clinical work to your team.

## The patient journey

{% stepper %}
{% step %}

### Patient checkout

The patient discovers and purchases a product or plan on your storefront. This can be Shopify, WooCommerce, or a custom site.
{% endstep %}

{% step %}

### Patient completes intake

Before or after checkout, the patient completes an intake form. The form collects health history, symptoms, and treatment goals.
{% endstep %}

{% step %}

### MDI creates the clinical record

MDI creates a patient record and opens an encounter. The encounter contains the case for physician review.
{% endstep %}

{% step %}

### Physician reviews the encounter

A licensed, board-certified physician reviews the encounter and intake information. The physician approves the treatment plan, requests more information, or declines treatment.
{% endstep %}

{% step %}

### Prescription routes to the pharmacy

For approved treatment, the prescription routes to a pharmacy for fulfillment.
{% endstep %}

{% step %}

### Pharmacy fulfills the order

The pharmacy prepares the order and ships it to the patient's address.
{% endstep %}

{% step %}

### Patient receives medication

The patient receives the medication at their address.
{% endstep %}

{% step %}

### Refills and follow-ups continue

Patients return through the same flow for refills or follow-up care. Your brand remains their experience throughout.
{% endstep %}
{% endstepper %}

## Why it matters

From your patient's perspective, this all happens inside your product, under your brand. From your team's perspective, MDI is handling licensing, physician staffing, compliance, and pharmacy logistics behind the scenes. You focus on your product and your customers; MDI focuses on the medicine.

The exact mechanics of intake, physician review, and fulfillment differ slightly depending on which integration path you choose, but the core loop above stays the same across every one of them.

Ready to bring this to your product? Head to [Get Started](/public/get-started.md) to begin registering as a partner.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/public/how-it-works.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.