Physician Collaboration in California: The Clinical-Governance Layer, Explained
In California, practices built around nurse practitioners, physician assistants, or registered nurses need defined physician relationships — collaborating physicians, medical directors, or supervising physicians — with real duties, real availability, and written agreements. These roles are clinical-governance requirements under California licensing law; they are separate from corporate structure, and no MSO arrangement can substitute for them.
Read this page if you’re a nurse practitioner building a practice and mapping your physician-collaboration requirements; a med spa or IV-hydration founder who’s been told you “need a medical director” and wants to know what that actually means; a physician considering a medical director or collaborating-physician role and weighing what you’d be signing up for; or a clinic or MSO operator responsible for making sure the clinical-governance layer in your structure is real. If your questions are about entity ownership, start with Professional Corporations →; if they’re about the business side, start with MSO Structures →. This page covers the layer that sits inside the clinical entity.
Why California requires a physician in the picture
California licensing law defines what each clinician type may do and under what conditions. Registered nurses and, in many configurations, nurse practitioners perform functions that would otherwise be the practice of medicine only under standardized procedures developed with physician involvement. Physician assistants practice under a written practice agreement with a physician. And certain services and settings call for medical direction — a physician responsible for clinical protocols, quality, and oversight.
The common thread: these are clinical requirements that attach to the care itself. They exist whether the business is a solo NP office, a five-location med spa, or a venture-backed telehealth platform — and they cannot be satisfied by corporate paperwork, an MSO relationship, or a physician’s name on a letterhead. If the required physician relationship isn’t real, everyone in the structure is exposed: the clinician performing the care, the physician lending oversight, and the business built on both.
The roles, distinguished
The page’s signature reference — the roles are chronically confused, including by people currently paying for the wrong one.
| Collaborating Physician | Medical Director | Supervising Physician (PA) | |
|---|---|---|---|
| Who needs one | Nurse practitioners practicing under the standardized-procedure framework | Practices needing defined clinical leadership — med spas, IV lounges, clinics, multi-provider operations | Practices using physician assistants |
| What the role does | Participates in developing standardized procedures; provides consultation and the collaboration the framework requires | Owns clinical protocols, quality oversight, delegation decisions, and treatment standards for the service line | Enters the written practice agreement; provides the oversight it defines |
| Core document | Standardized procedures + collaboration agreement | Medical director agreement with defined duties, time commitment, and availability | Practice agreement (the current California framework for PA oversight — verify current terminology and requirements) |
| What it is NOT | A silent name on file | A title sold by the month with no duties | A formality — the agreement defines real scope and oversight |
| Compensation | Fair market value for actual time and duties | Fair market value for actual time and duties | Fair market value for actual time and duties |
Two clarifications that resolve most confusion:
- “Medical director” is a functional role, not a magic license. Hiring a medical director does not, by itself, satisfy an NP’s collaboration requirement or a PA’s practice-agreement requirement — and vice versa. Many practices need more than one of these relationships; some physicians fill more than one role, with each papered separately.
- The row that repeats is the one that matters. Every role, same rule: fair market value for actual duties. A physician paid handsomely to do nothing is not governance — it’s the signature fact pattern in enforcement actions against this layer.
Standardized procedures: the framework behind NP and RN practice
Standardized procedures are the written policies, developed collaboratively with physician involvement, that authorize registered nurses and (in the collaboration framework) nurse practitioners to perform specific functions that overlap with the practice of medicine — from furnishing medications to performing defined procedures. They must actually exist, actually fit the services performed, and actually be maintained; a med spa whose RNs inject neurotoxins “under” standardized procedures nobody has seen is operating without the authority it thinks it has.
For practice founders, standardized procedures are where clinical governance becomes a concrete document set — and where a review most often finds the gap between what the practice does and what its paperwork authorizes. (Full treatment: Standardized Procedures for Nurse Practitioners — coming soon.)
AB 890 and the changing NP landscape
California’s AB 890 created pathways for qualifying nurse practitioners to practice with expanded autonomy — in defined settings and, with further qualification, in independent practice — reducing or removing the traditional physician-collaboration requirement for those who complete the applicable requirements. Which pathway an NP holds changes the governance design: an NP practicing under the standardized-procedure framework needs the collaboration architecture on this page; an NP with expanded-authority status operates under different rules.
The structural point for founders: confirm the NP’s actual status before designing anything. The right corporate structure, collaboration documents, and even the economics all depend on it — and the pathway requirements and board rules in this area should be verified as current at every build. (Full treatment: AB 890 Nurse Practitioner Pathways — coming soon.)
What makes a collaboration relationship real
California evaluates this layer the way it evaluates everything else in healthcare structures: by substance. A defensible physician relationship — whatever the role — has five properties:
- Defined duties in writing. The agreement says what the physician does: protocol development, chart review, availability, consultation, quality oversight — specifically, not aspirationally.
- Real time and availability. Duties imply hours. An agreement whose duties couldn’t be performed in the time the physician actually gives is self-impeaching.
- Fair market value compensation, priced to the work. Paid per the duties — not per the revenue the physician’s license makes possible, which drifts toward fee-splitting territory.
- Documentation that it happened. Reviewed protocols, consultation logs, meeting records. The relationship should leave footprints.
- Genuine authority. The physician can change a protocol, restrict a service, or stop a practice pattern — and everyone in the building knows it.
The inverse is the fig-leaf: a physician’s name, a monthly payment, no duties, no footprints. Fig-leaf arrangements expose the physician’s license, undermine the clinicians relying on the oversight, and hand regulators the clearest possible evidence that the structure’s clinical governance is nominal.
Recognize a fig-leaf in your own structure? Request a legal review of your collaboration and medical director arrangements.
Where this layer meets the PC-MSO structure.
The collaboration layer lives inside the clinical side of a two-entity structure — and keeping it there is a design rule, not a technicality:
- The professional corporation engages the physician. Collaborating physicians, medical directors, and supervising physicians are clinical roles; their agreements run to the PC, not the MSO.
- An MSO cannot supply clinical governance. A “medical director” hired and directed by the management company inverts the entire structure: the unlicensed entity would be sourcing and controlling the clinical oversight that’s supposed to constrain it.
- Design order matters. Structure the clinical-governance relationships first — the right physician, real duties, defensible compensation — then build the corporate and MSO architecture around them. Founders who do it backwards routinely discover their business model assumed a governance layer California doesn’t allow.
The structural context: MSO vs PC Strategy → · Corporate Practice of Medicine →.
Five collaboration mistakes
- Buying a title instead of a role — a monthly-fee “medical director” with no duties, no availability, and no idea what the practice actually does.
- The wrong relationship for the clinician mix — a medical director on file when what the NPs need is collaboration architecture, or vice versa.
- Standardized procedures that don’t exist or don’t match — services expanded, documents never updated.
- The MSO in the middle — physician oversight sourced, paid, or directed by the management company.
- Compensation priced to revenue — physician pay that tracks what the practice bills rather than what the physician does.
How MedBiz Law helps
We design and document the clinical-governance layer: medical director agreements with real duty architecture, collaboration and practice agreements, standardized-procedure alignment, and fair-market-value compensation structures — and we review existing arrangements before a regulator, payer, or transaction does. Because we also build the PC-MSO structures around this layer, the governance and the corporate architecture get designed to fit each other.
Legal services are provided by Bay Legal, PC, a California law firm.
Physician collaboration FAQ
What is a collaborating physician in California?
Do I need a medical director for my med spa?
What’s the difference between a medical director and a collaborating physician?
How much should a medical director be paid?
Can my MSO hire the medical director?
Can a nurse practitioner practice without a physician in California?
What are standardized procedures?
Make the governance layer real.
The physician relationships in your structure protect every license in the building — including the business built on top of them. Design them right, paper them properly, and review them before someone else does.