> 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/partner/get-started/the-mdi-ecosystem.md).

# The MDI Ecosystem

Learn how the Patient Portal, Clinicians App, and Partner Portal work together.

MD Integrations is made up of three connected products, each built for a different audience. Together they carry the patient journey from intake through care and fulfillment, and understanding how they hand off to one another is the fastest way to make sense of the rest of this platform.

### At a glance

| Product            | Primary users             | Purpose                             |
| ------------------ | ------------------------- | ----------------------------------- |
| **Patient Portal** | Patients                  | Complete intake and manage care.    |
| **Clinicians App** | Physicians and care teams | Review encounters and deliver care. |
| **Partner Portal** | Partner administrators    | Configure and operate your program. |

### Patient Portal

**patient.mdintegrations.com** is the white-label, patient-facing experience, and it includes two connected journeys:

1. **Intake wizard**: A voucher-gated flow that collects questionnaire responses and creates a patient record and encounter.
2. **Patient Portal**: A signed-in experience where patients can message their care team, view encounters and orders, manage subscriptions, and request refills.

Partners commonly embed this web experience in their own site or app. Because theme settings apply at runtime, branding changes take effect without a rebuild on your end.

You can also apply a custom domain to the Patient Portal — configure it in the Partner Portal, then use that URL across your site, app, and patient communications.

### Clinicians App

**app.mdintegrations.com** is the operational workspace for physicians, support staff, and administrators. MDI operates this application, so you won't integrate with it directly, but it's worth understanding what happens there since it's where your patients' encounters actually get handled:

* Physicians review encounters, approve or deny treatment plans, and issue prescriptions.
* Support staff message patients, manage pharmacy fulfillment, and resolve care issues.
* Administrators manage clinical workflows and physician assignments.
* Direct-to-pharmacy partners can track pharmacy orders through fulfillment.

### Partner Portal

**partners.mdintegrations.com** is your program's control center, and it's where most of your day-to-day configuration work happens. Use it to configure and manage:

* Offerings and intake questionnaires
* Branding, themes, automations, and custom domains
* Shopify, WooCommerce, API, and webhook integrations
* Administrator access and billing

### How the products connect

1. A patient begins intake in the Patient Portal with a voucher.
2. Voucher behavior follows your offerings configuration in the Partner Portal.
3. Completing intake creates an encounter for clinical review in the Clinicians App.
4. Care updates flow back to the patient in the Patient Portal.
5. Your team receives relevant data and webhook events through configured integrations.

**In short:** configure your program in the Partner Portal, serve patients through the Patient Portal, and deliver care through the Clinicians App.


---

# 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/partner/get-started/the-mdi-ecosystem.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.