> 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.md). # Key Concepts Before you start building against the MDI API, it helps to get comfortable with the handful of objects that the rest of this documentation keeps coming back to — Partners, Patients, Encounters, Offerings, Questionnaires, and Vouchers, among others. These aren't abstract API terms invented for convenience; each one maps to a real part of how a treatment episode actually unfolds, from the moment a patient starts an intake to the moment a physician approves a prescription and it moves to fulfillment. The pages in this section walk through each of these concepts individually, explaining what the object represents, how it relates to the others, and where you'll encounter it in the API. If you'd rather look something up than read through in order, the Glossary page collects every term in one place alongside its API field names, so you always have somewhere to check what something means the moment you see it in a request or response. --- # 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.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.