> 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/welcome.md).
# Welcome
#### **Bring healthcare into your product with MDI.**
MD Integrations (MDI) is a white-label telehealth platform and API that lets companies launch and scale medical services without building a clinical operation from the ground up.
You maintain the customer relationship and brand experience. We provide licensed medical care, clinical workflows, and infrastructure behind the scenes.
From DTC healthcare brands and weight-loss companies to pharmacies, retailers, diagnostics providers, and pharmaceutical organizations, MDI creates a frictionless patient journey from initial need to prescription fulfillment, all within your branded experience.
## A physician-led platform
Every treatment plan on MDI is reviewed by a board-certified physician. Our medical team spans 15+ specialties and holds licenses in all 50 states, backed by a 24/7 SLA for physician response. MDI is HIPAA compliant, SOC 2 and ISO 27001 compliant, and LegitScript certified — the compliance groundwork is already done, so you can focus on your product and your patients.
## One platform, three products
MDI is built from three connected products that work together behind your brand:
* **Clinicians App** — the operational hub for physicians and support staff.
* **Patient App** — the white-label patient experience, covering intake, messaging, and the patient portal.
* **Partner Portal** — your admin control panel for managing your catalog, branding, automations, and billing.
You don't need to build any of these yourself. You plug into them, brand them as your own, and MDI handles the clinical and operational machinery underneath. MDI 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 storefront? [Register to become a partner](/public/become-a-partner.md).
## Related reading
* [Understanding Core Concepts](/public/core-concepts.md)
* [Choosing Your Integration Path](/public/integration-paths.md)
* [Becoming a Partner](/public/become-a-partner.md)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mdintegrations.com/public/welcome.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media&token=b30873b7-a0c9-463f-9077-3ab70983f748)