MSO-PC Structure for Telehealth: The Legal Setup — and the Lock-In Trap to Avoid

An MSO-PC structure pairs a Management Services Organization (your business entity) with a Professional Corporation (owned by a licensed physician) to comply with corporate-practice-of-medicine laws. Most states prohibit lay companies from owning a medical practice, so this split is how DTC telehealth operators legally employ or contract with prescribers while keeping their business running.

That is the answer to the question. Here is the answer that actually costs operators money when they miss it: the structure is also the mechanism some platforms use to lock you in — and most operators don't realise it until they try to leave.

---

Why You Can't Just Start a Telehealth Business

If you've built a DTC brand in e-commerce, supplements, or consumer health, your instinct is to incorporate an LLC, hire the people you need, and start selling. Telehealth doesn't work that way.

The corporate practice of medicine (CPOM) doctrine exists in some form in roughly 40 US states. The core rule: a lay entity — one not owned by a licensed physician — cannot own, operate, or control a medical practice. The rationale is that business pressure shouldn't distort a clinician's medical judgment.

In practice, this means your standard operating company cannot:

• Employ physicians and direct their clinical decisions
• Bill patients for medical services under its own name
• Own the physician-patient relationship

If you're building a telehealth clinic where providers write prescriptions or supervise a compounding protocol — TRT, HRT, peptides, hair, ED, LDN, tretinoin, weight management — you have a medical practice on your hands. You need a compliant structure before you launch, not after your first complaint.

---

What Is an MSO, and What Is a PC?

The Professional Corporation (PC)

The PC is the licensed entity. It is a medical practice, majority-owned by one or more physicians licensed in the relevant state. The PC is what patients technically see — it is the entity that employs or contracts with providers, holds the patient relationship, and issues the prescriptions or orders.

In some states (Texas, California, and a handful of others), the rules are particularly strict. California's ban on corporate medicine is essentially absolute; you must use a true PC with a physician majority owner. Texas operates under a Friendly-PC model with its own quirks. Florida, New York, and most other states have their own variations.

This is not a formation-only concern. You need a physician owner who is genuinely engaged, properly documented, and not just a name on a certificate. Regulators and malpractice counsel look through structures they believe are shams.

The Management Services Organization (MSO)

The MSO is your business entity — the one you actually own. It handles everything that isn't the practice of medicine:

• Technology and infrastructure
• Marketing and patient acquisition
• Billing support (not clinical billing — administrative billing support)
• Pharmacy coordination and fulfillment logistics
• HR and staffing for non-clinical roles
• Business development

The MSO contracts with the PC to provide these services. That contract — the Management Services Agreement (MSA) — defines the fee the PC pays the MSO for administrative support, which is typically structured as a percentage of practice revenue or a flat monthly fee. This is how your economics flow from the clinical entity back to you.

The physician owner of the PC retains full authority over clinical decisions. That is not a formality. If you build a structure where the non-physician MSO owner is effectively controlling prescribing decisions, you have an CPOM violation hiding behind paperwork. Don't do it.

---

Do You Need This Structure?

If your product involves a licensed provider reviewing and approving a clinical order, yes. The short answer is: if there's a prescription, there's a medical practice, and in most states that means you need an MSO-PC setup.

Here's a quick decision filter:

• Telehealth intake + compounding pharmacy + provider sign-off? Yes, you need this.
• OTC supplements or wellness content only? Probably not — but verify with counsel.
• Async consults with no prescribing? Depends on the state. Get counsel.
• You are a licensed physician yourself? You may be able to own the PC directly. Still worth structuring cleanly for scale.

This post is educational. Your specific situation — your state, your service mix, your provider relationships — needs qualified healthcare counsel. neolife's platform overview covers what the infrastructure handles; it does not replace a lawyer.

---

How the Structure Works in Practice

Walk through a live example: an operator launching a men's health clinic focused on TRT and hair.

1. Form two entities. An LLC (your MSO) and a Professional Corporation in the state(s) you're launching in. The PC is majority-owned by a licensed physician in that state.

