> 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/key-concepts/glossary.md).

# Glossary

This glossary is a single reference for every core term used across this documentation. If you run into a capitalized platform term on any page and aren't sure what it means, look for it here — it's almost certainly defined below, usually alongside the API field name it corresponds to and a link to the page that covers it in depth.

<table><thead><tr><th width="243.95660400390625">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Access Token</strong></td><td>The bearer token used to authenticate calls to the MDI API. Passed on every request and subject to expiration and refresh — see Authentication &#x26; Credentials.</td></tr><tr><td><strong>Automation</strong></td><td>A no-code workflow made of a trigger and one or more steps (e.g., "when an Encounter is completed, send a message"). Lets partners react to platform events without writing code. See Automations.</td></tr><tr><td><strong>CarePair</strong></td><td>MDI's product-recommendation engine, which pairs complementary Offerings together (for example, suggesting a supporting medication alongside a primary treatment). See CarePair.</td></tr><tr><td><strong>Clinician</strong></td><td>The licensed provider who reviews an Encounter and prescribes. Clinicians are managed by MDI and attached to your Partner account — they are not managed from the Partner Portal directly. See Partners, Panel Users &#x26; Roles.</td></tr><tr><td><strong>Direct to Pharmacy (DTP)</strong></td><td>An MDI-managed pharmacy fulfillment model, where MDI handles order routing and fulfillment directly with select partner pharmacies rather than the partner managing that relationship themselves. See Direct to Pharmacy.</td></tr><tr><td><strong>Encounter</strong></td><td>The primary term for a single physician review or consultation. Created whenever a treatment plan needs evaluation, and includes the diagnosis, intake answers, attachments, lab results, and proposed Offerings. A Patient may have many Encounters over time. <strong>This is the same object the API calls a "case"</strong> (<code>case_id</code>, <code>case_offerings</code>, <code>case_questions</code>, <code>/v1/partner/cases</code>), and the same object the Patient App UI sometimes labels a "Visit" for patients. Encounter, case, and Visit all refer to one underlying record — the name just changes depending on whether you're reading this documentation, the API, or the patient-facing UI. See Patients &#x26; Encounters.</td></tr><tr><td><strong>Environment</strong></td><td>Sandbox or Live. Sandbox uses safe test data that is never billed and never sent to real pharmacies; Live is real and billable. See Sandbox vs. Live.</td></tr><tr><td><strong>EPCS</strong></td><td>Electronic Prescribing of Controlled Substances — the regulatory framework and technical requirements governing how controlled-substance prescriptions are transmitted electronically. See Controlled substances and compounds.</td></tr><tr><td><strong>NPS / Campaign</strong></td><td>Net Promoter Score — a 1-10 rating survey sent to patients, configured and delivered as a Campaign. See Campaigns &#x26; NPS.</td></tr><tr><td><strong>Offering</strong></td><td>A predefined treatment — medication, dosage, refills, communication rules, and pricing — that MDI's medical team reviews for safety and compliance before it can be used in an Encounter. Different product variants (e.g., a 1-month vs. 3-month supply) generally need separate Offerings. Identified by <code>offering_id</code>. See Offerings.</td></tr><tr><td><strong>Panel User</strong></td><td>A member of a Partner's staff who logs into the Partner Portal. Added and managed by the Partner's own admin users; access is admin or non-admin, with no granular role system. See Partners, Panel Users &#x26; Roles.</td></tr><tr><td><strong>Partner</strong></td><td>The tenant, or brand, integrating with MDI — a DTC health brand, pharma/weight-loss company, retailer/pharmacy, or lab. Has a lifecycle status (<code>new → onboarding → integrating → review → ready → live</code>, plus <code>suspended</code>/<code>canceled</code>) and an integration type (<code>shopify</code>, <code>woocommerce</code>, <code>full-api</code>, or <code>white-label</code>). See Partners, Panel Users &#x26; Roles.</td></tr><tr><td><strong>Patient</strong></td><td>The person seeking treatment. MDI automatically creates a Patient record — demographic data, medical history, allergies, height, weight, and other key health indicators — the first time someone interacts with the platform. Anchors every Encounter, message, and file tied to that person. See Patients &#x26; Encounters.</td></tr><tr><td><strong>Questionnaire</strong></td><td>The intake form tied to one or more Offerings, made up of Questions and Options with conditional Rules that branch based on factors like age, gender, BMI, vitals, pregnancy, state, prior prescriptions, or custom metadata. See Vouchers &#x26; Questionnaires.</td></tr><tr><td><strong>Review</strong></td><td>A pending approval record created whenever a Partner edits an Offering, Question, Option, Rule, or Questionnaire. An MDI admin must approve it before the change goes live — a safety and compliance gate. See Partners, Panel Users &#x26; Roles.</td></tr><tr><td><strong>Support Staff</strong></td><td>Staff who assist physicians with operational tasks (shipping, billing, missing information) on Encounters in the <code>Support</code> status. Can be external (Partner-side) or internal (MDI-side). See Partners, Panel Users &#x26; Roles.</td></tr><tr><td><strong>Tag</strong></td><td>A label that staff or partners apply to a Patient or Encounter for organization and filtering.</td></tr><tr><td><strong>Voucher</strong></td><td>A one-time-use, intake-authorization token — not a discount or coupon — that binds together a patient (or none, to create one), a questionnaire, and one or more offerings. Its response includes an <code>onboarding_url</code> that, once completed, creates the Patient and Encounter records. See Vouchers &#x26; Questionnaires.</td></tr><tr><td><strong>Webhook</strong></td><td>An asynchronous HTTP notification MDI sends to your system when an event occurs (e.g., an Encounter status change or a pharmacy order update). See Webhook event catalog.</td></tr><tr><td><strong>Wildcard</strong></td><td>A merge-variable placeholder — such as a patient's name — that automatically expands when used inside message or notification templates. See Tags &#x26; Wildcards.</td></tr></tbody></table>


---

# 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/key-concepts/glossary.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.