Executive Controls for Value-Based Care Pilots That Link Payment to Preventive Medication Adherence Stabilization

Medication-adherence pilots often attract support because the logic is straightforward. Better refill reliability should reduce avoidable deterioration, emergency use, and preventable service disruption. The risk is not the idea. The risk is weak executive control over who enters the pilot, how adherence work is targeted, and whether reported improvement can withstand payer scrutiny.

Strong value-based care innovation depends on disciplined controls around pharmacy risk, intervention timing, and settlement logic. That discipline also connects with lessons from new service models and the wider governance structure within the Innovation, Pilots & Emerging Models Knowledge Hub. When those controls hold, providers can show Medicaid and managed care partners that adherence-focused pilot work was targeted, measurable, and contractually defensible.

Weak adherence control can turn preventive innovation into disputed refill claims, uneven intervention effort, and fragile payment confidence.

Pilot credibility weakens when executive teams do not control baseline medication-risk activation

Medication-adherence models fail early when providers cannot prove that participants entered the pilot with a valid and documented adherence risk profile. Medicaid managed care organizations and CMS-aligned innovation arrangements expect providers to show that the participant met the contract rule, that baseline refill or access instability existed before intervention, and that exclusions were applied consistently. The operational gain is immediate. Leaders get a locked starting point for measuring adherence change without retrospective population shaping.

Operational example 1: controlled medication-risk activation for an adherence pilot

Step 1: Create the adherence episode record

The pharmacy innovation manager must create the adherence episode record within one business day of referral using the pilot intake platform, payer eligibility file, and medication access dashboard. The record must establish whether the participant meets the pilot definition of adherence instability before any adherence support is logged as pilot activity. Required fields must include:

participant ID, payer eligibility status, baseline refill-gap days, medication class code, and exclusion reason code where relevant. The episode record must be stored in the restricted adherence-pilot library and linked to the active contract pathway. Cannot proceed without:

written confirmation that the refill-gap lookback window matches the pilot contract and that payer eligibility is active on the proposed episode start date. Auditable validation must confirm:

participant ID matches the referral source, baseline refill-gap days match the medication access dashboard, and medication class code matches the current medication profile before the episode is marked pilot-eligible.

Step 2: Authorize adherence episode activation

The chief operating officer must review the adherence episode record within two business days using the activation approval log and the pilot rule matrix. The decision must classify the case as activated, pending clarification, or rejected. Required fields must include:

participant ID, activation decision code, review date, reviewer ID, control status, and next checkpoint date. The approval record must be stored in the executive pilot register and reviewed by compliance and payer relations before adherence intervention begins. Cannot proceed without:

a named owner and deadline for every pending clarification affecting the baseline adherence profile. Auditable validation must confirm:

every activated case has a valid baseline risk basis, every rejected case has a coded rationale, and no adherence support activity is entered into the live pilot pathway unless the decision is visible in the executive register.

This practice exists because adherence pilots are highly exposed to baseline distortion. The specific failure prevented is selective activation, where staff enroll participants after access barriers are already easing or exclude harder medication cases through delay. Managed care partners and state oversight entities often test whether adherence improvement is measured against a locked starting position rather than a shifting risk picture.

If this control is absent, teams may activate low-risk cases, misclassify refill instability, or begin intervention before baseline evidence is complete. Observable patterns include disputed denominator logic, inconsistent exclusion use, and payer concern that reported improvement reflects weak activation discipline rather than real operational impact.

The observable outcome is a stable and auditable adherence episode base. Evidence sources include episode records, activation logs, rejection records, and payer reconciliation notes. Measurable improvements often include fewer activation disputes, faster eligibility decisions, and fewer retroactive changes to the baseline adherence population.

Outcome value weakens when adherence support is not deployed through a fixed barrier-resolution sequence

Medication-adherence pilots do not create value because staff reminded people to take medication. They create value when refill, transport, authorization, education, and caregiver barriers are identified in sequence, assigned quickly, and escalated before the next refill failure occurs. Leaders need to show why one participant received pharmacy coordination, another received transport support, and another moved to clinician review. The reader gains a model for proving that intervention intensity followed barrier type and refill risk.

Operational example 2: auditable adherence intervention deployment inside a value-based model

Step 3: Release the adherence barrier-resolution pathway

The adherence supervisor must release the barrier-resolution pathway within forty-eight hours of activation using the intervention workflow board, barrier screening tool, and staffing assignment system. The pathway must specify the primary adherence barrier and the next required action rather than broad follow-up expectations. Required fields must include:

participant ID, barrier category code, intervention type, assigned lead, target action date, and escalation threshold code. The released pathway must be stored in the pilot delivery workspace and routed to pharmacy coordination, case management, and supervisory leads the same day. Cannot proceed without:

confirmation that the assigned lead has capacity and role authority to complete the intervention inside the contracted action window. Auditable validation must confirm:

barrier category code matches the screening record, intervention type matches the pilot intervention framework, and target action date aligns with the refill-risk rule before the pathway is marked active.

Step 4: Reconcile refill stabilization or escalation failure

The regional pilot supervisor must review pathway completion every seven calendar days using the adherence completion log and the unresolved-barrier tracker. The review must classify each case as stabilized, partially stabilized, or escalated. Required fields must include:

participant ID, stabilization status, unresolved dependency count, escalation status, review date, and validation timestamp. The reconciliation record must be stored in the pilot assurance archive and reviewed in the weekly interdisciplinary huddle by operations, clinical leadership, and finance. Cannot proceed without:

a coded reason for every incomplete barrier action and a named owner for every escalation dependency. Auditable validation must confirm:

all required intervention actions are evidenced in the delivery log, unresolved dependencies are visible in the barrier tracker, and every escalated case has a dated next checkpoint before the huddle closes.

This practice exists because adherence pilots often fail through diffuse effort. The failure prevented is generic outreach, where some participants receive repeated reminders while structural refill barriers remain unresolved. Medicaid innovation models and managed care medication pilots generally expect providers to show a defensible link between the documented barrier, the intervention deployed, and the refill outcome later reported.

Without this control, intervention effort becomes uneven and difficult to defend. Observable patterns include repeated refill gaps after nominal outreach, overloaded pharmacy coordinators, unresolved prior authorization barriers, and weak evidence that the pilot model differed from ordinary case management.

The observable outcome is stronger barrier-to-intervention logic and clearer adherence defensibility. Evidence sources include pathway files, completion logs, barrier trackers, and refill stability reports. Measurable improvements often include faster intervention release, fewer active cases without assigned action, and stronger refill stability among participants with the highest baseline access risk.

Financial confidence fails when boards cannot see whether refill improvement claims are settlement-ready

Medication-adherence pilots often generate persuasive reports about refill reliability, sustained possession, and lower downstream utilization. Those claims are fragile if refill methodology, observation windows, and claims lag are not actively governed. Executive leadership must show whether adherence performance is credible enough to support milestone payment, shared savings, or contract expansion. Funders and boards need evidence that the payment position can survive methodological challenge.

Operational example 3: board-level refill settlement assurance for an adherence pilot

Step 5: Build the refill settlement file

The chief financial officer must build the refill settlement file monthly using the pilot contract workbook, refill performance register, and claims lag monitor. The file must show whether reported adherence improvement can credibly support payment under the live arrangement. Required fields must include:

pilot month, activated episode count, refill stabilization rate, sustained adherence rate, claims lag percentage, and unresolved methodology question count. The file must be stored in the board finance portal and reviewed by finance, compliance, and the pilot executive sponsor before committee circulation. Cannot proceed without:

documented reconciliation between the refill performance register and the locked activation roster for the same reporting period. Auditable validation must confirm:

activated episode counts match the locked episode file, refill stabilization rates match the approved methodology, and claims lag percentages reflect the live lag monitor before any settlement position is shown to the board.

Step 6: Authorize or restrict adherence-payment statements

The board finance committee chair must review the refill settlement file at the next scheduled committee meeting or earlier if payment exposure is material. The committee must decide whether the pilot’s settlement position is supportable, provisional, or restricted. Required fields must include:

board decision code, settlement-position status, review date, executive owner, residual risk rating, and next checkpoint date. The decision must be stored in the governance action register and linked to the pilot contract file. Cannot proceed without:

clear notation of any methodology dispute, lag risk, or unresolved observation-window issue affecting confidence in refill-based claims. Auditable validation must confirm:

every board statement about incentive potential matches the current evidence base, every restriction has a named follow-up owner, and no external settlement representation exceeds the approved board position.

This practice exists because adherence pilots are often judged by improvement that may later prove temporary or methodologically unstable. The failure prevented is premature financial optimism, where the provider presents refill improvement as payment-ready before sustained adherence and lag-sensitive utilization effects are fully reconciled. CMS-aligned managed care arrangements expect disciplined settlement governance, not optimistic medication-access reporting without control.

If absent, the organization may overstate pilot value, understate downside exposure, and weaken payer trust when later data development changes the payment position. Observable consequences include disputed adherence rates, inconsistent finance papers, and executive decisions built on unstable refill assumptions.

The observable outcome is stronger settlement governance. Evidence sources include settlement files, board action logs, lag analyses, and methodology reconciliation notes. Measurable improvements often include fewer payment reversals, fewer external corrections, and stronger board challenge to unsupported adherence claims.

Stable adherence innovation depends on controlled episode activation, fixed barrier resolution, and governed settlement evidence

Value-based medication-adherence innovation becomes credible only when the risk baseline, the intervention sequence, and the payment logic are all controlled in live operations. A defensible activation rule prevents denominator drift. A fixed barrier-resolution pathway shows what the pilot actually delivered before refill instability caused greater harm. Board-level settlement assurance keeps refill-improvement claims inside disciplined governance boundaries. Together, these controls help community providers show Medicaid partners and managed care plans that adherence innovation is operationally real and financially supportable. Sustainable pilots are the ones that can prove when instability began, how barriers were resolved, and why every payment statement survived executive and board challenge.