When “quality assurance” starts looking a lot like workforce control & The tale of ApolloMD

This is Part 3 in our 'Who Is Actually Working for Who' Series: PART 1 and PART 2

Modern behavioral healthcare has quietly created one of the strangest labor structures in medicine. Many companies now rely almost entirely on large networks of “independent contractors” to deliver the actual healthcare services being sold, while simultaneously maintaining increasingly centralized operational systems governing how that care is delivered.

On paper, clinicians are told they are independent business owners. In practice, however, many providers are starting to question how much independence they truly retain once they enter these ecosystems.

The confusion is understandable. Many clinicians initially join these national behavioral health conglomerates believing they are simply outsourcing administrative burdens like billing, credentialing, scheduling, or insurance contracting. Instead, some eventually find themselves operating inside highly structured systems involving standardized documentation requirements, chart audits, QA scoring, prescribing oversight, workflow mandates, utilization monitoring, response-time expectations, and centralized operational infrastructure. At some point, the distinction between “independent contractor” and “employee without benefits” starts becoming difficult to meaningfully separate.

The deeper issue is structural. Many behavioral health companies market themselves like technology platforms or administrative support organizations, but their actual revenue depends on clinicians delivering healthcare services. The product is not the software itself. The product is psychiatric evaluation, therapy, diagnosis, prescribing, and clinical treatment. That raises an uncomfortable but important question: if clinicians are generating the company’s primary revenue stream while operating inside company-controlled infrastructure, how independent are they really?

Traditionally, independent contractor relationships involved one independent business providing services to another independent business while maintaining meaningful operational separation, mean that for the most part an independent contractor is generally not required to follow the other companies policy and procedures, even if on surface it seems the same.

For example, an outside billing company may absolutely comply with HIPAA, CMS regulations, cybersecurity requirements, payer rules, and healthcare privacy laws. But the billing company follows those rules because the billing company operates as its own independent business entity with its own legal obligations, policies, workflows, staffing structure, and operational systems. The medical practice is not directing how the billing company internally functions day to day even if both companies have similar internal policies and procedures.

Those dynamic feels fundamentally different from clinicians functioning inside another organization’s centralized operational hierarchy.

This is where many providers begin struggling with the “we’re just a platform” narrative.

Companies may market themselves as helping independent clinicians with billing and credentialing, yet providers simultaneously encounter chart scoring systems, prescribing restrictions, operational audits, workflow mandates, patient continuity limitations, centralized scheduling systems, and company medical directors overseeing certain prescribing decisions.

At some point, providers reasonably begin wondering whether these organizations are functioning less like neutral administrative platforms and more like centralized healthcare operations.

The NPI issue further complicates the conversation. If an organization bills under a group NPI, manages centralized payer contracts, controls reimbursement systems, and oversees clinical infrastructure, the operational reality starts looking much closer to a healthcare organization than a simple marketing or billing service. That does not automatically mean anything improper is occurring, but it does raise legitimate questions about where the line exists between a platform company, a group practice, an management services organization, and the corporate practice of medicine.

The “Quality Assurance” Question Nobody Wants to Touch

Healthcare organizations absolutely need quality assurance systems. Nobody serious is arguing otherwise. Legitimate healthcare organizations should have chart review, compliance oversight, peer review, documentation monitoring, prescribing safeguards, and patient safety systems. The problem is not that quality assurance exists. The problem is that “quality assurance” increasingly appears to function as a catch-all phrase covering operational structures that, in some cases, begin looking remarkably similar to workforce management.

If You’re “Just a Platform,” Why Are You Running Clinical Operations?

The IRS evaluates worker classification based in part on behavioral control, financial control, and the overall nature of the working relationship.

IRS Independent Contractor Guidance: https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-defined

IRS Behavioral Control Guidance: https://www.irs.gov/businesses/small-businesses-self-employed/behavioral-control

