Building controls into physician services agreement management

For compliance officers and physician contracting leads, these are high-volume agreements whose defensibility rests on records that were never stored with the contract.

What makes physician services agreements hard to keep compliant?

Volume and dependency. A mid-sized health system can hold thousands of arrangements across medical directorships, call coverage, professional services and teaching, each one small and each one governed by the same expectations. Compliance then rests on documents that usually sit outside the agreement, the fair market value opinion and its date, the signed counterpart, the timesheet or service log, and the total paid to that physician across every other arrangement in force at the same time.

Last updated: September 9, 2026 · Reviewed by the Aavenir Healthcare practice

Key takeaways

  • ✓Physician arrangements are judged on evidence that lives outside the contract, the valuation opinion, the signature page and the service log
  • ✓A written, signed agreement covering identified services for a stated term with compensation set in advance is the common structural expectation
  • ✓Fair market value and commercial reasonableness are distinct tests, and an arrangement can satisfy one while failing the other
  • ✓Aggregate compensation across every arrangement with one physician is the view most systems cannot produce on demand

Physician arrangements are the highest-volume regulated contracts a health system signs. Medical directorships, call coverage, professional services, teaching and supervision, telehealth, space and equipment leases. Individually each is a modest agreement handled under time pressure. Collectively they are the part of the portfolio that receives the most external scrutiny.

What makes them difficult is not the drafting. The template is usually settled. The difficulty is that whether an arrangement holds up depends on records that were never stored with the contract, the valuation opinion supporting the rate, the countersigned page, the monthly service log, and the total compensation flowing to that physician across every other arrangement in force.

This guide sets out the structure that keeps those records connected to the agreement. It describes general requirements rather than legal conclusions, because how any exception or safe harbor applies is a judgment for counsel. It is written for compliance officers and contracting leads who need the operating controls.

What the two regimes generally expect of an arrangement

Two federal regimes shape these contracts. The physician self-referral law, commonly called the Stark Law, and the federal Anti-Kickback Statute. They work differently, but many Stark exceptions and many Anti-Kickback safe harbors share a recognizable set of structural expectations for a compensation arrangement. Which expectations apply, and how strictly, depends on the exception or safe harbor being relied on.

  • Set out in writing and signed, by the parties, which sounds trivial and is the control that fails most often, because a fully executed counterpart is often missing from the system of record months after work began.
  • Covering identified items or services, so the agreement describes what the physician is actually doing, in enough detail that a reviewer coming to the file later recognizes the services.
  • For a defined term, with a stated duration, which is where automatic renewal and long-dormant evergreen arrangements deserve attention, since what is in force may no longer match what was reviewed.
  • Compensation set in advance, meaning the methodology is fixed before services are provided rather than reconstructed afterward, and the record should carry that methodology, not only the resulting rate.
  • Consistent with fair market value, and not determined in a manner that takes into account the volume or value of referrals, which is the substantive test that the surrounding documentation exists to support.

Each of those is a field or an artifact, not a paragraph. A team can satisfy every one at signature and still be unable to demonstrate it two years later, because the valuation opinion sat in a shared drive, the countersigned page arrived by email, and service logs were filed by the receiving department. The agreement is intact, the evidence is scattered.

Fair market value is not commercial reasonableness

These are distinct requirements and an arrangement can meet one while failing the other. Fair market value asks whether the rate suits the services. Commercial reasonableness asks whether the arrangement makes sense for the organization at all, given its purpose. A record holding only a rate cannot answer the second question.

Where physician arrangement records break down

The failures are consistent across organizations and none are dramatic. They are administrative gaps that survive because nobody owns the closing step, and they surface during an internal review or a due diligence exercise rather than when they occur. Five account for most of what a compliance team finds.

  • Signature pages never make it back. Work starts on a countersigned copy that exists somewhere. Detecting the gap needs a system that knows how many signatures an agreement should carry and flags a shortfall on a date, rather than a person noticing during a file review.
  • Valuation opinions expire without notice. A valuation opinion supports a rate as of a date and against a described scope, so it has a useful life. When neither the opinion reference nor its expiry sits on the contract record, the rate quietly outlives its support.
  • Evergreen renewal outlasts the original basis. An arrangement that renews automatically can run for years past the review that justified it. Duties change, hours change, the market moves, and none of it reaches anyone because renewal is silent by design.
  • Service logs are agreed and never collected. Directorships commonly require a timesheet or activity attestation as a condition of payment. In practice logs arrive late, arrive incomplete, or stop, while payment continues on schedule because the two processes are unconnected.
  • Aggregate compensation stays invisible. One physician may hold a directorship, a call coverage arrangement and a teaching stipend, each reviewed by a different owner. The total is the number that matters, and few systems can produce it without a manual exercise.

A five-step path to a defensible physician contract record

Step 1, Inventory Arrangements By Physician

Build the inventory around the physician rather than the document. For each individual, list every arrangement in force, its type, owner, term and compensation basis. Most systems find arrangements nobody owns, duplicates created when a department re-papered a renewal, and agreements running past their intended end.

Step 2, Agree The Record Fields First

