The MSO Model: How Non-Clinicians Legally Own Telehealth Businesses

The wall: corporate practice of medicine

The corporate practice of medicine doctrine (CPOM) is the rule, in many states, that only licensed clinicians or clinician-owned entities may own medical practices, employ physicians, or direct clinical care. The rationale is old and simple: medical judgment should answer to a license, not to shareholders. Enforcement intensity varies widely, with states like California, Texas, and New York among the strictest and others barely enforcing the doctrine at all, but a multi-state telehealth business has to build for the strict states, because that's where the patients are too.

Related doctrines travel with CPOM: fee-splitting prohibitions (restrictions on sharing professional revenue with non-clinicians, which constrains how the business entity may charge the practice) and anti-kickback rules where federal programs are involved. Together they mean a non-clinician can't simply incorporate, hire doctors, and sell visits, and any structure that pretends otherwise is fragile in exactly the states that matter.

You don't get to pick the friendliest state's rules. A national telehealth program is built to the strictest CPOM states it serves, or it's built twice.

The structure: PC plus MSO

The standard answer is two entities with a contract between them. The first is a professional corporation or professional LLC (the 'PC'), owned by a licensed physician, which is the medical practice: it employs or contracts the clinicians, holds the patient relationships and medical records, and owns every clinical decision. Because the owner-physician is chosen to work well with the business, the arrangement is nicknamed the 'friendly PC' model.

The second entity is the management services organization (the 'MSO'): the ordinary company the founders and investors own. It provides everything non-clinical under a management services agreement: the brand, technology, marketing, intake infrastructure, billing and collections support, scheduling, HR for non-clinical staff, and administrative operations. Revenue economics live in the management fee the PC pays the MSO for those services.

Multi-state operation adds a layer: the PC must be able to practice where patients are, which operators solve with some combination of foreign registrations and, where state rules require it, additional state-specific PCs under common friendly-physician ownership. This is bookkeeping-heavy rather than conceptually hard, but it's why 'we operate in N states' is an infrastructure claim, not a checkbox.

The documents that carry the weight

Four agreements do most of the structural work, and reviewers of every kind (state boards, certification analysts, acquirers' diligence teams) read them:

• The management services agreement (MSA): scope of services and the fee. Fee design is the sensitive part: flat or cost-plus fees at fair market value are the conservative pattern, while pure percentage-of-revenue fees draw fee-splitting scrutiny in strict states.
• The stock transfer restriction agreement (sometimes a succession agreement): the mechanism ensuring the PC's ownership can transition to another licensed physician on defined triggers (death, license loss, departure) without the MSO ever owning the practice.
• The physician's employment or independent-contractor agreements, drawn so that clinical supervision runs through the PC's medical leadership, not through the MSO's org chart.
• The BAA and data terms between the entities, because the MSO touching patient data does so as a service provider to the practice, not as an owner of it.

The one-sentence test regulators apply: who controls clinical judgment? Every document should answer 'the PC and its clinicians,' and the operating reality has to match the paper.

Where the model gets challenged

The structure fails when it's a costume. Warning signs regulators and plaintiffs cite: the MSO hiring and firing clinicians for clinical reasons, setting protocols or quotas that override clinical judgment, sweeping every practice dollar so the PC is insolvent by design, or a friendly physician who owns thirty PCs and couldn't name this one's patients. Scrutiny of exactly these patterns has grown through the 2020s, including state legislative attention to investor-controlled practices, so the trend line favors substance over form.

Telehealth adds its own pressure points: intake flows designed by the business must still leave prescribing genuinely to the clinician (the same clinical-autonomy point certification reviewers probe), and marketing written by the MSO is still advertising a medical practice, so the claims rules land on it. This is why the compliance layer and the corporate layer can't be built by different teams that never talk.

Practically, the diligence moments when the structure gets read are predictable: LegitScript certification (the application asks about ownership and control directly), payment underwriting, malpractice placement, large partnerships, and any acquisition. Building it right once is dramatically cheaper than repapering it under a deal deadline.

Build it, buy it, or plug into one

Founders have three real options. Build the structure from scratch with healthcare counsel: full control, meaningful cost, and months of sequencing (entity formation, physician recruitment, agreements, state registrations) before the first patient. Acquire or partner with an existing practice: faster clinically, heavier diligence. Or plug into an operated platform where the PC, the clinician network, and the MSO machinery already exist and your brand rides on top.

That third option is what Embed Care sells: the clinical entity structure, the licensed network, and the management layer already built and maintained, so a brand launches on infrastructure that has already answered the ownership questions this guide describes. Whichever path you take, get the structure decided before the brand launches; it's the one layer that's painful to retrofit under a live patient base.