2. Execute a Management Services Agreement. The MSO provides technology, marketing, and fulfillment support to the PC. The MSA defines scope, fees, and the hard line between administrative and clinical authority. Have healthcare counsel draft or review this.

3. Physician authority stays with the PC. The provider reviews every consult. Nothing ships without a licensed provider approval — not for regulatory compliance alone, but because that is the structure that protects the patient and the clinic. This isn't a hoop. It's the point.

4. Pharmacy relationship lives at the MSO layer (logistics, contracts, routing) or at the PC layer (the prescription order itself). Which entity holds which relationship depends on your state's pharmacy laws. Most operators use a pharmacy that accepts orders from the PC and coordinates fulfillment logistics through the MSO.

5. Patient data stays with the PC. The patient-physician relationship is owned by the PC. PHI cannot live on your Shopify store — it sits in your clinical stack, behind HIPAA-compliant infrastructure. See MVP compliance constraints for what Shopify can and cannot hold.

---

The Lock-In Trap: How Platforms Embed Themselves in Your Structure

Here is what most founders don't read in the fine print.

Platforms like TEHR, Wheel, OpenLoop, and others don't just provide software. They often provide the PC. Or more specifically: they have a relationship with a physician network that acts as the "Friendly PC" for your clinic — and that physician network, those providers, and sometimes the MSA template itself are all brokered through the platform.

This creates a compounding dependency:

• Your PC is the platform's network. The physician owner is their physician. The provider relationships are their relationships.
• Your MSA runs through their infrastructure. Switching platforms may require unwinding your MSA and finding a new PC owner.
• Your patient data may sit in their system. If the EHR is theirs, leaving means negotiating a data export — on their timeline.

Some operators have discovered this only when they tried to renegotiate pricing or move to a different tech stack. At that point, the leverage is entirely on the platform's side.

We are not saying any of these operators act in bad faith. We are saying the structure creates leverage that a clean, independent MSO-PC does not.

More on TEHR alternatives and how to evaluate your options.

---

How to Get the Structure Without the Lock-In

You want an MSO-PC that is legally sound, clinically real, and fully portable. Here is what that requires:

1. Use independent healthcare counsel

Do not let a platform's preferred legal partner draft your MSO documents. That attorney's client is the platform, not you. Hire your own healthcare attorney — one who has done MSO-PC structures in your target state(s) and has no relationship with your technology vendor.

Budget estimate: $5,000–$15,000 for initial structure and MSA drafting, depending on state count and complexity. This is not optional spending.

2. Establish a real physician relationship

Your PC's physician owner should be someone you chose, not someone a platform assigned. They should understand the clinic's model, have full authority over clinical policy, and be genuinely reachable. A name-only arrangement is a liability.

Some operators partner with a local physician; others find a physician-investor who takes a small equity stake in the PC in exchange for serving as owner. Both approaches work. The key is the relationship is real and documented.

3. Separate your clinical and operational stacks

• Patient data and PHI: lives in a HIPAA-compliant clinical system (EHR or equivalent), not your Shopify store, not a shared SaaS CRM.
• Order routing and fulfillment: can live in your operational infrastructure — a system you control and can move.
• Provider approval workflow: integrated into the order flow, not bolted on after the fact.

When your stacks are separated and you control the operational layer, switching any one component does not require unwinding your legal entity structure. That is portability.

4. Own your patient data

The patient consult, the health history, the prescription record — these need to be exportable from your system in a format you can move. If a vendor's contract restricts your data export rights, negotiate or walk. Data portability is not a nice-to-have; it is the thing that makes your patient base an asset rather than a liability.

50-state prescriber and telehealth licensing map covers the state-by-state variation in PC ownership rules and prescribing scope.

---

Where the MSO-PC Structure Meets Your Fulfillment Rail

Once your legal structure is clean, the operational question is: how does an approved prescription actually get to the patient?

This is where infrastructure matters.

When a provider approves a consult, a sequence starts: order confirmation, pharmacy routing, compounding or dispensing, shipping, and patient communication. In a well-built system, that sequence runs in under 60 seconds from approval to order confirmation — and every step is logged against the original consult in a system you own.

