Everything you were afraid to ask about the MSO-PC structure.

CPOM is a state-level legal doctrine that prohibits corporations and unlicensed individuals from practicing medicine, employing physicians to provide clinical care, or interfering with a clinician's independent medical judgment. It exists in some form in the majority of states, arising from medical practice acts, attorney general opinions, and case law rather than a single federal statute.

Its practical consequence for founders: if you are not a licensed physician, you generally cannot directly own the entity that delivers medical care. The MSO-PC structure exists to solve exactly this problem — a physician-owned Professional Corporation (PC) holds the clinical practice, while your Management Services Organization (MSO) owns the brand, technology, and business operations and supports the PC under contract.

Roughly 30+ states adhere to CPOM in some form, but strictness varies enormously. The consistently strict tier includes California, New York, Texas, New Jersey, and now Oregon (whose 2025 law is widely considered the most restrictive in the country). Colorado, Illinois, Ohio, Michigan, and North Carolina also apply meaningful restrictions. A smaller group — including Florida (for most physician arrangements), Alabama, and a handful of others — are considered permissive or effectively non-CPOM states.

Two cautions. First, "non-CPOM state" does not mean "no rules": fee-splitting prohibitions, anti-kickback statutes, and licensure laws still apply. Second, strictness is not static — the 2025–2026 legislative wave (Chapter IX) is actively re-tiering the map, so any static list should be re-verified before you rely on it.

Consequences stack across several dimensions: state medical boards can discipline or revoke the licenses of physicians involved; regulators or attorneys general can seek injunctions, civil penalties, and unwinding of the arrangement; contracts made in violation of CPOM (including your MSA) can be declared void and unenforceable, which means you may be unable to collect fees owed to the MSO; payers can claw back reimbursements; and in some states, unlicensed practice of medicine is a criminal offense.

The quieter but more common consequence for startups: diligence failure. Investors and acquirers routinely walk from — or reprice — deals where the CPOM structure looks sham-like. Enforcement is no longer theoretical: California's Attorney General has already reached a settlement with a management company over a friendly-PC arrangement, signaling that regulators look past paperwork to actual control.

Yes — and it applies in every state where your patients are located, not where your company is incorporated. A Delaware C-corp headquartered in San Francisco treating a patient in Texas is subject to Texas CPOM for that encounter. This is why multi-state telehealth companies typically operate a central MSO connected to one or more physician-owned PCs registered in each state they serve.

Telemedicine has also drawn disproportionate regulatory attention because the model scales fast and the corporate layer is often obvious. If you market care under your brand, set prices, and profit from clinical volume, regulators will treat you as being in the business of medicine regardless of what your homepage says.

Yes. Parallel doctrines exist for other licensed professions: Corporate Practice of Dentistry (CPOD — the reason DSOs exist), Corporate Practice of Veterinary Medicine, Corporate Practice of Optometry, and in some states restrictions covering psychology, therapy, nursing, chiropractic, and physical therapy. The mechanics are analogous: a licensee-owned professional entity delivers care; a management entity handles business operations.

The details differ by profession and state — which license types may co-own an entity, what the entity must be named, and how strict the fee rules are — so a structure copied from a medical model cannot be assumed to work for a dental or behavioral health company without review.

In strict CPOM states, no — professional entities must be owned (sometimes majority-owned, sometimes wholly) by appropriately licensed professionals. Some states allow limited co-ownership by other license types (e.g., a podiatrist or nurse in a California professional corporation up to a minority stake under the Moscone-Knox Act). In permissive states, a non-physician may be able to own a practice outright, though employment of physicians and fee-splitting rules may still constrain the design.

If you plan to operate nationally, design for the strictest states you'll enter. It is far cheaper to build the friendly-PC architecture on day one than to restructure a live business later.

Fee-splitting prohibitions bar licensed professionals from sharing professional fees with unlicensed persons or entities. They are related to but distinct from CPOM: a structure can satisfy ownership rules and still violate fee-splitting through its compensation design. The classic trap is a management fee set as a percentage of the PC's clinical revenue, which several states — most explicitly New York — treat as an unlawful split of professional fees.

Fee-splitting analysis is also where federal law enters: if any federal healthcare program dollars are involved, the Anti-Kickback Statute (a criminal, intent-based law) and Stark Law can apply on top of state rules. This is why fee design (Chapter VI) deserves as much attention as entity design.

The line generally falls at diagnosis, treatment, prescribing, and the ordering or interpretation of tests for an individual patient. Coaching, general wellness content, fitness programming, and non-diagnostic education typically fall outside the practice of medicine. But the line moves fast in practice: the moment your product involves prescriptions (including GLP-1s), lab orders, diagnoses, or individualized treatment plans delivered by licensed clinicians, you are in medicine and CPOM applies.

Common self-deceptions to avoid: calling prescribing "asynchronous review," calling clinical protocols "content," or assuming that contracting with clinicians as 1099s rather than employing them removes the issue. Regulators evaluate substance, not labels.

You may not strictly need one on day one, but most well-advised companies build it anyway, for four reasons: (1) you will almost certainly expand into a CPOM state, and retrofitting is expensive; (2) payers, including Medicare and Medicaid, often expect a professional entity structure for enrollment and reimbursement; (3) the separation cleanly isolates malpractice and clinical liability from the corporate balance sheet; and (4) investors underwrite the structure as standard — its absence raises questions even where it is not legally required.

The doctrine dates to the early 20th century and rests on a simple policy intuition: commercial interests should not dictate clinical decisions. Courts and legislatures worried that a corporation answerable to shareholders would pressure physicians on volume, coding, referrals, and treatment choices. The modern revival of the doctrine — aimed largely at private equity after high-profile collapses like Steward Health Care — runs on exactly the same theory.

This matters practically: every structural decision you make should be explainable in terms of protecting clinical independence. If your honest answer to "who decides clinical questions?" is anyone other than licensed clinicians, the structure will not survive scrutiny regardless of the paperwork.

Yes, at the margins. The MSO should avoid holding itself out as the provider of medical care. Best practice is a disclosure (usually in the footer and terms) explaining that medical services are provided by the affiliated professional entity or entities — often named, e.g., "[Brand] Medical Group, P.C." Marketing claims that the company "treats," "diagnoses," or "prescribes" are technically claims that a corporation practices medicine.

Advertising rules also apply to clinical claims themselves (FTC substantiation, state medical board advertising rules), and marketing that promises specific prescriptions before evaluation — "get your GLP-1 today" — attracts both board and FTC attention.

It is better understood as the settled compliance architecture than a loophole — it exists because states themselves recognize the distinction between clinical practice and business administration, and versions of it have been reviewed by regulators, courts, and thousands of transactions over decades. What the 2025–2026 wave (Chapter IX) targets is not the model itself but its abuse: arrangements where the MSO exercises de facto control over clinical matters while the physician owner is a figurehead.

Oregon's SB 951 is the significant exception — it restricts core features of the friendly-PC arrangement itself, and other states are watching. The defensible posture is a structure where the clinical independence is real, so that tightening laws change your paperwork rather than your business.

The MSO is the ordinary business corporation (usually your Delaware C-corp or an LLC subsidiary of it) that owns everything non-clinical: the brand and trademarks, the technology platform, marketing, payer contracting support, billing operations, HR and recruiting support, finance, and administration. It is the entity your investors own, the entity that employs your non-clinical team, and the entity where enterprise value accumulates.

The MSO earns revenue by providing these services to one or more professional entities under a Management Services Agreement, in exchange for a management fee. It does not — and must not — practice medicine, employ treating clinicians in strict states, or control clinical decisions.