Decide what the arrangement record holds before populating it. A working set is arrangement type, services described, term and renewal status, compensation methodology, rate, valuation reference and date, signature status, required attestations and owner. Keep it narrow enough that contracting maintains it during normal intake.

Step 3, Close Signature And Term Gaps

Run the portfolio against two mechanical tests. Does every arrangement carry a complete set of signatures, and does every term remain unexpired. These are the questions a reviewer asks first and the ones a system can answer without judgment, which makes them the right place to start. Detail sits in the audit checklist for these regimes.

Step 4, Track Attestations As Obligations

Timesheets, activity logs and service attestations are dated commitments with a named owner. Convert each into a scheduled obligation with an expected artifact and a due date, so a missing log raises an exception before the next payment rather than during a review, the model described in obligation management for healthcare.

Step 5, Run A Recertification Cycle

Set a periodic review in which the owner reconfirms that services are still provided as described, hours remain broadly as expected, valuation support is current and the arrangement is still needed. Recertification stops an evergreen agreement drifting from what was reviewed and approved.

See a physician arrangement record built from your agreements

Walk through valuation references, signature detection, service log obligations and physician-level compensation views using a sample of your executed arrangements.

Book a demo

The physician-level view and why it is hard to build

Individual arrangements are reviewed individually, which is reasonable, and it is also how aggregate exposure goes unnoticed. A physician holding a directorship in one service line, a call coverage arrangement negotiated by another and a teaching stipend administered by a third has three owners, three approval trails and no combined total. Building that view is a data problem more than an analytical one. It needs a stable physician identifier applied across every arrangement record, so agreements written at different times by different teams resolve to the same person. Once it exists, aggregate compensation, overlapping commitments and total contracted hours become queries. Without it, the answer is assembled by hand, which means rarely.

The physician arrangement record, field by field

The table sets out the fields that carry the most weight in a review, where each comes from, and the condition that should raise an alert. Systems applying the same structure to their payer side will recognize the approach from work on payer-provider contract automation, where terms and renewal dates face the same problem of living in prose.

Record fieldSourceWhy it carries weightAlert condition
Signature statusExecuted counterpartsWritten and signed is a common expectationRequired signature missing at start date
Term and renewal statusTerm and renewal clausesEvergreen arrangements drift from reviewTerm passed or auto-renewed unreviewed
Compensation methodologyCompensation exhibitSet in advance rather than reconstructedRate changed without a methodology update
Valuation opinion and dateValuation file referenceSupports the rate as of a dateOpinion expiring within ninety days
Required attestationsService and reporting clausesPayment often depends on the logLog missing for a payment period

These arrangements are written to make a clinical relationship clear and a compensation basis defensible. They do that only while the evidence behind them stays connected to the agreement. Systems that hold valuation references, signature status, term posture, attestations and physician-level totals as structured fields answer a compliance question in an afternoon. Everyone else answers it during an audit or a transaction, reconstructing from shared drives and email under a deadline set by someone else.

For related guidance, see Physician agreements, compliance pressure points, Provider contract management for health systems and GPO and medical device contract control for health systems.

FAQ

Physician agreement questions, answered

Is this guide legal advice on Stark Law or the Anti-Kickback Statute? +
No. It is general information about contract operations for compliance and contracting teams, and it describes structural requirements in general terms rather than asserting how any exception or safe harbor applies. Application depends on the specific arrangement and the facts around it. Physician compensation arrangements should be reviewed by qualified healthcare counsel.
What structural elements do these arrangements commonly need? +
Many exceptions and safe harbors expect an arrangement to be set out in writing and signed, to cover identified items or services, to run for a defined term, and to set compensation in advance in a way that is consistent with fair market value and not determined by the volume or value of referrals. Which apply depends on the provision relied on.
How is commercial reasonableness different from fair market value? +
They are separate tests. Fair market value asks whether the compensation is appropriate for the services being provided. Commercial reasonableness asks whether the arrangement makes sense for the organization given its purpose, independent of the rate. An arrangement can be priced defensibly and still raise a commercial reasonableness question, so both belong in the record.
Why does the fair market value opinion need an expiry date on the record? +
An opinion supports a rate as of a date and against a described scope of services. As duties, hours or market conditions change, the support ages. Carrying the opinion reference and its expiry on the contract record turns an aging valuation into a dated alert with an owner, rather than something discovered during a review years later.
How should timesheets and service logs be handled? +
Treat them as tracked obligations rather than paperwork. Each log needs a cadence, a responsible owner, an expected format and a due date, so a missing submission raises an exception before the next payment cycle. Where payment is conditioned on the attestation, connecting the two processes is the control that makes the condition real.
Why does aggregate compensation per physician matter? +
Because a single physician often holds several arrangements owned by different service lines, each reviewed on its own. The combined total, the overlapping service commitments and the total contracted hours are what a reviewer will ask about. Producing that view requires a consistent physician identifier applied across every arrangement record.

Make your physician arrangements provable

See how a CLM platform builds a structured arrangement record from executed agreements, detects missing signatures and passed terms, alerts before a valuation opinion ages out, and tracks service log attestations with named owners.

  • ✓Missing signatures and passed terms detected automatically
  • ✓Valuation dates and service logs tracked with owners
  • ✓Standalone or native on ServiceNow