In the vast majority of the fifty states, corporate practice of medicine doctrine — in one form or another — prevents non-physician corporations from directly employing physicians or owning medical practices. The whole edifice of MSO-PC structuring that occupies so much of healthcare compliance work exists because of this doctrine and the need to navigate around it. Missouri, in a development that dates back more than a century, decided differently. The state has no corporate practice of medicine doctrine, and Missouri courts have consistently upheld that position ever since.

For digital health founders, this raises an obvious question: does that mean we can skip the MSO-PC structure in Missouri? The answer is more complicated than a simple yes or no — and understanding why requires grasping both what Missouri's no-CPOM position actually means and what it does not protect you from. This guide covers the history and current state of Missouri law, the practical implications for digital health companies, and the compliance requirements that apply in Missouri regardless of the CPOM question.

The 1907 Ruling That Changed Missouri Healthcare Law

Missouri's departure from the CPOM doctrine traces to a landmark 1907 court ruling in which the Missouri Supreme Court allowed a hospital corporation — an entity that could not hold a medical license — to employ physicians and operate a medical practice. The court's reasoning centered on the legitimate business purpose of hospital care delivery: hospitals could not function if they were prohibited from employing the physicians necessary to provide care. The administrative and financial management of medicine could be separated from the professional practice of medicine, and the former could properly reside with a corporate entity.

This ruling was not a fluke or an anomaly that was later narrowed. Missouri courts revisited the issue in subsequent decades and consistently reaffirmed the principle. The state never enacted legislation to override the court's holding and never developed the Attorney General opinion tradition that other states used to build CPOM restrictions as a matter of executive branch policy. The result is that Missouri today stands alongside a small handful of states — Indiana is another commonly cited example — that affirmatively permit corporate employment of physicians and corporate ownership of medical practices.

This is genuinely unusual. It means that in Missouri, a Delaware C-corporation with no physicians on its board can, as a matter of state corporate law, directly employ licensed Missouri physicians, operate a medical practice under the corporate name, set clinical protocols, and derive revenue directly from professional medical services — without the layered MSO-PC structure that every other major healthcare market requires.

What Missouri's No-CPOM Position Actually Permits

The practical permissions that flow from Missouri's no-CPOM position include:

This structural flexibility can meaningfully simplify a Missouri-specific operation. A startup that wants to launch in Missouri without the overhead of establishing a separate professional entity, finding a physician-owner willing to hold PC equity, and executing a full suite of MSO-PC governance documents can, in Missouri alone, build a simpler structure.

Missouri's absence of CPOM removes the structural constraint — but it doesn't remove the compliance obligations. Federal law, professional licensing, and the requirements of every other state you operate in all still apply. Know what Missouri gives you, and know what it doesn't.

Why Most Multi-State Companies Still Use MSO-PC Structures in Missouri

Despite Missouri's permissive posture, most serious digital health companies operating in Missouri use an MSO-PC structure anyway. There are several strong practical reasons for this:

Multi-State Operations Require Multi-State Compliance

A digital health platform that serves patients in Missouri, California, Texas, and New York needs a compliant structure for every state. California and Texas require robust MSO-PC governance regardless of what Missouri permits. Companies typically choose to operate under a single unified structure across all states — the MSO-PC structure — rather than maintain different structural frameworks in different states. The overhead of managing a Missouri-specific "simplified" structure alongside a California-compliant MSO-PC structure almost always exceeds the benefit of the simplification.

Investor Expectations

Venture investors in digital health have become sophisticated about CPOM compliance. They expect to see an MSO-PC structure in any company that provides clinical services, because that structure is the due diligence standard across the industry. A company that says "we don't have an MSO-PC because we're Missouri-based" will face questions — and potentially valuation discounts — during financing rounds, even if Missouri law technically permits the simpler structure. Investor confidence tracks the compliance standard, not just the legal minimum.

M&A and Exit Readiness

Acquirers of digital health companies conduct extensive CPOM due diligence. A company that has operated without an MSO-PC structure will need to retrofit one before a major acquisition — a process that takes time, creates potential transition risk, and can complicate deal timelines. Building the structure from the start in Missouri, even when not legally required, puts you in a cleaner position for exit.

Telehealth and Multi-State Patient Populations