The professional entity is the licensed-owner corporation that actually delivers care: it employs or contracts the clinicians, holds the clinical policies, bills payers, and appears on payer contracts and medical records. The label varies by state statute: Professional Corporation (PC) is most common; some states use or permit Professional Limited Liability Companies (PLLCs); Texas uses the Professional Association (PA); California requires a "Professional Medical Corporation" under Moscone-Knox naming rules.

The differences are more than cosmetic — states differ on which entity forms are allowed for medicine, who may own shares, officer/director license requirements, and naming conventions. Your formation counsel will pick the correct vehicle per state; your job is to keep the operational model consistent across them.

A friendly PC is a professional corporation owned by a licensed physician who is aligned with — "friendly" to — the MSO and its mission. The physician genuinely owns the PC and controls clinical matters, but a lattice of agreements (most importantly a stock transfer restriction or succession agreement) ensures continuity: the shares can't be sold to a stranger, and if the physician dies, retires, loses licensure, or departs, ownership transitions to another qualified physician designated under the agreed mechanics.

The critical nuance: "friendly" describes alignment, not subservience. Structures where the physician owner is a straw owner — paid a token fee, never consulted, signing whatever is sent — are exactly what regulators now target. The friendliness must coexist with real clinical authority.

Investors own the MSO. Enterprise value deliberately accumulates there: the brand, technology, data infrastructure, payer relationships (operationally), contracts, and the MSA economics itself. The PC is intentionally kept close to economically neutral — its revenue is largely consumed by clinician compensation and the management fee — so that it functions as a conduit for care delivery rather than a store of value.

At exit, what gets bought is the MSO (plus assignment or re-papering of the PC relationships). This is why sloppy PC economics — trapped cash, unclear intercompany balances, undocumented fee arrangements — directly damages the valuation of the thing you actually sell.

