> 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/core-concepts.md). # Core Concepts MD Integrations is built around a small set of core ideas. You don't need to understand every detail to see how the platform fits together — just the basics of what each concept means and where it shows up in the patient journey. ## Patient The Patient is the person seeking treatment through your product. The first time someone interacts with MDI, a Patient record is automatically created to hold their demographics, medical history, allergies, and basic health details like height and weight. This record travels with the patient across visits, so returning patients don't have to start from scratch. ## Encounter An Encounter is a single physician review — the moment a treatment plan needs a licensed physician's evaluation. Whenever a patient requests treatment, MDI opens an Encounter, a physician reviews the patient's information against it, and the physician approves, requests more information, or declines the request. Encounters are the heartbeat of the platform: nearly everything that happens after checkout flows through one. ## Offering An Offering is a predefined treatment — a specific medication, dosage, and refill count — that MDI's medical team has pre-reviewed for safety and compliance before it's ever offered to a patient. Offerings are how you define what your storefront actually sells: rather than building a formulary from scratch, you choose from and configure Offerings that are already clinically vetted. ## There's more where this came from This page is a starting point, not the full picture. The partner documentation goes deeper into these concepts and introduces others — like Vouchers and Questionnaires — that shape how intake, eligibility, and treatment actually work under the hood. That full concept glossary, along with detailed guides for every integration path, is available once you register 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/core-concepts.md?ask=&goal= ``` `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.