> 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/onboarding-guide.md). # Onboarding Guide This page covers MDI's review and certification process specifically — the evidence you submit, how long review takes, and the compliance bar your patient flow needs to clear before launch. For the day-to-day steps of configuring your account (users, offerings, credentials), see the Onboarding Checklist page instead. ## The review-evidence video Before MDI can move your account from `review` to `ready`, you'll need to submit a single recorded video walking through your live, compliant patient flow. This is the one real "submission" in onboarding — everything else in the Integration stage is configuration inside the Partner Portal, not a document you hand over. Record the video as a 7-step script, in order: 1. Privacy policy is clearly available 2. Terms of Service is acknowledged by the patient 3. Patient is made aware a consultation is needed and their treatment might be rejected 4. Consultation fee is clearly indicated at checkout 5. Patient goes through the intake questionnaire 6. Patient can visualize their treatment plan 7. Patient can reach out to their doctor Once you've recorded it, upload it in the Partner Portal. There's a 100MB limit, so convert or compress to MP4 first; if it's still too large after that, share it with your MDI contact over Slack instead. > **Note:** Missing one of these seven moments — the consultation fee disclosure and the "reach out to the doctor" step are the ones most often missed — is a common reason evidence gets sent back. ## Review timeline and rejection handling Once submitted, MDI's clinical team reviews your evidence and setup. Per the source material, this typically takes **24–48 hours for an initial pass, and up to 7 days for more complex setups** — there's no same-day guarantee, so it's best to avoid building a launch date around a fixed turnaround. From there, one of two things happens: * **Approved** — your account moves from `review` to `ready`, and you proceed to the final live pharmacy test. * **Rejected** — you get specific, concrete feedback on what to change. Fix it and resubmit; there's no cap on how many times you can resubmit, and no way to expedite the review itself. ## Regulatory and compliance sign-off Beyond completing the checklist, MDI's clinical team checks your patient flow against a specific compliance bar before granting a green light. At a level of detail not covered on the Onboarding Checklist page, you'll need to have the following in place: * **Side-effect and treatment disclosure** — common side effects disclosed before a patient selects a treatment, plus any off-label or non-FDA-approved use. Marketing can't imply a doctor visit isn't really needed or promise a consult length; patients need to understand a licensed physician genuinely reviews their case and can decline treatment. * **Consent language** — the intake should tell patients plainly that a board-certified physician licensed in their state will review their answers, and confirm the information they've provided is accurate, complete, and about themselves. Near the end, ask whether they understood all the questions. * **Legal protections** — patients agree not to submit claims for this care to Medicare or other insurers, are told they can send their prescription to any pharmacy of their choice, are directed to call 911 or seek in-person care for urgent conditions, and your terms protect MDI and its contracted physicians from liability. Treatment and prescriptions are never guaranteed. * **Complaint pathway** — clear, accessible instructions for how a patient can file a complaint with their state medical board. To get the green light, you'll share two sample cases with a medical director — one with typical answers, one with unusual ones. Keep in mind that a green light covers that exact version of your intake, materials, and treatment plan, so changing any of them afterward means another review before you can relaunch. ## Branding, notifications, and contacts Branding (logo, colors), notification settings, and key/support contacts also get configured during onboarding, alongside the integration work — but where to set those up in the Partner Portal is covered on other pages, not here. --- # 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/onboarding-guide.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.