> 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.md). # Get Started Everything you need to onboard as an MDI partner and get your integration underway lives in this section — from understanding how the Patient Portal, Clinicians App, and Partner Portal fit together, to setting up your team, standing up a Sandbox environment, and working through the checklists that carry you to Live traffic. Start by getting oriented: read through the ecosystem overview so you know which product does what, then work the onboarding checklist stage by stage as your Partner status moves from `new` toward `live`. Along the way you'll assemble the right people on your team, configure and test against Sandbox before touching production, and prepare the review evidence MDI needs before you go live. Keep your partner credentials and technical contacts close at hand throughout the process, so you can resolve setup questions quickly and move toward production with confidence. --- # 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.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.