Platforms that also control this fulfillment layer have a second point of leverage over you. If order routing runs through their system, you are again dependent on their availability, their pharmacy relationships, and their pricing.

A clean setup — which neolife is built to support — separates the legal structure (your MSO-PC, your counsel, your physician) from the operational infrastructure (fulfillment routing, pharmacy connection, order status). You own the structure. The infrastructure just moves the orders. See how it works.

---

A Note on Provider Approval

Throughout this guide we have referenced "provider approval" repeatedly. That is intentional.

Nothing ships without a licensed provider approving the clinical order. Not a GLP-1 script, not a TRT protocol, not a tretinoin consult, not an LDN prescription. The MSO-PC structure exists to protect that approval chain — to make sure a real clinician with real authority is reviewing every patient case.

The regulatory requirement here is not the ceiling. It is the floor. Operators who treat provider approval as a checkbox to be minimized will have compliance problems; they will also have patient outcomes problems. Build your structure — legal and operational — so that provider approval is easy, fast, and auditable. Not because you have to, but because it is the right way to run a clinic.

---

Key Takeaways

• Most states ban lay-owned medical practices. The MSO-PC split is how you operate legally without being a licensed physician yourself.
• Your MSO and your PC are two separate entities. The PC must be majority-owned by a licensed physician in that state, not by you.
• TEHR, Wheel, and similar platforms sometimes embed themselves inside your MSO agreement — meaning leaving their platform can mean unwinding your whole legal structure.
• You can get a clean MSO-PC setup that is fully portable: your stack, your patient data, your physician relationship. The structure does not have to tie you to any vendor.
• Nothing ships without a licensed provider. The MSO-PC structure is what makes that provider relationship legally durable — protect it from day one.
• Get qualified healthcare counsel to review your specific state before launching. This post is educational, not legal advice.

---

Frequently Asked Questions

Do I need a separate PC in each state I operate in?

Often yes, but it depends on the state. Some states require a PC incorporated in-state with a physician licensed in that state. Others have more flexibility. A few states allow PA or NP-owned PCs under certain conditions. This is one of the highest-variance questions in telehealth formation — get state-specific advice. Our 50-state prescriber map is a starting point.

Can I be the physician owner of my own PC if I'm a licensed MD?

Yes, in most states. If you hold an active medical license in the relevant state and are clinically engaged with the practice, you may be able to own the PC directly. This simplifies the structure considerably. You will still want an MSA between your PC and your MSO-equivalent operating entity to separate clinical and business functions.

What happens if my Friendly-PC physician stops practicing or leaves?

Your MSA should have explicit provisions for physician succession — what happens if the PC owner becomes unavailable, loses their license, or wants to exit. Without this, you could face a gap in your compliant structure. Healthcare counsel should draft this before you sign anything.

Is the MSO-PC structure the same as a "Friendly PC"?

They are related terms. "Friendly PC" refers specifically to the physician-owned professional corporation that has a management services agreement with a lay MSO — where the physician nominally owns the entity but the lay operator runs the business. The degree of physician control required to avoid CPOM violations varies by state; some regulators have scrutinised "friendly PC" structures where the physician appeared to have no real authority.

How does HIPAA intersect with my MSO-PC structure?

Both the PC and the MSO may be covered entities or business associates under HIPAA, depending on what each entity does with PHI. You need Business Associate Agreements (BAAs) in place for any vendor that touches patient health information. Your Shopify store is not HIPAA-compliant by default and should not hold PHI. Your clinical stack — wherever PHI lives — needs proper BAAs and access controls.

---

How neolife Fits

neolife is not a PC provider. We do not supply the physician, manage the clinical relationship, or draft your MSA. That is intentional.

What we do is build the operational infrastructure that runs cleanly on top of a properly structured MSO-PC: Shopify-native order intake, provider approval workflow, multi-pharmacy routing, and order confirmation — all in a system that you own, with patient data that stays yours.

You bring the structure. We build the rail. See how neolife connects your clinic to your pharmacy.