Value-Based Care

MSO in healthcare: the management services organization

~8 min readBy Pelica Health teamPublished August 28, 2026Updated August 28, 2026Reviewed by Catherine Zhao

Short answer

An MSO, or management services organization, is a company that runs the non-clinical side of a medical practice: billing and collections, payer contracting support, credentialing, HR, IT, compliance, and reporting. The physicians keep the clinical entity and every clinical decision. A management services agreement joins the two and pays the MSO a fee. The structure exists mostly because most states bar corporations from practicing medicine, so health systems, IPAs, and investors build around the professional entity instead of buying it.

What an MSO does

An MSO runs the parts of a medical practice that do not require a license. The clinical entity keeps the patients, the records, the license, and every clinical decision. The MSO takes the rest and charges a fee for it.

The usual scope:

Revenue cycle. Billing, collections, denials, coding support, and payer follow-up.
Payer contracting and credentialing. Negotiating support, enrollment, primary source verification, and re-credentialing calendars.
Back office. HR and payroll, purchasing, real estate and equipment, accounting, and finance.
Technology. EHR administration, interfaces, security, help desk.
Compliance and reporting. The compliance program, policies, audit response, and quality and risk adjustment reporting.

What it does not do is decide care. In most states it also cannot employ the physicians or own the professional entity, which is why the structure below exists.

Non-clinical

The boundary that defines an MSO's scope in every state with a corporate practice of medicine doctrine.

The MSA

The management services agreement is the whole relationship: scope, term, fee, and who gets to decide what.

Jan 1, 2029

Deadline for MSOs formed before June 9, 2025 to comply with Oregon SB 951, the strictest state limit yet on MSO control of a medical practice.

The friendly PC model, and why it exists

Most states prohibit a business corporation from practicing medicine or employing physicians to deliver care. The doctrine is called the corporate practice of medicine, and it is the single biggest reason healthcare deal structures look strange to people from other industries.

The workaround has a standard shape. The clinical entity is a professional corporation whose shares are held by a licensed physician. The MSO, which can be owned by anyone, signs a long-term management services agreement with that PC and usually a stock transfer restriction agreement governing who may hold the shares if the physician-owner leaves or dies. Practitioners call it the friendly PC model because the physician shareholder is chosen by, and aligned with, the MSO.

Two things keep the structure from being a formality.

The first is the HHS Office of Inspector General's contractual joint venture doctrine. Its 2003 Special Advisory Bulletin took the position that an arrangement can violate the anti-kickback statute even when every individual lease, service, and management agreement inside it fits a safe harbor. Structure alone is not a defense.

The second is that states are tightening the rules. Oregon SB 951, signed June 9, 2025, bars the same people from holding an ownership interest in the MSO and controlling the professional entity, restricts MSO control over clinical and business decisions of the practice, and voids certain non-compete and non-disparagement clauses between licensees and MSOs. MSOs formed on or after June 9, 2025 were covered from January 1, 2026. Those formed earlier have until January 1, 2029. Other states are working from the same template.

MSO vs IPA vs medical group

The shorthand people use in meetings blurs these together. On paper they answer different questions: who sells administration, who holds the payer contract, and who owns the practice.

	MSO	IPA	Medical group
What it holds or sells	Administrative services under a management agreement	Payer contracts on behalf of independently owned practices	The practice itself
Party to the health plan contract	No	Yes	Yes
Takes medical cost risk	No, it earns a fee	Often, through capitation or shared savings	Often
Who can own it	Physicians, a health system, an IPA, or outside investors	Its physician members, usually	Its physicians
The physician's relationship to it	Customer	Member	Owner or employee
Main legal constraint	Corporate practice of medicine and fee-splitting law	Antitrust and payer delegation rules	Professional licensure and group governance

The comparison people actually want is MSO vs IPA, and the one-line answer is that an IPA signs the payer contract and an MSO does not. An IPA can hire an MSO, own one, or be one organization with two legal entities. The distinction still matters, because only the IPA carries the delegation obligations.

Why plans and IPAs work with MSOs

An IPA is a contract and a governance structure. Someone still has to do the work. In most markets that someone is the MSO: it runs the claims system, staffs the utilization review nurses, keeps the credentialing files, and produces the quality and risk adjustment reporting the IPA's delegation agreement obligates it to produce.

That is why a health plan's delegation audit usually lands on an MSO's desk even though the plan's contract is with the IPA. It does not move accountability. Under 42 CFR 422.504(i), the Medicare Advantage organization remains responsible to CMS for delegated activities no matter how many entities sit below it, and its contracts have to specify the delegated activities and allow revocation for poor performance.

