Management services organization (MSO)
A management services organization (MSO) is the business entity in the “friendly PC” structure that provides non-clinical services — technology, staffing, billing, marketing — to a physician-owned medical group, allowing a company to build a healthcare business without unlawfully practicing medicine.
- Two entities: business MSO + physician-owned PC
- Connected by a management services agreement at fair market value
- Clinical decisions and medical records belong to the PC
- Several states directly regulate MSO arrangements
How the MSO / friendly-PC model works
Two entities, one program: a professional corporation (PC) owned by one or more licensed physicians employs or contracts the clinicians and owns all clinical decisions; the MSO — typically the startup — owns the brand, product, and operations, and charges the PC a management fee under a management services agreement (MSA). A stock-transfer restriction agreement usually keeps the PC aligned with the business (hence “friendly” PC or “captive” PC).
Done correctly, the structure satisfies corporate-practice-of-medicine laws in strict states while letting the business scale nationally. Done sloppily — fees tied to prescription volume, MSO control of clinical protocols, undocumented FMV — it creates CPOM, fee-splitting, and anti-kickback exposure simultaneously.
What to get right in the MSA
- Management fees at fair market value, never a percentage of clinical revenue in fee-splitting states.
- Clinical protocols, hiring of clinicians, and treatment decisions reserved to the PC.
- Term, termination, and succession provisions that survive a physician-owner change.
- State-by-state review — several states regulate MSO arrangements directly.
Build the structure or rent it?
Standing up your own MSO/PC stack means forming the PC with physician owners, negotiating the MSA and stock-transfer agreements, recruiting and credentialing clinicians state by state, and maintaining all of it as laws shift — commonly months of legal work before the first patient. It buys maximum control, and it is the right call at sufficient scale.
The alternative is infrastructure that already operates the clinical entity, the clinician network, and the compliance perimeter — you integrate an API instead of incorporating a medical group. Many programs start there and revisit the build decision when volume justifies it; the switching cost is real but far smaller than building wrong the first time.
Compliance handled, so you can build
Lithos runs the clinicians, pharmacies, and 50-state rules behind your care program — one API.
Frequently asked questions
Do I need an MSO structure to use a telehealth infrastructure API?
No — platforms like Lithos operate the clinical entity relationship for you, which is precisely the burden the MSO structure otherwise makes you carry yourself. Building your own medical group is when you need one.
Is the friendly-PC model legal?
It is the prevailing, widely accepted structure — but its legality depends on execution: FMV fees, genuine clinical independence, and state-specific terms.
Who owns the patients in an MSO model?
The medical records and care relationship belong to the PC. Data-access and continuity terms for the business live in the MSA and BAA.