If your Missouri-based physicians are treating patients in other states via telehealth, the CPOM law of the patient's state governs — not Missouri's. A Missouri digital health company whose clinical staff treat California patients via telehealth is subject to California CPOM doctrine for those patient relationships, regardless of where the company is incorporated or where the physician is physically located. The MSO-PC structure is necessary for the California patients even if it would not be required for Missouri patients.

What Missouri Law Still Requires

Missouri's no-CPOM position does not create a compliance-free zone. The following requirements apply in Missouri regardless of the CPOM question:

Missouri Physician Licensure

Every physician practicing medicine in Missouri — including via telehealth for Missouri patients — must hold a valid Missouri medical license issued by the Missouri State Board of Registration for the Healing Arts. Licensure requirements, renewal obligations, continuing medical education requirements, and disciplinary processes apply fully regardless of the physician's employer. A non-physician corporation employing physicians does not relieve those physicians of individual professional responsibilities.

Missouri's Medical Practice Act

Missouri Revised Statutes Chapter 334 governs the practice of medicine in Missouri. While it does not contain a CPOM prohibition, it establishes the conditions under which medicine may be practiced and provides the Missouri State Board of Registration for the Healing Arts with disciplinary authority over physician conduct. Physicians employed by non-physician corporations can still be disciplined by the Board for clinical misconduct, regardless of who their employer is.

Federal Anti-Kickback Statute and Stark Law

Missouri's no-CPOM position has no effect on the application of federal healthcare law. The Anti-Kickback Statute (42 U.S.C. § 1320a-7b) prohibits remuneration arrangements designed to induce referrals of federally reimbursable services, regardless of state law. Stark Law (42 U.S.C. § 1395nn) restricts certain financial relationships between physicians and healthcare entities in the context of Medicare and Medicaid billing. Any Missouri healthcare company that bills federal programs must structure its financial arrangements to comply with these federal statutes, independent of Missouri's CPOM posture.

HIPAA and Federal Data Privacy

Missouri healthcare companies, like all healthcare companies, are subject to HIPAA's privacy and security rules, the HITECH Act, and applicable federal telehealth privacy regulations. Missouri's no-CPOM position does not affect these obligations.

FDA Regulation

If your digital health platform includes a regulated medical device or software as a medical device (SaMD) under FDA jurisdiction, Missouri law does not affect FDA regulatory obligations. Digital health companies offering clinical decision support, diagnostic tools, or therapeutic software must comply with FDA clearance, 510(k), or de novo pathways regardless of their state of incorporation or their state's CPOM posture.

Missouri-Specific Behavioral Health and SUD Licensing

Missouri has distinct licensing requirements for behavioral health and substance use disorder service providers through the Missouri Department of Mental Health (DMH). Behavioral health facilities, residential treatment programs, outpatient behavioral health agencies, and SUD treatment providers must obtain DMH licensure in addition to complying with general medical practice rules. A no-CPOM position does not remove these specialty licensing requirements — they exist independently of CPOM doctrine and apply to any entity providing these services in Missouri.

Missouri's Healthcare Market: Kansas City and St. Louis

Missouri's two major healthcare markets are Kansas City and St. Louis, each with distinct characteristics for digital health companies. Kansas City is home to a growing health-tech corridor supported by the Kauffman Foundation's entrepreneurship ecosystem and several large employer groups (including major companies in the insurance, financial services, and manufacturing sectors) that are active purchasers of employer health solutions. The presence of Children's Mercy, Saint Luke's, and other health systems creates clinical partnership opportunities.

St. Louis is anchored by BJC HealthCare and Washington University Medicine (Wash U Medical School), which together constitute one of the most influential academic medical systems in the Midwest. St. Louis has a growing health-tech incubator ecosystem and specific strength in genomics, oncology, and medical research translation — areas that align with several categories of digital health innovation.

The no-CPOM environment makes both cities particularly attractive for companies that want to pilot direct-employment clinical models before rolling them out more broadly — Missouri can serve as a proof-of-concept market for direct-employ structures that might be adapted into MSO-PC wrappers for other states.

Missouri CPOM Compliance Checklist

Even without a CPOM doctrine to comply with, Missouri digital health operations require the following: