The Cadence Question Compliance Officers Don’t Ask
Most compliance programs treat fair market value opinions as annual deliverables. The physician compensation arrangement gets reviewed at execution, an FMV opinion is obtained, and a calendar reminder fires twelve months later to schedule the next opinion. The cycle repeats. This is industry norm and it is operationally defensible — until it isn’t.
The question compliance officers rarely ask is: between annual refreshes, what could happen that would make the current opinion non-defensible? The answer, looking at enforcement cases, is “quite a lot.” A modification to the scope of services. A change in the underlying market data the opinion relied on. A specialty-level shift in compensation benchmarks. A renewal that quietly extended the term beyond what the opinion contemplated. Any of these events can render a fifteen-month-old FMV opinion non-defensible even though the calendar says it’s only three months overdue for refresh.
The Stark Law strict-liability framework doesn’t care about the calendar. It cares about whether the arrangement satisfies the fair-market-value requirement throughout its term. Annual refresh is the floor, not the ceiling.
What “Calendar Cadence” Actually Means Under Stark
The Stark Law statute and regulations do not specify a calendar-based refresh interval. Neither does the Anti-Kickback Statute. The regulatory expectation, articulated in OIG advisory opinions and DOJ enforcement actions, is that compensation remains within fair market value range throughout the term of the arrangement. The institution’s burden is to demonstrate that the FMV grounding has not drifted.
Annual refresh became industry norm because it’s administratively tractable and because most market data sets refresh annually. A new MGMA compensation survey, an updated Sullivan Cotter benchmark, a refreshed wRVU multiplier — these arrive on roughly annual cycles and create natural review points. Compliance teams pegged FMV opinion refresh to the same cycle.
That alignment is reasonable as a default. What makes it insufficient is the assumption that nothing material happens between refresh cycles. In practice, plenty happens. Arrangements get amended. Scope expands. Service lines reorganize. Specialty mix shifts. The market data the original opinion relied on gets revised. Each of these events is a moment when calendar cadence stops protecting defensibility — and where trigger cadence has to take over.
The Trigger Events That Demand Out-Of-Cycle Refresh
A defensible compliance program documents a list of trigger events that demand out-of-cycle FMV review. The list is institution-specific, but the following events appear consistently in enforcement-pattern analysis:
Material modification to scope of services. If the arrangement’s scope expands (additional clinical responsibilities, additional administrative duties, additional coverage obligations), the original FMV opinion was scoped to a different deliverable. A re-validation is generally required before the modified arrangement takes effect.
Change in compensation methodology or structure. If the arrangement converts from straight salary to wRVU-based, or from wRVU-based to a productivity-incentive hybrid, the FMV opinion that supported the original structure does not extend to the new structure. Each structural change resets the analysis.
Material change in the underlying market data. If the FMV opinion relied on a specific survey or benchmark dataset, and that dataset publishes a material revision (corrections, methodology updates, specialty re-classifications), the opinion may need to be re-tested against the corrected data. This is one of the less-visible trigger events because the change happens outside the institution.
Modification to term or renewal structure. If the arrangement is renewed or extended in a way the original opinion didn’t contemplate, the renewal itself is a moment for FMV re-validation. A five-year arrangement extended to ten years on the same terms isn’t automatically still at fair market value — market conditions over the additional five years may have shifted.
Change in the physician’s role or specialty. If the physician transitions to a different specialty, takes on a new administrative role, or shifts the mix of services they provide, the FMV opinion needs to address the new role. This is common in academic medical centers and large health systems where physician roles evolve continuously.
Discovery that the original opinion relied on data later corrected or updated. If the institution later learns that the original FMV opinion contained an error, or relied on a dataset that has been corrected, the opinion needs to be refreshed against accurate data.
Each of these events should be documented at the time it occurs — not at the next calendar refresh. The contemporaneous documentation is what supports the defensibility argument later.
How Enforcement Cases Show Trigger Cadence Failures
The pattern that emerges from enforcement cases is rarely “the institution never obtained an FMV opinion.” The more common pattern is “the institution had an FMV opinion that became stale through events the compliance program didn’t track.”
Tuomey Healthcare’s $72.4M settlement turned in part on FMV documentation issues where opinions existed but did not survive scrutiny when the underlying arrangements’ structure was examined against the documentation provided. The institution had FMV opinions. The question litigated was whether those opinions adequately supported the arrangements as actually structured and operated.
Halifax Health’s medical director arrangements illustrate a parallel pattern. Medical director compensation arrangements were entered into with FMV grounding, but the operational reality (hours actually worked, services actually delivered, value actually received) diverged from the FMV opinion’s assumptions. Calendar cadence alone wouldn’t have caught the drift — trigger cadence might have.
Mercy Health’s self-disclosed Stark violations show the opposite (and instructive) pattern: an institution that proactively identified FMV cadence as the issue, self-reported, and worked with OIG to resolve. The self-disclosure framework values exactly this kind of trigger-event identification — the institution that recognizes a material change and takes action receives meaningfully better treatment than the institution that lets calendar cadence ride.
What Continuous Monitoring Actually Looks Like
Calendar cadence and trigger cadence are both backward-looking in their default implementation. The compliance officer reviews FMV opinions at scheduled intervals or when triggered events surface. Continuous monitoring inverts this — the infrastructure detects potential trigger events in real time and surfaces them to the compliance officer before they become enforcement exposure.
What continuous monitoring requires in practice: every arrangement’s FMV opinion is stored alongside its expiration date, the assumptions it was based on, and the trigger events that would invalidate it. When any of those assumptions change — through arrangement amendment, scope expansion, role change, or external market data revision — the system surfaces the affected arrangements automatically. The compliance officer reviews, documents the determination, and either accepts the existing opinion as still applicable or initiates refresh.
This is what compliance infrastructure built for arrangement lifecycle management actually delivers. It’s also what spreadsheet-based tracking structurally cannot deliver — spreadsheets are static, and the trigger events that demand attention are continuous.
Common Questions About FMV Refresh Cadence
Is annual FMV refresh required under Stark Law?
Stark Law does not specify a calendar-based refresh interval. The regulatory expectation is that compensation remains within fair market value range throughout the term of the arrangement. Annual refresh is industry norm and operationally defensible as a floor, but is not the regulatory ceiling. Material change events can render a six-month-old opinion non-defensible.
What events trigger an out-of-cycle FMV refresh?
Material change events include: significant modification to the scope of services, change in compensation methodology or structure, material change in the underlying market data the opinion relied on, modification to the term or renewal structure, change in the physician’s role or specialty, and discovery that the original opinion relied on data that has been updated or corrected. Each trigger should be documented at the time the event occurs.
How long can an FMV opinion remain defensible without refresh?
There is no single answer. The defensibility depends on three factors: the stability of the underlying market data, the materiality of any changes to the arrangement, and the institution’s documented monitoring process. An opinion that was current at execution can lose defensibility if the institution doesn’t have a documented process to detect material changes in the interim.
Does material modification to an arrangement require FMV re-validation?
Yes. Any material modification to compensation terms, scope of services, or related arrangement elements typically requires FMV re-validation before the modification takes effect. The validation can take the form of a refreshed third-party opinion or a documented internal analysis explaining why the existing opinion remains applicable to the modified arrangement.
What documentation supports a “no refresh needed” compliance decision?
The documentation should record: the date the no-refresh decision was made, the compliance officer who made it, the specific change event evaluated, the rationale for why the existing FMV opinion remains applicable, and any reference materials consulted. The decision itself is reasonable in many cases. The undocumented decision is what creates enforcement exposure.
Closing Note
Annual FMV refresh is a reasonable floor. It is not a defense in itself. The institution’s defensibility argument under Stark and AKS rests on demonstrating that compensation remained within fair market value range throughout the arrangement’s term — which requires both calendar cadence and trigger cadence to operate together, with documentation of both maintained contemporaneously.
ArrowISE is built for the compliance program that wants both. The Defensibility Index methodology incorporates FMV currency as one of its five evidence dimensions, and the platform’s monitoring infrastructure surfaces trigger events as they occur rather than at annual review.