Health systems use MSOs for a different reason: to affiliate with independent practices without buying them, keeping referral relationships and shared infrastructure without the acquisition. Investors use them because the MSO is the piece of a physician enterprise a non-physician is allowed to own, which is why nearly every private equity investment in physician services runs through one.

Where MSO arrangements go wrong

Fee structures that trip state law. A percentage-of-collections management fee is ordinary in some states and an illegal fee split in others. The fee also has to survive fair market value and commercial reasonableness scrutiny when referrals move between related entities.

Letting the MSA drift into clinical territory. Visit-length standards, staffing ratios, coding targets, and hiring vetoes over clinicians are the exact provisions Oregon's SB 951 went after. An agreement written in 2019 may not survive a 2029 review.

Assuming delegation moves accountability. It does not, and the plan will document that in the audit finding.

Naming the wrong entity. Payer contracts signed by the MSO instead of the IPA, or delegation exhibits that describe functions the MSO performs but obligate the IPA, cause avoidable disputes when performance slips.

Running the practice through six payer portals. This is the operational failure mode, not the legal one. An MSO manages practices it does not own, across payers it does not control, and its staff spend the day logging into one portal per plan. We wrote about what that portal sprawl actually costs.

How Pelica fits into an MSO stack

An MSO's problem is coverage: it is accountable for outcomes across practices it does not own, using data that arrives late and in pieces. Pelica pulls claims, EHR, pharmacy, lab, and ADT feeds into one member record and puts an AI copilot on each function, so quality, pharmacy, risk, care management, and network teams are working the same list instead of five exports.

At HealthCare Partners, an IPA of roughly 1,000 providers and 200,000 lives, weekly assignment prep went from 8 hours to 15 minutes, quality gap closure improved 41%, adoption was 100%, and the teams were live in two weeks.

Related terms

An IPA is the contracting entity an MSO usually serves. A CIN is the clinical integration program that lets independent providers negotiate jointly without financial risk sharing. An ACO is defined by the payer program it joins. Capitation is the payment form that puts risk on the IPA rather than the MSO, and value-based care is why the whole stack keeps getting rebuilt.

Sources

Frequently asked questions

Common questions about what an MSO does, how the friendly PC structure works, and how an MSO differs from an IPA.

What is an MSO in healthcare?

An MSO, or management services organization, is a company that provides the non-clinical services a medical practice needs: billing and collections, payer contracting support, credentialing, HR, IT, compliance, and reporting. The physicians keep the clinical entity and all clinical decisions. A management services agreement sets the scope, the term, and the fee.

What is the difference between an MSO and an IPA?

The IPA signs the payer contract; the MSO does not. An IPA is a contracting entity made up of independently owned practices and it often takes capitation or shared savings risk. An MSO sells administration for a fee and takes no medical cost risk. Many organizations run both, with the MSO performing the work the IPA's delegation agreement obligates it to perform.

What is the friendly PC model?

It is the standard structure used in states that bar corporations from practicing medicine. A professional corporation owned by a licensed physician holds the clinical business, and an MSO that anyone can own signs a long-term management services agreement with it, usually alongside a stock transfer restriction agreement controlling who may hold the PC's shares. It is called friendly because the physician shareholder is selected by and aligned with the MSO.

Can an MSO own a medical practice?

In most states, no. The corporate practice of medicine doctrine bars a business corporation from practicing medicine or employing physicians to deliver care, so the MSO contracts with the professional entity instead of owning it. States vary widely, and Oregon SB 951 has gone further than any other, prohibiting overlapping ownership and control between an MSO and the practice it manages.

Why do private equity firms and health systems use MSOs?

Because the MSO is the part of a physician enterprise a non-physician is permitted to own. Investors buy the management company and contract with the professional entity. Health systems use the same structure for a different purpose: to affiliate with independent practices, share infrastructure, and keep referral relationships without acquiring the practices outright.

Does hiring an MSO change who a health plan holds accountable?

No. Under 42 CFR 422.504(i) a Medicare Advantage organization stays accountable to CMS for any activity it delegates, and its contracts have to specify the delegated activities and reporting duties and allow revocation for poor performance. In practice the plan's delegation audit may be answered by MSO staff, but the finding still lands on the plan and the delegated entity that signed the contract.

What services does an MSO not provide?

Anything clinical. An MSO does not select treatment, supervise care, or hold the professional liability for it, and in most states it cannot employ the treating physicians. Agreements that reach into visit length, staffing ratios, coding targets, or clinician hiring are the ones state regulators have started to challenge.

An MSO is accountable for outcomes in practices it does not own.

Pelica gives every function one member record and an AI copilot that works the queue instead of reporting on it. At HealthCare Partners, weekly assignment prep went from 8 hours to 15 minutes, quality gap closure improved 41%, and the teams were live in two weeks.

Book a Demo → See the Provider Network copilot