Most multi-state companies do not form 50 PCs. A common pattern is one "hub" PC registered as a foreign professional entity in many states, plus separate domestic PCs in the handful of states that effectively require them — New York and California are the usual culprits (New York generally will not recognize foreign professional entities for practice, and California's rules make a domestic professional medical corporation the standard answer), with a few others (e.g., New Jersey, Kansas) frequently added to the list depending on facts.

The result for a national footprint is typically 2–5 professional entities, each tied to the MSO by its own MSA. Every additional PC multiplies your banking, payroll, payer enrollment, and intercompany accounting surface — a fact that matters more operationally than legally (see Chapter VI).

When a company operates multiple state PCs, employing every clinician in the correct entity creates payroll and benefits chaos. The Mega PC pattern designates one professional entity as the employer of record for all clinicians, which then leases those clinicians to the state-specific PCs under an employee leasing (or personnel services) agreement. Clinicians get one W-2 and one benefits plan; the state PCs get properly credentialed staff.

This is a widely used but state-sensitive arrangement — some states restrict professional employee leasing or require the local PC to employ directly — so it needs counsel's sign-off per state, and the intercompany charges for leased staff need the same FMV discipline as the management fee.

Both patterns exist. Many startups simply have the topco C-corp act as the MSO. Others insert an MSO LLC subsidiary beneath the topco to isolate the management business, simplify state registrations and taxes, or ring-fence liability. A subsidiary structure becomes more attractive as you add regulated lines (a pharmacy entity, a lab entity, an ASO for behavioral health) that are cleaner as siblings than as activities of the parent.

Note that new laws increasingly define "MSO" functionally — California's AB 1415 reporting regime, for instance, captures entities by what they do for healthcare entities, not what they are named — so the choice affects administration more than regulatory exposure.

Several vendors operate pre-built professional entities with 50-state clinician networks that your brand can contract with — you plug into their PC rather than forming your own. This gets you to market in weeks, avoids formation and PC-owner sourcing, and suits companies validating demand or running an asset-light clinical layer.

The trade-offs: you don't control the clinical entity, payer contracts, or clinician relationships; unit economics carry the vendor's margin; and migrating patients and providers to your own PC later is a genuine project (payer re-enrollment, records custody, provider re-papering). A common lifecycle is rent-to-own: launch on a network, form your own MSO-PC once volume justifies it. Decide with eyes open about the migration cost you are deferring.

Structurally it is the same architecture — a dentist-owned professional entity supported by a Dental Support/Service Organization — governed by Corporate Practice of Dentistry rules. Differences show up in the details: dental boards in several states police DSO control aggressively (equipment ownership, patient records custody, and marketing control have all triggered enforcement); fee-splitting rules for dentistry can differ from medicine in the same state; and California's SB 351 explicitly covers dental practices alongside medical.

Each is its own licensed regime and usually its own entity: pharmacies require state board of pharmacy licenses (and non-resident licenses for mail order) and are commonly held in a separate pharmacy entity; clinical labs need CLIA certification and state licensure; DME suppliers need accreditation and Medicare enrollment if applicable. None of these belong inside the medical PC, and stuffing them into the MSO can trip ownership and anti-kickback rules — especially where the same enterprise both prescribes and dispenses.

If your model includes prescribing and fulfillment (the GLP-1 pattern), get specific advice on anti-kickback, state anti-self-referral rules, and the growing set of state laws on dispensing tied to telehealth prescribing.

The clinical relationship and the medical records belong to the professional entity, not the MSO. The MSO may host the EHR and process data as a business associate under HIPAA (with a BAA in place), but custody and control of records — and decisions about care — sit with the PC. This distinction matters at three moments: regulatory audits, PC-owner transitions (records must not be hostage to one physician), and any future migration between PCs or platforms.

Patient contact lists for marketing purposes are a separate, delicate topic — using clinical data for MSO marketing needs HIPAA analysis and often authorization.

They can share a great deal — that is the point of the model — but the sharing must be papered and priced. Shared space and equipment run through the MSA or a lease/sublease at fair market value. Shared personnel need clear allocation: clinical personnel belong to the PC; administrative staff belong to the MSO; anyone genuinely split should have documented allocation. Shared systems (EHR, telehealth platform) run through the MSA/technology license with a BAA.

What cannot be shared: bank accounts, clinical decision rights, and the corporate identity itself. Commingling in those three areas is the fastest way to make two entities look like one — which is precisely the finding that unwinds the structure.

Partially. Malpractice claims run primarily against the clinician and the professional entity, and a well-maintained separation keeps them there. But plaintiffs routinely name the MSO under theories like corporate negligence, negligent credentialing, or vicarious liability — and the more the MSO controlled clinical operations in practice, the stronger those theories get. Respecting the separation is thus a liability strategy, not just a compliance one.

Both entities need insurance: the PC carries medical professional liability (with adequate per-claim/aggregate limits and tail coverage planning), and the MSO carries its own E&O/management liability, cyber, and general commercial coverage.

It is the single organizing principle of modern enforcement: regulators, courts, and diligence teams evaluate how the arrangement actually operates, not what the documents recite. A perfect document set with an MSO that in practice hires and fires clinicians, sets clinical protocols, and sweeps every dollar nightly without invoices is a CPOM violation with good paperwork.

The MSA is the master contract between MSO and PC — the constitutional document of the whole structure. A well-drafted MSA covers: the scope of services (billing support, technology, marketing, HR support, facilities, finance); the management fee and its methodology; an explicit reservation of clinical authority to the PC and its clinicians; term, termination, and renewal mechanics; audit and records access; indemnification; insurance obligations; and compliance covenants including a change-of-law/severability clause that lets the parties reform terms if a state tightens its rules.

The two clauses that decide whether the MSA survives scrutiny are the fee clause (Chapter VI) and the clinical-authority carve-out: hiring/firing of clinicians, clinical protocols, treatment decisions, and clinical staffing levels must sit with the PC.

The STRA (also called a stock restriction, continuity, or succession agreement) is the document that makes the PC "friendly" durably. It restricts the physician owner from selling, pledging, or transferring PC shares without consent, and prescribes what happens on trigger events: death, disability, license loss, retirement, breach, or departure. On a trigger, shares transfer — typically for nominal consideration — to a successor physician who meets the agreement's qualifications.

Without it, your clinical entity is hostage to one person's life events: a PC owner who dies without succession mechanics can leave the shares to an estate, and an estate cannot own a professional corporation. Design notes: keep the successor-designation mechanics practical (a standing list beats a scramble), and check state law — Oregon's SB 951 restricts certain transfer-control arrangements, and other states may follow.

Beyond the MSA and STRA, a complete structure typically includes:

• Technology / IP license — the MSO licenses the platform, trademarks, and brand to the PC (often folded into the MSA, sometimes standalone).
• PC-owner agreement — the physician owner's compensation and duties for serving as owner (distinct from any clinical employment they hold).
• Clinician employment or contractor agreements — between the PC and its providers, with comp, supervision, and restrictive covenants as state law allows.
• Employee leasing agreement — if using a Mega PC pattern (§ 2.06).
• Business Associate Agreement — HIPAA coverage for the MSO's handling of PHI.
• Intercompany notes / working-capital agreements — if the MSO funds the PC's launch or smooths its cash cycle (§ 6.09).

The consensus reserved-to-PC list, drawn from state guidance and the new statutes: hiring, firing, and disciplining of clinicians; setting clinical protocols, standards of care, and quality policies; diagnosis and treatment decisions; clinical staffing levels and patient-panel decisions; medical record content and custody; scope of services offered as a clinical matter; and — under newer laws like California's SB 351 — influence over coding/billing judgments tied to clinical determinations and clinician noncompete terms.

The MSO can recommend, present data, source candidates, and administer processes for all of the above. The distinction between administering a process and deciding its outcome is where compliant structures live.

Terms of 5–20 years with evergreen renewals are common — investors like long terms because the MSA is the MSO's revenue engine. But termination design cuts both ways: an MSA the PC can never realistically exit reads as control; one the PC can exit at will terrifies investors. The usual compromise: long initial term, termination for cause on both sides, cure periods, and carefully limited without-cause rights, with transition-services obligations to protect patient continuity on any exit.

Most startup MSAs are exclusive in practice: the PC takes all covered services from the MSO, and the MSO serves only affiliated PCs. Exclusivity itself is generally acceptable, but pay attention to two edges: total exclusivity over every conceivable service can look like control (leave the PC theoretical freedom on genuinely clinical vendors), and if the MSO later wants to sell services to unaffiliated practices (a real revenue line for some companies), the agreements should not preclude it.

The PC. Payer agreements are contracts for the provision of medical services, and payers credential and contract with the professional entity and its clinicians (under the PC's Type 2 NPI and tax ID). The MSO typically performs the contracting work — negotiation support, credentialing operations, enrollment paperwork — under the MSA, but signature and legal party status belong to the PC.

Same logic for clinical vendor contracts (labs, pharmacies for clinical services) and anything creating clinical obligations. The MSO signs its own vendor stack: software, marketing, facilities, corporate services.

The MSO typically owns the brand, website, and acquisition machinery and licenses them to the PC — that is standard and value-accretive. The care needed is at the clinical boundary: intake flows that make treatment decisions (auto-approving prescriptions before clinician review), advertising that promises specific clinical outcomes, or scripts that steer diagnosis are marketing artifacts practicing medicine. Keep the funnel's job at generating and routing demand; keep clinical determinations behind a real clinician's judgment.

This area tightened sharply. The FTC's attempted nationwide noncompete ban stalled in litigation, but states moved anyway: California has long voided most noncompetes; SB 351 adds explicit limits on noncompete and non-disparagement provisions in the PE/MSO context; Oregon's law voids many physician noncompetes; and a dozen states restrict physician noncompetes specifically. Non-solicitation of patients raises its own patient-choice issues in several states.

The durable tools: confidentiality, IP assignment, non-solicitation of employees, garden-variety non-disparagement (where allowed), and above all economic alignment — a PC owner and clinical team who are fairly paid and genuinely engaged is better retention than any covenant.

They need maintenance. The clearest current example: California guidance around SB 351 indicates MSAs continuing past January 1, 2026 should be reviewed and amended — the law reaches existing arrangements, not just new deals. A good MSA anticipates this with a change-of-law clause obligating the parties to reform terms to preserve the arrangement's intent. Calendar an annual structure review, and a per-state review before each new state launch.

Yes. Under HIPAA the PC is a covered entity and the MSO — performing billing, technology, and administrative functions involving PHI — is its business associate. That relationship legally requires a BAA regardless of common ownership of the broader enterprise. Skipping it is one of the most common findings in diligence and one of the easiest to fix; being unable to produce it after a breach is much more expensive.

One well-built template family, localized per state. The economic architecture and service scope stay consistent; the localization handles state-specific fee rules (percentage prohibitions in NY, Oregon's structural limits), professional entity statutes, noncompete law, and any state filing requirements. Resist the temptation to negotiate bespoke economics per PC — heterogeneous MSAs are a diligence burden and an accounting headache, and consistency is itself evidence of an arm's-length, systematized arrangement.

1. Form the MSO (usually the Delaware C-corp you already have, or a subsidiary).
2. Pick launch states and determine the professional-entity map (§ 2.05).
3. Secure the friendly PC owner (Chapter V) — licensed in every launch state.
4. Form the PC(s): articles with state-required professional language, board/medical-board filings where required (e.g., New York's Department of Education process), EIN, registered agent.
5. Execute the document set: MSA, STRA, PC-owner agreement, BAA, tech license (Chapter III).
6. Open bank accounts for each entity separately and stand up the money-flow architecture before revenue arrives (Chapter VI).
7. Register the PC: NPI Type 2, state Medicaid/Medicare enrollment if applicable, malpractice coverage.
8. Hire/contract clinicians into the PC; credential and enroll with payers if in-network.
9. Stand up compliance operations: collaboration agreements where required, clinical protocols owned by the PC, telehealth modality compliance per state.
10. Document the launch economics: initial management fee methodology with FMV support, intercompany funding notes for pre-revenue costs.

Steps 6 and 10 are the ones founders most often defer — and the ones that surface in diligence a year later.

Wide range, driven by who does it and how many states. Rough 2026 market bands: tech-enabled formation services (Permit Health and similar) typically land in the low-five-figures for a single-state MSO-PC with standard documents, scaling with states; boutique healthcare firms commonly run $25k–$75k for a multi-state build with negotiated documents; BigLaw builds for funded companies frequently reach $75k–$200k+ once multi-state entity work, FMV support, and bespoke drafting are included. Ongoing costs — registered agents, annual reports, PC-owner compensation, collaboration fees, and FMV refreshes — typically add five figures annually.

Where not to economize: the MSA fee architecture, the STRA, and strict-state formations (NY, CA). Where you can: commodity filings, registered agents, and standard-state foreign registrations.

With an experienced team and an available PC owner: 2–6 weeks for a standard-state structure. Add time for: New York (its professional-entity approval process runs months, not weeks — start it first, § 4.08); payer enrollment if you're in-network (90–180 days per payer is normal and utterly unaffected by your urgency); DEA registrations per clinician per state if prescribing controlled substances; and Medicaid enrollment in slow states. The critical-path insight: entity formation is rarely the bottleneck — clinical licensure, credentialing, and payer enrollment are. Sequence them in parallel from day one.

The honest answer: the formation services are real and have compressed cost and time dramatically — many are themselves attorney-partnered — and for a standard structure in standard states they are often sufficient at launch. You should still want a healthcare attorney relationship for: strict-state entity work, anything touching controlled substances or federal program billing, FMV and fee design at scale, the 2026-wave amendments, and financing/M&A events where investor counsel will probe the structure.

A sensible pattern for a funded startup: formation service or startup-friendly boutique for the build; a named healthcare regulatory firm on retainer before your Series A. Investors will ask who your healthcare counsel is; "nobody yet" is a bad answer in diligence.

• Entity licensure/registration in each practice state (professional entity registration; some states require medical-board or professional-board registration of the entity itself).
• Clinician licensure in the patient's state for every treating provider — the non-negotiable core of telehealth compliance.
• NPI Type 2 for the PC; Type 1 for each clinician (§ 4.06).
• Malpractice coverage naming the PC and its clinicians.
• DEA registration per prescriber (and per-state registrations where required) if controlled substances are involved, plus state CSR licenses where applicable.
• Telehealth-specific registrations — a growing set of states (e.g., Florida's out-of-state telehealth registration) require registration even without a full license, and some require the entity to register.
• Payer enrollments if in-network (Medicare PECOS, state Medicaid, commercial credentialing).

Type 1 NPIs belong to individual clinicians; Type 2 NPIs belong to organizations — your PC gets a Type 2. Claims typically carry both: the rendering provider's Type 1 and the billing organization's Type 2. Common founder errors: billing under an individual clinician's NPI/tax ID after the PC exists (creates tax and payer chaos); forgetting each PC entity needs its own Type 2 and its own payer enrollments; and mismatching the NPI/tax ID/bank account triad in payer EFT enrollments — the payer pays whoever the enrollment says, and unwinding misdirected payments is miserable (§ 6.12).

California operates under the Moscone-Knox Professional Corporation Act plus an aggressive CPOM tradition. Key features: the entity is a "professional medical corporation" with statutory naming rules; ownership must be majority licensed-physician, with a defined list of other licensees permitted as minority shareholders within caps; officers and directors face licensure requirements; and the Medical Board and Attorney General actively police MSO overreach. As of January 1, 2026, SB 351 codifies the CPOM restrictions with explicit prohibited-control lists for PE/hedge-fund-backed structures, and AB 1415 adds a 90-day pre-closing notice regime for material transactions involving MSOs and healthcare entities (§ 9.02–9.03).

Three compounding reasons. First, New York generally requires a domestic professional entity — you cannot simply foreign-register your hub PC. Second, forming a New York PC/PLLC routes through the State Education Department with certificate-of-authority mechanics that run on a timeline of months and reject filings for technicalities. Third, New York's fee-splitting rule expressly prohibits percentage-of-revenue management fees, so your national fee architecture needs a New York-compliant variant (fixed or cost-plus, § 6.03). Founders' standing advice: if New York is on your roadmap, start its formation first, and consider vendors' pre-formed NY solutions if speed matters.

Texas maintains a strong CPOM prohibition: non-physicians cannot employ physicians for clinical care outside statutory exceptions (certain hospitals, federally qualified health centers, and other carve-outs in the Occupations Code). The professional entity is typically a Professional Association (PA) or PLLC owned by Texas-licensed physicians. Texas also has detailed delegation and supervision rules for NPs and PAs — prescriptive authority agreements with defined requirements — and an active board. MSAs get scrutinized for control; keep the reserved-clinical-powers list explicit.

• PC board minutes and annual meetings — the PC is a real corporation; an empty minute book supports the "sham entity" narrative.
• Annual reports and franchise taxes in every registration state — administrative dissolution of a PC mid-operation is a genuine disaster.
• Registered agent maintenance — service of process to a dead address means default judgments.
• Insurance certificates that actually name the right entities.
• An org chart that matches reality — entity names, ownership, and officers, updated when anything changes. Diligence starts here.

PCs default to C-corporation status federally (with the "personal service corporation" flat-rate regime), and many elect S-status where eligible to avoid entity-level tax — but S-eligibility interacts awkwardly with the friendly-PC arrangement, and the right answer depends on your consolidation approach, state taxes, and how close to zero the PC's taxable income runs after clinician comp and the management fee. This is one of the genuinely accountant-required questions: get a healthcare-literate tax advisor to design the PC tax posture alongside the fee architecture, not after it. (See § 6.10 on the "zeroing out" question.)

Sometimes — acquiring or affiliating with an existing practice brings payer contracts, credentialed clinicians, and revenue on day one, which is why the "buy the base" strategy is common. The costs: inherited liabilities (billing history, employment claims, malpractice tail), legacy payer contract terms you might not want, change-of-ownership filings with payers and Medicare (CHOW processes with their own timelines), and — in a growing set of states — transaction-review notice requirements that now cover practice acquisitions (§ 9.03). Diligence the practice like the acquisition it is.

The structure must exist before the first patient encounter, not before the first dollar of profit. Delivering care through your C-corp "just for the pilot" is practicing medicine through a general corporation — the violation is immediate, not deferred until scale. If speed matters more than ownership, the rent-a-PC route (§ 2.08) exists precisely for this stage. What can genuinely wait: additional state PCs (form as you enter states), in-network payer strategy (many launch cash-pay), and the Mega PC optimization (only matters at clinician scale).

• Annual reports/franchise taxes per entity per state; registered agent renewals.
• PC corporate formalities: board actions, officer confirmations, minute book.
• Management fee review against actual services; FMV refresh on a cadence (commonly every 1–3 years or on material change).
• Intercompany invoice and settlement discipline — monthly, documented (§ 6.07).
• Clinician licensure, DEA, and collaboration agreement renewals; chart-review documentation where required.
• Malpractice and corporate insurance renewals with correct named insureds.
• A change-of-law review: new state entries, and the moving 2025–26 legislation (Chapter IX).

Four sourcing channels, in rough order of prevalence for startups: (1) marketplaces and networks — Permit Health, Zivian, and similar platforms maintain vetted physicians (often 50-state licensed) who have held the role before; (2) your own clinical leadership — a chief medical officer or founding physician who takes ownership (with real independence mechanics); (3) referrals from healthcare counsel, who maintain informal benches of experienced PC owners; (4) an acquired practice's physician, in buy-the-base strategies. Whatever the channel, treat it as an executive hire: interview for judgment and engagement, check references from prior MSO relationships, and verify licensure and disciplinary history in every state.

Market compensation for the ownership role alone (excluding any clinical or CMO work) commonly runs from the low thousands to roughly $3k–$8k+ per month, scaling with the number of PCs/states, the physician's licensure breadth, specialty, and the depth of actual engagement expected. Marketplace-sourced arrangements sit toward the lower-middle of the band; nationally licensed, multi-entity, high-engagement arrangements price higher. Two design rules: compensation must be fair market value for the duties actually performed (documented — a comp that looks like a rubber-stamp fee supports the straw-owner narrative in both directions), and it must not be tied to the PC's revenue or profits.

If national scale is the plan, a 50-state (or broadly) licensed owner removes a scaling constraint: the owner must generally hold a license in each state where their PC practices, so a narrowly licensed owner either limits your map or forces multiple owners/PCs. The trade-offs: broadly licensed owners are scarcer and pricier, and the Interstate Medical Licensure Compact has made multi-state licensure faster for a committed physician, so "grow the licenses with the roadmap" is a viable middle path. Multiple PC owners for distinct entities is also a legitimate architecture — it just multiplies your succession planning.

The real version: reviews and approves clinical protocols; participates in credentialing and clinician hiring decisions; oversees quality assurance and reviews QA data; holds regular documented governance meetings; signs board filings knowingly; escalates and resolves clinical-business tension; and can describe all of it under questioning. The red-flag version: paid a token stipend, meets no one, reviews nothing, signs whatever arrives, and learned about the last three clinical policy changes from the documents themselves. The second version is the fact pattern behind the current enforcement wave — and it also fails diligence, because investors now interview PC owners.

Yes, and it's common — a physician co-founder owning the PC aligns everything neatly. The cautions: their MSO equity plus PC ownership concentrates the structure in one person (succession planning matters more, not less); their dual role needs clean hats — decisions as PC owner should be documented as such; and if they ever leave the company acrimoniously, they own your clinical entity, which is exactly what the STRA's trigger mechanics must anticipate. Some companies deliberately choose an outside owner to keep the clinical governance visibly independent; either answer is defensible if the mechanics are.

This is the STRA's job (§ 3.02): on a defined trigger, the shares transfer to a qualified successor physician for nominal consideration under the pre-agreed mechanics. Operationally you also need: a standing successor candidate (or a network relationship that can produce one fast — this is part of what the PC-owner marketplaces sell); a transition checklist covering bank signatories, payer notifications, board filings, and licensure-dependent registrations; and attention to states whose rules complicate transfer-on-trigger designs (Oregon's SB 951 restricts certain share-transfer control arrangements). An unplanned PC-owner transition with no successor is one of the few events that can genuinely halt a care delivery business.

Frequently yes — MSO equity or options for the PC owner aligns incentives and is common practice. Watch three things: state law limits (Oregon's new regime restricts MSO-owner overlap with the professional entity; other states may follow); the optics of compensation — equity is fine, but the ownership role's cash comp should still be FMV for duties; and anti-kickback analysis if federal program dollars flow and the equity could look like payment for referrals. Disclose the overlap plainly in diligence; concealed alignment reads worse than documented alignment.

A single owner across all entities is operationally simpler — one relationship, one succession plan, consistent governance — and is the default when the owner's licensure supports it. Multiple owners arise when licensure doesn't stretch, when specialties differ by entity (a behavioral PC and a medical PC may warrant different owners), or when a state's rules or an acquisition dictate it. If you run multiple owners, standardize the agreements and calendar the governance so no entity becomes the neglected one — diligence will find the PC with no minutes.

• License verification in every relevant state, plus NPDB/board disciplinary history and OIG/SAM exclusion checks.
• References from at least one prior MSO relationship — ask specifically how they handled a disagreement with management.
• Concurrent-commitment count: an owner serving dozens of PCs simultaneously cannot credibly govern yours, and regulators have noticed the "serial PC owner" pattern.
• Specialty fit for your clinical model — a plausible owner for a dermatology practice may be implausible for psychiatry.
• Insurance and financial basics: no personal circumstances that make a share-transfer trigger likely or messy.

Three distinct legal roles, often confused because one physician can hold more than one: the PC owner owns the professional entity and holds corporate/clinical governance duties; a medical director provides clinical leadership and protocol oversight for an organization or service line (a contractual role, not ownership); a collaborating/supervising physician fulfills state-mandated oversight of NPs and PAs under a collaboration or supervision agreement (§ 7.02). Each role has separate duties, compensation, and agreements — paying someone one fee for an undifferentiated blend of all three creates both compliance and FMV problems.

The canonical flow has a strict order: patient and payer revenue is paid to the PC (its accounts, its tax ID, its payer enrollments) → the PC pays its own clinical obligations (clinician compensation, malpractice, clinical vendors) → the PC pays the MSO its management fee under the MSA, against an invoice → the MSO funds its operations and, ultimately, investor returns. Every arrow is a documented, contract-backed transfer between separate bank accounts.

The inverted flow — revenue landing in the MSO and being "allocated" to the PC — is the classic strawman fact pattern regulators cite, because it makes the corporation the real recipient of professional fees. Getting the direction right on day one is cheaper than every alternative.

Minimum viable architecture: one operating account per legal entity, no exceptions. Common mature architecture: each PC holds a payer-receipts account (the landing zone for ERAs/EFTs and lockbox deposits) plus an operating account; the MSO holds operating, payroll, and reserve accounts. Multi-PC groups often add sub-accounts per PC per function so reconciliation maps one-to-one with the ledger. Signatory design matters: PC accounts should have PC-authorized signers (the PC owner, typically with MSO finance staff holding operational access under the MSA rather than unilateral discretion over clinical funds).

The three structures and their standing:

• Fixed (flat) fee — a set monthly amount grounded in a valuation of services. The most defensible nationwide; brittle as the business grows, so build in periodic true-ups.
• Cost-plus — MSO's allocated costs plus a reasonable markup. Widely used and defensible; requires honest cost accounting.
• Percentage of revenue — the risky one. New York expressly prohibits percentage-of-revenue compensation as fee-splitting; Florida restricts it in referral contexts; many states disfavor it. California is comparatively permissive where the percentage is commercially reasonable and tied to non-referral administrative services — but a national company needs the strict-state answer anyway.

Prevailing advice for multi-state companies: fixed or cost-plus, supported by FMV documentation, reviewed on a schedule. If someone proposes a percentage because it's easier to model, show them New York.

FMV means the fee two unrelated parties would negotiate for the same services at arm's length — payment for identifiable administrative services at commercially reasonable rates, independent of clinical revenue. Support typically combines: a services inventory (what the MSO actually provides, itemized); market benchmarking against third-party vendor pricing for comparable services; cost build-ups; and, at scale or before transactions, an independent third-party FMV opinion from a healthcare valuation firm. Document the methodology, refresh it when services or scale change materially, and keep the file where diligence can find it.

The failure mode isn't usually a wrong number — it's a fee that was set casually years ago, never revisited, and now bears no explicable relationship to the services. Regulators and buyers both read that as a split dressed as a fee.

The sweep is the recurring transfer of the management fee (and other contracted charges) from PC accounts to the MSO. A compliant sweep is: invoiced (the MSO bills the PC per the MSA's methodology), approved (PC-side authorization — the PC owner or their delegate approves or holds a veto window), scheduled (monthly is the norm; daily automatic sweeps of every dollar look like the MSO owns the revenue), sized by the contract (the transfer matches the invoice, not "whatever's in the account"), and recorded (booked identically on both entities' ledgers with the invoice attached).

An auditable approve-then-transfer workflow between entity accounts is precisely the kind of thing worth automating — the discipline that protects the structure is the discipline nobody sustains manually.

Access, yes; unilateral control, no. It is standard for the MSA to authorize the MSO to perform treasury operations for the PC — receiving deposits into PC accounts, running payables, executing the invoiced fee transfer. What draws fire is the MSO holding sole dominion: MSO-only signatories, the PC owner lacking visibility or authority over the PC's own funds, or the MSO moving PC money outside the contracted mechanics. Several of the new state laws list control over the practice's funds and banking among the prohibited forms of MSO control. Design principle: the MSO operates the pipes; the PC owns the water and can see every valve.

Every dollar crossing an entity boundary needs three artifacts: a contract basis (which agreement authorizes this category of transfer — MSA fee, leasing charge, expense reimbursement, intercompany loan), a transaction document (invoice, reimbursement schedule, or note draw), and matched ledger entries on both entities' books that tie to the bank movement. Monthly settlement with a reconciliation of intercompany balances to zero (or to a documented running balance under a note) is the standard cadence.

The anti-pattern: a single "due to/due from" account that grows for two years, absorbs every uncategorized transfer, and gets "trued up" the week diligence starts. Every healthcare CFO has seen it; none of them lend it credibility.

• Payer deposits (checks or EFTs) landing in MSO accounts because enrollment paperwork listed the wrong entity or account.
• One card or account paying both entities' vendors, sorted out later "in the books."
• Clinician payroll run from the MSO's payroll account without a leasing agreement or reimbursement mechanics.
• Round-number transfers between entities with no invoice, memo, or contract basis.
• The PC's tax refund, credit card rebates, or vendor refunds deposited wherever was convenient.
• A shared "company" account from the early days that both entities never quite left.

Each instance is individually small; collectively they support the argument that the two entities are one enterprise — which collapses both the CPOM defense and the liability shield.

The MSO almost always funds the launch: formation costs, early clinician compensation, malpractice premiums, working capital through the payer-payment lag. The compliant mechanics are (a) an intercompany loan or revolving working-capital note — documented, with commercially reasonable terms, drawn and repaid on the books — and/or (b) deferred management fees that accrue until the PC can pay. What to avoid: undocumented cash injections, or "capital contributions" from an entity that legally cannot own the PC. The note also matters at exit — buyers need to see how launch funding will be treated in the purchase mechanics.

In practice the fee architecture typically leaves the PC near break-even — its revenue covers clinician costs and the management fee, with modest retained earnings. Near-zero is normal and expected. The nuance: the fee must get there via a defensible methodology (FMV for services), not via a clause that simply defines the fee as "all remaining profit" — a profit-stripping formula is functionally a percentage fee at 100%, the least defensible design of all. Leave the PC genuinely solvent: it must cover its liabilities, maintain reserves appropriate to its obligations, and never depend on same-day MSO top-ups to clear payroll.

Treating clinicians are employed (or contracted) by the professional entity in strict states — full stop. Payroll therefore runs from PC funds: either the PC operates its own payroll directly, or a Mega PC employs everyone and leases staff to sibling PCs with invoiced intercompany charges (§ 2.06). The MSO can administer payroll operations (running the platform, managing benefits) as a service under the MSA — administration is fine; being the employer of clinical labor in a strict state is not. The recurring operational bug: the MSO fronts payroll cash "temporarily" and the reimbursement mechanics never get papered. Paper them.

Each payer requires enrollment linking the PC's tax ID, Type 2 NPI, and bank account before it will pay electronically and deliver remittances — through payer portals and intermediary networks (Availity, Optum Pay, Zelis, EnrollSafe, and Medicare's contractors like Noridian and Novitas, among others). Each PC entity enrolls separately, per payer, and timelines run weeks to months per enrollment.

The standard failure modes: enrollments pointing at the wrong entity's account (instant commingling); virtual card payments silently substituting for EFT and eating 2–3% in fees until someone opts out; paper checks continuing to a lockbox nobody reconciles; and no tracking of enrollment status across dozens of payer/entity pairs. Treat enrollment as a managed program with an owner and a tracker — or use infrastructure that manages it for you — because every gap is unreconciled or misdirected revenue.

Refunds of clinical fees are the PC's obligation and should be paid from PC funds — the entity that earned the revenue returns it. Operationally this trips companies whose payment processor is contracted at the MSO level: the refund then flows from the wrong entity and creates an intercompany imbalance every time. Align the processing entity with the earning entity, and where card-network mechanics force the original-instrument refund through a particular account, document the intercompany settlement that trues it up. Also mind state escheatment rules for uncashed refunds and credit balances — payers and states both audit credit-balance hygiene.

Maintain per-entity books that consolidate cleanly: a chart of accounts consistent across entities; intercompany accounts that reconcile monthly; revenue recognized in the PC and fee income in the MSO; and consolidated statements (most VC-backed MSO-PC groups consolidate the PCs as variable interest entities — § 8.05). The Series A request list will include: consolidated and per-entity financials; the intercompany ledger with supporting invoices; the MSA and fee methodology with FMV support; bank statements per entity; payer enrollment and AR aging by entity; and the working-capital note history. If producing that list would take you a quarter, start now — the companies that close fast are the ones whose money story is already legible.

The patient's state, as a near-universal rule — the encounter is deemed to occur where the patient is located. Some relief valves exist: the Interstate Medical Licensure Compact expedites multi-state physician licensure; the Nurse Licensure Compact covers RNs (not NPs, in most respects); PSYPACT covers psychologists; and a handful of states offer telehealth-specific registrations short of full licensure. Build your clinician-to-state coverage matrix early — it drives hiring, scheduling logic, and how fast you can turn on a new state.

It depends entirely on state practice-authority law. States split into full practice (NPs practice independently — roughly half the states), reduced practice (a collaboration agreement is required for some elements), and restricted practice (supervision/delegation required, e.g., Texas and California's transition frameworks). Several full-practice states impose a supervised transition-to-practice period on newly licensed NPs before independence. PAs have a parallel but distinct map. For a multi-state NP-heavy model, the collaboration requirement is a real operating cost and compliance program — physician ratios, chart-review percentages, meeting cadences, and board filings vary state by state.

Market rates commonly run in the hundreds of dollars per NP per month — varying with state burden, specialty (psychiatric collaboration prices higher), and chart-review volume — sourced through platforms (Zivian, Collaborating Docs, and peers) or direct relationships. The physician's duties are state-defined: availability for consultation, periodic chart reviews at mandated percentages, documented meetings, and in some states board-filed agreements and prescriptive-authority delegation. The compliance risk isn't the agreement's existence — it's the documentation: unperformed chart reviews and unheld meetings are what board audits find.

The PC must own and approve clinical protocols, whatever their engineering provenance. In practice: the MSO's clinical-product team can draft, research, and encode protocols into the platform, but adoption requires documented review and approval by the PC's clinical governance (medical director/PC owner and clinical committee), and changes follow the same path. This is not ceremony — it is the operational expression of clinical independence, and it is one of the first things the new statutes and diligence questionnaires probe. Keep an approval log tying each protocol version to its approving clinician and date.

State telehealth practice standards govern whether a valid clinician-patient relationship can be established asynchronously — via an intake questionnaire reviewed by a clinician — and the map has been liberalizing but remains uneven. Some states require a synchronous (video/audio) encounter for initial prescribing generally or for specific drug classes; questionnaire-only models have drawn board enforcement in several states; and controlled substances live under the stricter federal framework (§ 7.06). The design implication: your intake flow must be state-configurable, and "we launch async everywhere and see" is a board-complaint generator.

The Ryan Haight Act requires an in-person evaluation before prescribing controlled substances via telemedicine, subject to exceptions. The COVID-era flexibilities that suspended this requirement have been repeatedly extended while the DEA works toward a special-registration framework for telemedicine prescribing — proposed rules have been published and revised, and the landscape remains in motion. If controlled substances are core to your model (psychiatry, addiction medicine with buprenorphine, ADHD): track the DEA rulemaking as an existential dependency, layer state controlled-substance telehealth rules on top, register prescribers appropriately (federal DEA per state of practice, plus state CSR where required), and build the in-person-capable fallback your category may need. Verify the current status before launch — this answer has a short shelf life by design.

The PC carries medical professional liability covering the entity and its clinicians (per-claim and aggregate limits sized to specialty and volume; telehealth-experienced carriers matter because coverage must match your modality and state footprint). Understand claims-made vs. occurrence forms and who funds tail coverage when clinicians depart — a chronically under-negotiated term in clinician agreements. The MSO carries its own tower: general liability, E&O/professional for its services, cyber (non-negotiable given PHI), and D&O once institutionally funded. Verify additional-insured and named-insured designations actually match your entity names.

Sometimes, but the space is narrowing. Worker-classification tests (California's ABC test and its cousins) make contractor status hard to sustain for clinicians working your protocols, your schedule, your platform, exclusively; misclassification brings wage-and-hour, tax, and benefits liability. Clinical nuances too: some payers and states expect employment for certain enrollment types, supervision structures assume employment relationships in some states, and malpractice arrangements differ. Fractional, multi-platform clinicians with genuine independence fit 1099 better; your core clinical workforce usually belongs on W-2 with the PC (or Mega PC).

A real privacy and security program: risk analysis (the single most-cited OCR gap), administrative/technical safeguards, workforce training, breach response procedures, minimum-necessary access design across the MSO/PC boundary, and BAAs downstream with every vendor touching PHI (EHR, telehealth platform, billing, analytics, cloud). Two structure-specific notes: MSO staff access to clinical data should be role-scoped (marketing does not need charts), and analytics/advertising pixels on patient-facing properties have driven a wave of enforcement and litigation — audit your tracking stack before someone else does.

Earlier than feels natural. A lightweight clinical governance rhythm — a quality committee that meets (even briefly), reviews cases and metrics, documents findings, and owns protocol changes — serves four masters at once: state collaboration/supervision requirements, payer credentialing and delegated-credentialing ambitions, the substance-over-form defense of the whole structure, and your own clinical safety. It also produces the artifact diligence loves most: a paper trail proving clinicians govern care. Start it at your first ten clinicians, not your first hundred.

They own the MSO — a normal Delaware C-corp with normal preferred stock — and the MSO's economics derive from its contractual relationship with the PC(s). The investor never owns clinical equity; the MSA (plus the STRA's continuity mechanics) is what makes the MSO's revenue durable enough to underwrite. This is settled, well-trodden architecture: essentially every VC-backed care delivery company of the last decade is built this way, and sophisticated healthcare investors evaluate the quality of the arrangement rather than its existence.

• Documents: MSA, STRA, PC-owner agreement, BAA, entity formation records, per-state good standing.
• Fee integrity: methodology, FMV support, invoices matching transfers, no percentage fees in prohibited states.
• Substance: increasingly, interviews with the PC owner and medical director; protocol approval logs; clinical hiring records showing PC decision-making.
• Money hygiene: per-entity bank accounts, intercompany ledger, payer enrollments pointing at correct entities, no commingling patterns.
• Regulatory exposure: state footprint vs. licensure, collaboration compliance, controlled-substance posture, marketing claims, pixel/tracking exposure.
• Change-of-law readiness: post-2026, whether CA/OR-era amendments have been made.

The pattern across failed processes is rarely a missing document — it's a money trail or a control reality that contradicts the documents.

One slide, four sentences: state law requires licensed clinicians to own the medical practice, so clinical care sits in a physician-owned professional entity; our company owns everything that scales — brand, technology, operations — and supports the practice under a long-term services agreement at market-rate fees; continuity agreements ensure the practice remains aligned through any physician transition; this is the standard structure used by [name three respected companies in your category]. Then stop. Generalists don't need the statute citations; they need to hear that it's standard, durable, and that value accrues to the entity on the cap table.

• Commingled money — the #1 killer, because it's slow to remediate and impossible to hide (§ 6.08).
• A straw PC owner who can't describe their role under gentle questioning.
• Percentage fees in New York (or profit-stripping formulas anywhere) discovered mid-process.
• Practicing before the structure existed — early encounters delivered through the C-corp, discoverable in the records.
• Licensure gaps — patients treated in states where the clinician wasn't licensed; boards and buyers both find these.
• Marketing/clinical boundary violations — intake funnels that auto-promise prescriptions.
• Unmade 2026 amendments — stale MSAs in California/Oregon after the effective dates.

None of these usually kill at term sheet; they kill (or reprice, or escrow) at confirmatory diligence — the most expensive possible moment.

Under U.S. GAAP (ASC 810), a PC the MSO doesn't own can still be consolidated as a variable interest entity when the MSO holds the controlling financial interest in substance — which the MSA/STRA architecture is generally designed to establish. Practical consequence: audited financials present the PCs consolidated with the MSO (patient revenue on top, with the intercompany fee eliminating), which is what investors expect and what makes your revenue "yours" for fundraising narratives. Get an audit firm with healthcare VIE experience; the consolidation memo is a standard artifact, and metrics like "revenue" in your deck should match the consolidation approach your auditors will bless.

No. The cap table is the MSO's; the PC's shares are held by the friendly physician under the STRA and never carry investor economics. What investors will want alongside the cap table is the structure chart — entities, ownership, and the agreements connecting them — and confirmation that nothing grants anyone equity-like rights in the PC (profit interests in a professional entity are a red flag in strict states). PC-owner incentive equity lives at the MSO level (§ 5.07).

The MSO — by stock sale or merger like any company — with the PC relationships traveling via the existing agreement lattice: the buyer steps into the MSA economics, and the STRA's mechanics permit an orderly PC-owner transition if the buyer wants its own physician. Deal-specific work includes: assignment/change-of-control clauses in the MSA (negotiate these on day one — a consent right you gave the PC owner casually becomes leverage at exit), payer contract change-of-ownership processes, state transaction-review filings that now capture MSO deals in several states (§ 9.03), and treatment of intercompany balances in the purchase price mechanics.

A growing set of states — California (AB 1415, effective January 1, 2026), Massachusetts, Indiana, New Mexico, Connecticut, Maine, Colorado, Illinois, and others — require advance notice (California: 90 days) or review for material healthcare transactions, with several regimes explicitly covering MSOs and PE investors. For deal planning this means: map the notice states early in any process, build the notice period into the closing timeline, and expect data-submission obligations. Most regimes are notice-and-transparency rather than approval — but a missed filing is an unforced error with penalties, and buyers will diligence your compliance with them.

The instruments themselves are standard — they sit at the MSO/topco. What's healthcare-specific: representations and warranties about regulatory compliance and the MSO-PC structure (expect them from institutional leads; make sure they're true before signing); covenants about the structure's maintenance; and, under the SB 351-era laws, care that investor protective provisions don't reach into prohibited-control territory (an investor consent right over "hiring clinical leadership," for instance, is now a drafting error in California). Sophisticated healthcare counsel on both sides will navigate this routinely; generalist paper may not.

A pragmatic sequence: pre-launch — correct entity structure, core document set, separate banking, licensure matrix (non-negotiable at any stage); seed — fee methodology documented, collaboration compliance operational, monthly intercompany discipline, basic clinical governance; Series A prep — third-party FMV opinion, healthcare regulatory counsel engaged, VIE-experienced auditors, data room built to the § 6.14/§ 8.02 lists, 2026-wave amendments made; growth — annual structure reviews, per-state compliance calendar, delegated credentialing, internal audit rhythm. The principle: compliance debt compounds like technical debt, and the interest rate spikes exactly when you can least afford it — mid-process.

Seed investors routinely accept rented clinical infrastructure as a speed decision. By Series A, expectations shift: owning your MSO-PC means owning payer contracts, clinician relationships, unit economics, and the data — the things the valuation is built on. A credible migration plan (or a completed migration) is usually the ask. If you intend to stay asset-light on the clinical layer as a strategy, be able to defend the margin math and the platform-dependency risk explicitly; some models genuinely warrant it, but it's a choice to justify, not a default to drift into.

Run your own mock diligence: pull the § 8.02 list, attempt to produce every item in 48 hours, and interview your own PC owner cold. The gaps you find — the unsigned BAA, the intercompany account nobody can explain, the FMV memo that predates half your services — are each cheap to fix now and expensive to explain later. Companies that do this annually close financings measurably faster, because the data room is a byproduct of operations rather than a quarter-long archaeology project.

A legislative and enforcement cycle driven by concern over private equity in healthcare — catalyzed by high-profile failures like Steward Health Care — produced the most significant tightening in decades: California and Oregon enacted the strictest new laws; Massachusetts, Indiana, New Mexico, Connecticut, Maine, Colorado, and Illinois added transaction-review or transparency regimes; more states have bills pending; and enforcement moved from theoretical to active, with California's AG already settling with a management company over a friendly-PC arrangement. The through-line: regulators now examine what MSOs actually control, not what the documents say.

Effective January 1, 2026, SB 351 codifies California's CPOM/CPOD restrictions with a focus on private equity groups and hedge funds: they may not interfere with licensed professionals' clinical judgment or exercise specified forms of control over medical and dental practices — including through MSOs. The codified prohibited-control themes include influence over clinical hiring/firing, treatment and diagnostic decisions, patient-care policies, and related clinical determinations, and the law adds restrictions on noncompete and non-disparagement provisions in these arrangements. It also gives the AG explicit enforcement tools. Practical takeaway: PE/fund-touched structures operating in California should have completed an MSA and governance review; even structures without PE backing should treat the codified control list as the state's definition of what MSOs must not do.

Also effective January 1, 2026, AB 1415 expands the Office of Health Care Affordability's transaction-review regime: "noticing entities" — now explicitly including private equity groups, hedge funds, MSOs, and entities that own or control providers — must give OHCA written notice at least 90 days before material transactions (sales, transfers, changes of control involving healthcare entities or MSOs). It also imposes data-reporting obligations on MSOs, with implementing regulations still being detailed. It applies to qualifying transactions from 2026 onward, including material changes to pre-existing arrangements — existing relationships aren't grandfathered against future transactions. Deal-planning consequence: the 90-day clock now belongs in every California-touching timeline.

Because it restricts the friendly-PC machinery itself, not just its abuse: SB 951 (as amended by HB 3410) bars MSOs and their owners/officers from owning or controlling a majority of a professional medical entity they manage, restricts overlapping ownership and governance between MSO and practice, limits the share-transfer control arrangements that make PCs "friendly," and voids many physician noncompetes — with staggered effective dates (January 1, 2026 for new arrangements; January 1, 2029 for pre-existing ones). Companies operating in Oregon need Oregon-specific structuring, and everyone else should watch whether the model propagates: several states floated similar bills in the 2025–26 sessions.

Partially, and don't relax. Some provisions are drafted around "private equity groups and hedge funds" — and whether a given venture fund falls in scope involves definitional analysis that counsel should do rather than founders assuming. But much of the wave applies regardless of investor type: AB 1415's noticing regime covers MSOs as such; Oregon's structural rules govern the arrangement, not the fund behind it; and the codified control lists are being read as statements of what CPOM always meant. The safe operating assumption: build to the standard, because the "we're VC, not PE" argument is a thin place to stand in an enforcement action.

Beyond CA and OR: Massachusetts expanded transaction oversight and false-claims exposure for investors; Indiana, New Mexico, Connecticut, Maine, Colorado, Illinois added or expanded transaction notice/review regimes; Washington, Vermont, and others have run CPOM-strengthening bills; and New York perennially considers expanded review. The pattern to internalize: transaction transparency is spreading fastest, control restrictions second, Oregon-style structural limits are the frontier. Assign someone (or a service) to track state sessions — this FAQ's Chapter IX will age faster than any other chapter.

1. Amend MSAs to carve out the statutorily-listed clinical controls explicitly (hiring/firing of clinicians, protocols, coding judgment, patient-care policies).
2. Audit governance reality: protocol approval logs, PC-owner engagement records, clinical hiring files showing PC decisions.
3. Review noncompete/non-disparagement provisions against the new state limits.
4. Fix the money mechanics to the Chapter VI standard — invoiced fees, per-entity accounts, documented intercompany.
5. Map your transaction-notice exposure and build the filing calendar into any deal planning.
6. Oregon-specific structuring if Oregon is in footprint; a watch process for copycat bills.
7. Re-verify annually. The half-life of this checklist is about twelve months.

Yes — with the caveat that the margin for sloppy versions has collapsed. The model remains legal and standard in the overwhelming majority of states; the new laws overwhelmingly target control abuses rather than the architecture; and no realistic alternative exists for non-physician-founded care delivery at scale. The strategic read: structures built with real clinical independence, clean money mechanics, and documented substance now enjoy a widening moat, because the enforcement wave raises the cost of the corner-cutting versions competitors run on. Compliance quality is becoming a competitive asset rather than a tax.

1. Form the structure before the first patient encounter.
2. One bank account per entity, minimum, from day one.
3. Revenue lands in the PC; fees move by invoice; everything reconciles monthly.
4. Fixed or cost-plus fees with written FMV support — designed for your strictest state.
5. A real PC owner with real duties, real compensation, and a signed STRA with succession mechanics.
6. Clinical decisions — hiring, protocols, treatment — documented as the PC's.
7. Licensure in the patient's state, every encounter, no exceptions.
8. A BAA between MSO and PC, and down the vendor chain.
9. Corporate formalities for the PC: minutes, filings, insurance, good standing.
10. An annual structure review against the moving law.

1. Don't deliver care through your C-corp "just for the pilot."
2. Don't run one account, one card, or one payroll for two entities.
3. Don't sweep PC cash daily, automatically, and un-invoiced.
4. Don't sign a percentage-of-revenue fee and hope New York never notices.
5. Don't hire a PC owner you'd be embarrassed to have interviewed by a regulator.
6. Don't let marketing promise prescriptions before a clinician has judged anything.
7. Don't treat the collaboration agreement as paper — the chart reviews have to actually happen.
8. Don't put analytics pixels on patient flows without a privacy review.
9. Don't defer the intercompany paperwork to "when we're bigger."
10. Don't assume last year's structure survives this year's legislature.

Launch: practicing pre-structure; wrong entity type in a strict state; payer enrollments pointing at the wrong account; no working-capital note for MSO funding. Growth (the dangerous middle): the fee methodology frozen while services tripled; intercompany balances accreting undocumented; new states launched on the hub PC where a domestic PC was required; collaboration compliance outrunning its documentation. Scale: heterogeneous per-PC agreements from ad-hoc deals; the Mega PC leasing charges never FMV'd; governance theater (committees that exist on paper); stale structures meeting new statutes. The middle stage causes the most diligence damage — early mistakes are small and late-stage companies have counsel; growth-stage companies have neither excuse nor infrastructure.

Remediation is normal and survivable — most funded companies have done some. The playbook: (1) diagnose comprehensively with counsel under privilege before touching anything; (2) fix architecture first (accounts, enrollments, agreements), then reconstruct history (recreate the intercompany ledger, paper the past transfers as note draws or fee true-ups where defensible); (3) memorialize the remediation — a dated cleanup with board awareness reads far better in diligence than a discovered mess; (4) don't backdate anything, ever — documents can be effective-dated transparently, but forged history converts a compliance issue into a fraud issue. Disclose remediated issues proactively in diligence; buyers price discovered problems far more harshly than disclosed ones.

Not the absence of issues — everyone has issues. The differentiators observed across processes: money mechanics that reconcile (the single strongest signal, because it can't be dressed up retroactively); a PC owner who is visibly real; documentation produced in hours rather than weeks; proactive disclosure with remediation narratives; and a team that can explain why each structural choice was made rather than reciting that counsel told them to. Structure quality turns out to be a proxy investors trust for operational quality generally — which is the deepest reason to build it right.

A realistic seed-stage stack: formation via a specialized service or boutique firm; PC owner via a vetted network with a real engagement model; collaboration management via a platform if NP-heavy; banking built multi-entity from day one — per-entity accounts, an intercompany workflow with invoice-and-approve mechanics, and payer EFT enrollment managed per entity (purpose-built healthcare banking infrastructure like Lemma exists because generic business banking handles none of this); books with a healthcare-literate fractional controller and per-entity ledgers; counsel on speed-dial rather than retainer until the Series A. Total run-rate: low five figures monthly — the cheapest insurance in your budget relative to what it protects.

Triangulate three source types: law firm literature (the healthcare regulatory groups at national firms publish rigorous, current analysis of the state-law wave — read the primary alerts, not summaries of summaries); the operator-facing ecosystems (formation and compliance platforms publish practical guides reflecting live deal patterns); and primary sources when stakes are high (the statutes and board guidance are shorter and clearer than their reputation). Then buy judgment where it matters: an hour of specialized healthcare counsel on your specific fact pattern outperforms any amount of general reading — including this handbook, which is a map, not the territory.