As organizations implement required templates, dictate documentation structures, audit charts, score clinicians internally, monitor productivity, control scheduling systems, track response times, restrict patient continuity (you can't take your patients with you if you leave), require approval from company-employed medical directors for certain prescribing decisions, prohibit specific medications, and mandate operational meetings, providers are increasingly asking a reasonable question:

At what point does quality assurance and oversight become workforce control?

That question becomes especially uncomfortable when organizations begin exerting influence over prescribing behavior itself. Again, healthcare organizations absolutely need compliance oversight regarding controlled substances. Nobody is arguing otherwise.

But when a company tracks prescribing patterns (requiring you to identify if you prescribed a controlled substance on a billing claim form), prohibits certain medications (does not allow the provider to prescribe controlled substances for ADHD, or SUD), requires approval from company medical directors (controlled substances, esketamine, TMS or other services), establishes prescribing policies, and centrally oversees workflows while simultaneously describing clinicians as fully independent businesses operating autonomous private practices, providers naturally begin questioning what role the organization is actually playing.

At that point, the operational structure starts sounding much less like administrative support and much more like centralized clinical oversight.

The MSO Question

This is where the Management Services Organization (MSO) conversation becomes important. Traditionally, Management Services Organizations were designed to provide administrative and operational support without directly practicing medicine.

Legitimate MSOs may assist with billing, credentialing, scheduling, HR support, marketing, technology infrastructure, and operational coordination while leaving patient care, diagnoses, prescribing, treatment planning, and clinical judgment under the control of licensed clinicians and independently owned practices.

That distinction matters because many states maintain some form of Corporate Practice of Medicine doctrine restricting non-clinicians from controlling medical decision-making. The problem is that modern healthcare infrastructure has evolved into something far more complicated than traditional MSO models.

Increasingly, some organizations appear to operate in a gray zone where they avoid formally employing clinicians or openly identifying as medical groups while simultaneously exercising substantial operational influence over healthcare delivery itself.

If a company controls the contracts, reimbursement systems, workflows, scheduling infrastructure, patient acquisition pipeline, QA systems, and operational expectations while clinicians remain financially dependent on that infrastructure, the distinction between “supporting healthcare” and “operating healthcare” becomes increasingly difficult to meaningfully separate.

The ApolloMD Case: Why Healthcare Lawyers Started Paying Attention

For many clinicians reading conversations about Corporate Practice of Medicine (CPOM), MSOs, and “management control,” the ApolloMD litigation may sound obscure or overly technical.

But the case became important because it touched a much bigger question that has been quietly developing across modern healthcare:

At what point does a management company stop merely supporting healthcare operations and start effectively controlling them?

ApolloMD is a large healthcare management organization that has historically worked with emergency medicine groups and hospitals across multiple states. Like many modern healthcare organizations, the structure involved layers of management entities, physician entities, staffing relationships, and operational agreements designed to separate administrative functions from direct clinical ownership.

The controversy arose in Oregon, where allegations were raised involving Corporate Practice of Medicine concerns and whether non-physician-controlled entities were exercising too much practical control over medical operations.

ApolloMD Oregon Litigation: https://law.justia.com/cases/oregon/court-of-appeals/2024/a178856.html

Now, it is important to understand what the case was not.

The lawsuit was not simply:

“A company used an MSO.”

That alone would not be remarkable. MSOs are extremely common throughout healthcare and often serve legitimate operational purposes.

The deeper issue involved allegations that the management structure may have crossed the line from:

administrative support --->into ---> operational control over medical practice activities.

That distinction is the entire heart of Corporate Practice of Medicine law.

Historically, CPOM doctrines were created to prevent non-clinicians—or corporations primarily driven by financial interests—from exerting excessive control over medical judgment. Different states apply these rules differently, and enforcement varies significantly, but the underlying concern has remained relatively consistent for decades:

Healthcare decisions should ultimately remain under the control of licensed clinicians, not purely financial or corporate entities.

What makes ApolloMD especially relevant today is that the allegations reflected many of the same structural questions now emerging throughout behavioral healthcare and telehealth infrastructure models.

For example:

• Who actually controls the practice operations?

• Who controls staffing decisions?

• Who controls reimbursement systems?

• Who controls workflows?

• Who controls scheduling expectations?

• Who controls the operational infrastructure clinicians depend on?

• And perhaps most importantly: who has practical leverage over the clinicians delivering care?

Modern healthcare organizations have become extraordinarily sophisticated in how they structure these relationships. Many companies now build layered arrangements involving:

• management companies,

• staffing entities,

• contractor agreements,

• administrative organizations,

• physician ownership structures,

• technology platforms,

• and operational service agreements

all carefully designed to preserve legal separation between administrative and clinical functions.

Critics of some modern healthcare structures argue that while the paperwork may preserve formal legal separation, the operational reality underneath may still reflect substantial centralized corporate control.

To be clear, the existence of these structures does not automatically mean an organization is acting illegally. Many large healthcare organizations operate complex MSO arrangements completely lawfully.

But ApolloMD became important because it signaled that regulators, courts, and healthcare attorneys are increasingly paying attention not only to:

“What does the contract technically say?”

but also:

“How does the organization actually function operationally in the real world?”

And honestly, that distinction matters enormously in modern behavioral healthcare.

Because many clinicians assume the phrase:

“You are an independent contractor”

automatically means:

“You are operating an independent business.”

But ApolloMD helped highlight a broader reality: operational control, financial dependence, infrastructure ownership, workforce oversight, and practical leverage may matter just as much as whatever label appears on the contract itself.

That is why the case resonates far beyond emergency medicine.

It touches a growing healthcare-wide tension between:

• administrative support

  and

• operational control,

  between

• contractor flexibility

  and

• workforce management,

  and between

• supporting healthcare practices

  and

• effectively running them.

  
  

And as behavioral healthcare continues consolidating into increasingly centralized, venture-backed, payer-connected operational systems, those questions are likely only going to become more important. The ApolloMD litigation in Oregon brought national attention to many of these broader structural questions involving management organizations and physician control.

The larger issue raised in cases like ApolloMD is not simply whether a specific statute was technically violated its the arguement that some organizations may effectively control large portions of healthcare operations while preserving enough legal separation to maintain plausible deniability.

To be clear, this does not mean every MSO model or contractor arrangement is improper.

Legitimate MSOs absolutely exist and provide real operational value. Many clinicians also genuinely prefer structured contractor arrangements and centralized administrative support.

The problem is not necessarily the existence of these models.

The problem is that many clinicians do not fully understand the structures they are entering because healthcare education rarely teaches providers how healthcare business systems actually work.

Most graduate programs never teach clinicians:

• business ownership,

• employment classification,

• MSO structures,

• reimbursement infrastructure,

• payer relationships,

• operational control,

• or the difference between owning a business versus functioning inside someone else’s infrastructure.

That educational gap leaves many providers vulnerable—not necessarily to malicious companies, but to entering operational arrangements they may not fully understand until years later.

Some clinicians may ultimately decide they are perfectly comfortable functioning inside larger healthcare ecosystems. Others, particularly those frustrated by feeling like they are “working for someone else” despite contractor language, may eventually decide they want true private practice ownership, direct payer relationships, operational autonomy, or genuinely independent infrastructure.

Neither path is inherently wrong.

But providers deserve to understand the difference.

There is a very important distinction between providing an independent service that helps a company operate (like a billing company) and being the actual service the company sells (diagnosing, prescribing, treatment plan creation, direct patient care, etc).

A billing company helps a healthcare organization operate. An accountant helps a healthcare organization operate. An IT vendor helps a healthcare organization operate.

But if the organization’s actual revenue-generating product is psychiatric evaluation, therapy, diagnosis, prescribing, and clinical treatment—and clinicians are performing all of those services inside company-controlled infrastructure—then providers should stop and ask themselves a very honest question:

Am I providing an independent service TO this company—or Am I the service the company is selling?

That is not cynicism.

That is business literacy.

And increasingly, clinicians may need both clinical training and business literacy to survive modern healthcare.

This article is intended for educational and informational purposes only and does not constitute legal, tax, employment, reimbursement, regulatory, financial, or compliance advice. The information presented reflects general industry commentary, analysis, opinion, and discussion regarding evolving healthcare business models, operational structures, reimbursement systems, workforce classification issues, and healthcare infrastructure trends. The organizations, platforms, and companies referenced in this article are discussed solely as examples within broader industry conversations and should not be interpreted as allegations of wrongdoing, illegal conduct, fraud, regulatory violations, or improper business practices. References to specific companies, policies, organizational structures, litigation, or publicly available reports are included for commentary, educational discussion, and analytical purposes only. This content is provided in good faith based on publicly available information at the time of publication. While reasonable efforts have been made to present accurate and current information, no guarantees, representations, or warranties are made regarding completeness, accuracy, interpretation, future regulatory outcomes, or legal applicability. Readers should independently verify all information and consult qualified legal, financial, tax, employment, and healthcare regulatory professionals before relying upon any information contained herein.The author and publisher disclaim liability for decisions, actions, or outcomes arising from the use or interpretation of this content. Nothing in this article should be interpreted as creating an attorney-client, employment, consulting, fiduciary, or professional advisory relationship.