The demo tells you what the platform does. It does not tell you what it leaves.
MD Integrations sells itself in one line, and the line is honest: "You control the brand, we power the medicine." A clinic owner reads that and hears we handle the hard part. Then the build starts, and it turns out the hard part was never the medicine. It was the decisions nobody labeled as decisions.
Every claim below is read out of their own documentation and linked so you can check it. The only question is where the seam sits.
Nothing here is medical advice, and nothing here is legal advice.
What does MD Integrations own?
More than most platforms in this category, and the list is specific.
The clinicians. A physician network they describe as licensed in all 50 states, plus DC and Guam, operating 24/7, and covering a specialty count their own pages do not agree on. Their FAQ puts the service level at automatic case reassignment after four hours; the 52 minute figure on the homepage is an average, not the commitment. Two different numbers, routinely conflated.
The clinical record. Three objects do most of the work. A Patient record is created automatically on first contact and carries history and allergies across visits. An Encounter is a single physician review, opened whenever a patient requests treatment, in which, in their words, "the physician approves, requests more information, or declines the request". An Offering is a predefined treatment, which their documentation defines as a specific medication, dosage and refill count, and which "MDI's medical team has pre-reviewed for safety and compliance before it's ever offered to a patient".
The catalog gate. Their help center says partners "control a prescribable catalog, including medications, compounds, supplies, services, and lab requests". True, and also reviewed. An Offering can come back marked `rejected` with a note, and an edit sits in pending review, because "Edits apply only after approval". You own the catalog. You do not change it unilaterally, which matters if you have a launch date.
The pharmacy layer and the medical entity. Prescription routing and fulfillment across a network they describe as 30 or more pharmacies, three applications you do not build (a Clinicians App, a white-label Patient App and a Partner Portal), and the Professional Corporation itself, which their FAQ says your organization can contract into directly.
What stays yours?
The trick for reading any platform's documentation: find every sentence that offers you a choice, because a choice is a thing you now own. Two sit side by side in one help center answer.
Both of those are one short sentence in their docs and a quarter of your build.
Payments. On their Stripe account, you launch faster and the merchant relationship is theirs. On your own, you own the merchant account and everything attached: underwriting, the descriptor on the statement, chargebacks, and every subscription disclosure obligation at your checkout. If you sell a recurring program, the wording at the moment of purchase is yours to get right.
Pharmacy. Bring your own and more plumbing becomes yours. The pharmacy configuration screen holds required secret fields you populate, and when updates stop arriving the documented first step is to confirm the webhook URL with your pharmacy partner, not with MDI. And "Available pharmacies come from the MDI catalog", so an unlisted pharmacy is a request, not a connection. Compounded drugs are not FDA approved, and who compounds and ships them is a choice you own and should be able to explain.
Where intake sits. Their How It Works page is explicit that the patient "completes an intake form" either "Before or after checkout". That is flexibility, and it is the highest consequence architectural decision in a telehealth storefront, handed to you. On the Shopify path, the March 2025 release note tells partners to place the "MD Integrations Medical Intake" app block in the Thank You page order details sidebar, which is to say after payment. Whether that sequence is defensible for your program and your certification application is your call. See what an asynchronous intake has to stop and refuse and how intake, booking, checkout and follow-up join up.
Per state availability. Each Offering carries a States field on an Advanced tab. Your map, your maintenance.
Who owns the integration after it goes live?
Almost nobody asks this in a sales call. MD Integrations answers it in writing on their Solutions page:
That is a fair boundary, and it is a staffing decision. Somebody on your side owns the integration in perpetuity, and the changelog shows what that costs. Fourteen dated release notes in the public changelog run from March 2025 to September 2026, and six carry a breaking change notice. Two examples:
- June 2025 deprecated `case_prescriptions` and `case_services` in favor of `case_offerings`, with a migration deadline of July 31, 2025. The note says "Shopify/WooCommerce extension users do not need to take action" on that change, which tells you the deeper your integration, the more of this lands on you. It is also not the same as nothing: the same note says the "Chat With Doctor" button extension "needs to be re-added to templates after this deploy". Even the shallow path was not zero touch.
- September 2026 removed 2FA codes from API responses for white-label partners, moving patients to single use magic links.
Shipping breaking changes with notice and a deadline beats not shipping them. But an integration is a thing you staff, not a project you finish, and the cheapest path to launch is not always the cheapest to keep.
Does their compliance cover you?
Partly, and the part that it does not is the one that costs money.
MD Integrations states that it is HIPAA, SOC 2 and ISO 27001 compliant and LegitScript certified. Those are statements about MD Integrations. LegitScript Healthcare Certification is granted to an applicant and covers the websites that applicant discloses and controls, so your storefront is a separate application with its own review. A certified platform underneath you is useful to point at during that review. It is not a substitute for it. Start with our LegitScript checklist for web developers and the LegitScript and telehealth FAQ.
The same applies to the medical entity. Contracting into somebody else's PC network answers the staffing question, not the structural one. That is the corporate practice of medicine question, it varies by state, and it belongs with your own counsel.
Where do their own pages disagree?
Read enough vendor documentation and you learn the most valuable finding is never a missing answer. It is two answers.
Controlled substances. The marketing FAQ says "MD Integrations does not prescribe controlled substances." The partner help center answers the same question "Yes, subject to EPCS requirements and clinician and pharmacy eligibility", and a June 2026 release note is titled in part "Controlled Substances Support". Both cannot be true. This matters more than usual right now, because of what expires on December 31, 2026 for telehealth controlled substance prescribing.
Insurance. The marketing FAQ says MD Integrations "facilitates the use of health insurance for consult payments and prescription medications". The help center says "No. MDI uses a direct-pay telemedicine model." Those two answers describe two different checkouts.
How many specialties. The marketing FAQ claims "over 15 clinical specializations". The help center names them, and there are ten: Primary Care, Dermatology, Pediatrics, OB/GYN, Allergy and Immunology, Weight Loss, Urgent Care, Family Medicine, Internal Medicine and Emergency Medicine. Plan against the ten.
Launch time. The homepage says go live in under a week. The help center gives the number you can plan against: roughly 2 days for a storefront plugin, about 5 days for white label, up to 14 days for a custom API build.
None of this means anybody is being dishonest. Marketing pages and engineering docs drift apart at every company, including ours. It means the version you rely on has to be the version in your contract.
What to settle before you sign
Get these in the agreement rather than the deck.
- Whose Stripe account, and if theirs, who owns the chargeback and the statement descriptor.
- Which pharmacy, named, and whether it is in the catalog today.
- Whether intake sits before or after payment, and who signs off that the sequence is defensible.
- Controlled substances and insurance, yes or no, in writing.
- Who on your side owns the integration, and what happens in month fourteen when the next breaking change lands.
Every one of those is a thing the platform hands back to you. That is not a flaw in MD Integrations. It is what a platform is: it absorbs the clinical operation so you can own the commercial one, and the seam between the two is where a build quietly fails.
If you want that seam mapped against your actual program before you commit, that is what a telehealth program fit review is for, and it is the same work behind our telehealth and GLP-1 website builds.
Common questions
What does MD Integrations provide, and what do I still have to build?
MD Integrations provides the clinician network, the clinical record, the physician review step, the pharmacy connections and three applications: a Clinicians App, a white-label Patient App and a Partner Portal. Its own help center states that it 'manages clinicians, pharmacy fulfillment, compliance, and platform infrastructure'. What stays with you is the brand, the storefront, the funnel, the decision about where intake sits relative to checkout, the payment relationship if you want to keep it, the pharmacy relationship if you want your own, and the ongoing maintenance of whichever integration path you pick.
Does MD Integrations handle payments, or do I?
Either. MD Integrations states in its help center that partners 'Process payments through MDI's Stripe account or your own.' That is a genuine fork and it is yours to decide. Running on their Stripe account is faster to launch and leaves the merchant relationship with them. Running on your own means you own the merchant account, the underwriting, the descriptor on the statement, the chargebacks and any subscription disclosure obligations at checkout. Neither is wrong, but the two produce very different builds, so decide before you start rather than after.
Can I use my own pharmacy with MD Integrations?
Yes. The help center states that partners can 'Fulfill prescriptions through the standard pharmacy network or your own pharmacy relationship.' If you bring your own, more of the plumbing becomes yours: the pharmacy configuration page holds required secret fields you fill in, and when pharmacy updates do not arrive the documented first step is to confirm the webhook URL with your pharmacy partner. The platform also notes that available pharmacies come from the MDI catalog, so a pharmacy that is not listed has to be requested rather than simply connected.
If MD Integrations is LegitScript certified, is my brand certified too?
No. MD Integrations states that it is LegitScript certified, and that is a statement about MD Integrations. LegitScript Healthcare Certification is granted to an applicant and covers the websites that applicant discloses and controls. Your storefront is a separate application with its own review. A certified platform underneath you is a useful thing to be able to point at during that review, and it is not a substitute for it.
Do I need my own Professional Corporation to work with MD Integrations?
MD Integrations says not. Its FAQ states that your organization 'can contract directly with our nationwide Professional Corporation (PC) network', and its homepage currently lists 'No charge for the Professional Corporation' among what a partnership includes. Treat that as the start of a conversation with your own counsel rather than the end of one. How the medical entity, the management company and the brand relate to each other is the corporate practice of medicine question, it varies by state, and it is settled in your contract and your structure, not on a vendor page.
Does MD Integrations prescribe controlled substances?
Its own published pages disagree, so ask and get the answer in writing. The marketing FAQ on mdintegrations.com states plainly that 'MD Integrations does not prescribe controlled substances.' The help center in the partner documentation answers the same question with 'Yes, subject to EPCS requirements and clinician and pharmacy eligibility', and a June 2026 release note is titled in part 'Controlled Substances Support'. Both cannot be true at once. If controlled substances matter to your program, this is a contract question and not a documentation question.
Sources
- MD Integrations partner documentation, Welcome, describing the three products and the platform's compliance claims checked 2026-10-10
- MD Integrations partner documentation, How It Works, the eight step patient journey including intake before or after checkout checked 2026-10-10
- MD Integrations partner documentation, Integration Paths, comparing API, White-Label Apps, Shopify and WooCommerce checked 2026-10-10
- MD Integrations partner documentation, Core Concepts, defining Patient, Encounter and Offering checked 2026-10-10
- MD Integrations help center, General Questions, stating the payment and pharmacy forks, the insurance answer and the controlled substances answer checked 2026-10-10
- MD Integrations help center, Pharmacy Configuration Issues, on pharmacy secrets, webhook URLs and the MDI pharmacy catalog checked 2026-10-10
- MD Integrations help center, Offering Configuration Issues, on rejected Offerings, pending review and per state availability checked 2026-10-10
- MD Integrations changelog, fourteen dated release notes from March 17 2025 to September 18 2026, six carrying a breaking change notice checked 2026-10-10
- MD Integrations release note, Magic-Link Authentication for Patient Workflows, September 18 2026, removing 2FA codes from API responses checked 2026-10-10
- MD Integrations release note, Unified Offerings Structure and Stripe Payments, June 17 2025, with a July 31 2025 migration deadline checked 2026-10-10
- MD Integrations release note, Shopify Checkout Extension Update, March 17 2025, listing the required partner theme and settings changes checked 2026-10-10
- MD Integrations marketing FAQ, including the controlled substances answer, the insurance answer and the Professional Corporation answers checked 2026-10-10
- MD Integrations Solutions page, stating the support limit of four hours a month and that the development team will not provide debugging or coding services checked 2026-10-10
- MD Integrations homepage, including the Professional Corporation offer line and the network coverage claims checked 2026-10-10
- LegitScript, Healthcare Certification, on what certification covers and the disclosure of websites under the applicant's control checked 2026-10-10
Want this costed for your build?
Tell us what you already have and what is not working, and we will come back with the shape of the work and what drives the number.