SystemMarket Access & Pricing

Payer Coverage Policy & PA Criteria Monitor

Payer policy monitoring that reads every PA criterion and checks every change against what the plan contracted

Every payer policy change caught within a day of posting, and checked against what the plan contracted.

See one case, screen by screen ↓
target0.9daysmedian from a policy posting to a cited alert
target412policieschecked every 4 hours across 64 plans and benefit managers
target18of 62changes in a month that moved access, each priced in covered lives
demo1,840patientson Veltrimab at Crestline who will re-authorize every 6 months instead of 12
The problem

Why payer policy changes are found a quarter too late

Plans and PBMs post a new medical policy, a formulary file or a preferred drug list revision whenever their P&T committee meets — on their own sites, in PDFs, in spreadsheets, on their own schedule. A new step through a competitor, a higher threshold or a shorter approval length can take effect a few weeks later. The access commitment in the rebate agreement says the plan should have given 60 days’ notice. Often nobody on the manufacturer side has read the new version yet.

So the change surfaces at the quarterly policy review, or when hub cases start coming back denied and the field calls in. By then patients have been turned away, the notice and cure period has started to slip, and the payer analytics team is rebuilding the criteria grid by hand — one policy, one indication, one criterion at a time — before anyone can say which plans are breaking which term, and for how many lives.

typical60–90dayslate — when a policy change first shows up in claims data
target62changesposted in one month across 412 watched policies
demo27daysof notice given by Crestline Health, where the contract asks for 60
Where a policy change’s days goestimated
By hand54 days
With the solution2.8 days
  • Noticing the plan posted a new version45 → 1 d
  • Reading the policy and pulling out the criteria2 → 0.1 d
  • Comparing it with the last version1 → 0.1 d
  • Checking it against the contract2 → 0.5 d
  • Sizing covered lives and patients1 → 0.1 d
  • Drafting and signing the notice3 → 1 d

Estimated split for one adverse change on a contracted plan, with a quarterly policy review and with the solution. The quarterly-review baseline is an estimate.

How it works

How a policy change moves

Six specialist agents fetch, read and compare every policy change, size its reach and check it against the contract; the payer intelligence lead confirms before any notice goes out.

What comes in
Policies in412 policies · payer sites, formulary files, state lists
Agents at work
Policy Watcherfetch + detect
Then
Criteria Extractorevery criterion, with its page
Then
Version Comparerredline
Impact Estimatorlives + patients
Then
Contract Guardclause quoted
A person decides
Payer intelligence leadconfirms the finding
What comes out
Cited change alert
Notice to the plan
Field brief for approval
One case, step by step

One policy change, from posting to signed notice

Crestline Health posts revision 14 of its psoriasis biologics policy on Oct 5, effective Nov 1. Here is what happens next, screen by screen, in the working solution.

  1. 01Wednesday, 09:10

    Immunology coverage, on one screen

    Lena Ortiz · Payer intelligence lead

    Lena opens the coverage pulse for Veltrimab and Corventa: 412 policies across 64 plans and PBMs. Three changes need her — Crestline, Bluepeak and Harbor — two plans are not meeting contract terms across 25.5M covered lives, and 92% of US lives have contracted access to Veltrimab in psoriasis — 89% once the published changes apply.

    Change wire: “Crestline Health · Step through Ostrelix added before Veltrimab” — “Veltrimab · Psoriasis · effective Nov 1 · caught 26 h after posting.”

  2. 02Oct 6 · 07:12

    Caught 26 hours after posting

    Policy Watcher

    The morning sweep fingerprints RX-PSO-117 and sees new content: revision 14, approved by P&T on Sep 29, posted Oct 5, effective Nov 1. The other agents take it from there — 14 pages and 9 criteria read, 4 criteria changed, 2 contract terms not met, 3.1M lives and 212 open hub cases on the plan.

    How the agents found it: Policy Watcher 0.8 s · Criteria Extractor 6.2 s · Version Comparer 2.1 s · Contract Guard 3.4 s · Impact Estimator 0.9 s.

  3. 03Redlined

    Four criteria tighten, five stay the same

    Version Comparer

    Against revision 13 of Jan 1, 2026: the step goes from one TNF inhibitor to one TNF inhibitor plus Ostrelix, body surface area from 3% to 10%, re-authorization from 12 months to 6, and the notice given is 27 days against the 60 required. Age, dermatologist prescriber, TB test, no combined biologic and the quantity limit are listed as unchanged.

    Old and new side by side — unchanged criteria are listed as unchanged.

  4. 04One click

    Every criterion opens its page

    Criteria Extractor

    Lena clicks the new step and the passage opens where it lives: page 3 of RX-PSO-117 rev 14, criterion B.4, from the stored version fingerprinted on fetch. Every field in the criteria database carries its page and line, and anything read below 0.85 confidence goes to a person.

    “The member has had an inadequate response, intolerance or contraindication to ONE preferred TNF inhibitor AND to Ostrelix.”

  5. 05Checked

    Two terms not met, both clauses quoted

    Contract Guard

    §4.2 of the Crestline 2026 Commercial Formulary Agreement says the plan shall not require a member to try or fail any Competitive Product before Veltrimab — and Exhibit B names Ostrelix. §7.1 asks for 60 days’ written notice of a utilization management change; 27 were given. The 10% BSA threshold is flagged under §4.5 as stricter than the label, but not counted as a breach: it matches Ostrelix’s own criteria, so parity holds.

    Flagged for you, not counted as a breach.

  6. 06Priced

    What the change is worth

    Impact Estimator

    3.1M covered lives on Crestline, 1,840 patients on Veltrimab on the plan, 212 open hub cases and about 38 new patients a month at risk — the last one marked as an estimate. Counts only: no patient detail leaves the hub.

    “From Nov 1 every patient re-authorizes every 6 months — 1,840 re-authorizations a half-year instead of a year.”

  7. 07Confirmed

    Lena confirms; the notice is drafted

    Lena Ortiz · Payer intelligence lead

    The agents propose, a person confirms. Lena presses “Confirm and draft notice” — “Not a breach” would close it with her reason, kept with the alert. The Notice & Brief Writer drafts the notice of non-compliance in the legal-approved template, with 5 citations: what changed, the terms not met, and what Crestline is asked to do before Nov 1.

    §9.3: if the failure is not cured within 30 days of the written notice, access rebates may be suspended for each quarter it continues.

  8. 08Signed · Oct 7

    The account director signs; the cure clock starts

    Sam Patel · Director, National Accounts

    Lena sends the draft to Sam to sign, with Dana Okafor copied for the cure clock. Sam signs electronically and the notice goes out; the 30-day cure period ends Nov 6. From now on the Contract Guard re-checks the Crestline policy every sweep until it is cured.

    “Signed and sent Oct 7 · 09:12 by Sam Patel · cure by Nov 6.”

  9. 09Every day

    Every notice and cure clock in one table

    Dana Okafor · Contract operations

    Crestline: 30 days left to cure, ends Nov 6. Northgate Rx, where the 2027 formulary puts a TNF step on Veltrimab in Crohn’s but none on Dravimab: 28 days left, ends Nov 4. Silverpine MA and Marlowe Health tightened access too, but there is no access agreement with either, so they sit with the account team with no contract clock.

  10. 10Good news too

    A field brief, approved before it reaches the field

    Dr. Maya Chen · Access compliance

    Bluepeak Medicare Rx removes the TNF step for Veltrimab in psoriatic arthritis for 2027 — better than contracted. The Notice & Brief Writer drafts the field brief from approved coverage wording: what changed, who it affects, what offices need to send. It goes to Dr. Maya Chen for approval before field reimbursement and hub teams see it.

    “Approved coverage wording only. Do not predict approval for an individual patient. Refer clinical questions to Medical Information.”

Who it’s for

Built for everyone who acts on a coverage change.

The same policy change, seen by the people who carry it — what their week looked like, and what it looks like now.

LO
Lena OrtizPayer intelligence lead
Confirms changes
Before
Finds policy changes at the quarterly review, then rebuilds the criteria grid by hand before she can say what moved.
Now
Starts the day from a change wire of cited, redlined changes already checked against the contract, and confirms or dismisses each one.
SP
Sam PatelDirector, National Accounts
Signs notices
Before
Hears about a breach from the field, weeks after the plan posted it, with half the notice period gone.
Now
Receives a drafted notice with the policy passage and the clause quoted side by side, and signs it the same morning.
DO
Dana OkaforContract operations
Cure clocks
Before
Tracks notice and cure dates in a spreadsheet that has to be told when a notice went out.
Now
Sees every open contract flag with its cure clock, owner and status, started the moment the notice is sent.
MC
Dr. Maya ChenAccess compliance
Approves briefs
Before
Reviews field messages written from scratch, checking each line against the policy.
Now
Approves briefs drafted only from approved coverage wording, every statement cited to the plan’s policy.
OH
Omar HaddadField reimbursement lead
Reads briefs
Before
Learns a plan changed its criteria when offices call about a denied PA.
Now
Reads approved briefs and the current criteria for every plan and indication, each cell opening the passage it came from.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents fetch, read and compare every policy change, size its reach and check it against the contract; the payer intelligence lead confirms before any notice goes out.

Policy Watcher

Fetches 412 payer policies, PBM formulary files and Medicaid preferred drug lists on schedule and spots a new version by its content, ignoring page furniture such as footer dates.

  • Public payer documents only
  • Licensed data used within its terms
  • Failed fetches are reported, never skipped
Criteria Extractor

Reads each policy and fills the criteria for every drug and indication — formulary status and tier, PA, steps and named agents, thresholds, prescriber, labs, approval length, quantity limits, site of care.

  • Every field carries its page
  • Never infers a criterion that is not written
  • Below 0.85 confidence, a person checks it
Version Comparer

Builds the redline between the old and new policy, lists each changed criterion, classifies it as adverse, favourable or administrative and counts the notice given.

  • Shows old and new side by side
  • Unchanged criteria are listed as unchanged
Impact Estimator

Adds covered lives, patients on therapy and open hub cases on the plan, so the team sees what a change is worth.

  • Counts only — no patient data leaves the hub
  • Estimates labelled as estimates
Contract Guard

Checks every changed criterion against the plan’s access commitments — competitor steps, parity, label-level PA, notice periods — and quotes the clause.

  • A person confirms every breach
  • Both passages always shown
  • Reads the contract system, never writes to it
Notice & Brief Writer

Drafts the notice of non-compliance for the account director and the field brief for compliance approval — every statement cited.

  • Never sends — a person signs
  • Field briefs need compliance approval
  • No efficacy claims in field briefs
Payer intelligence lead

Confirms; the account director signs. The agents propose; a named person decides.

Ask in plain words

Ask about any plan, policy or contract term

Ask in plain words — or tell it what to watch. Every answer cites the policy or the clause it rests on.

What changed at Crestline Health?

Revision 14 of RX-PSO-117 (psoriasis biologics) was posted Oct 5 and takes effect Nov 1. Three criteria tighten for Veltrimab: a step through Ostrelix after one TNF inhibitor, body surface area 3% → 10%, and re-authorization 12 → 6 months. Two terms are not met: §4.2 forbids a step through a competitor, and §7.1 needs 60 days’ notice — 27 were given. 3.1M lives.

Which plans are breaking our contract terms?

Two: Crestline Health (step through a competitor, 3.1M lives) and Northgate Rx (parity with an IL-23 competitor, 22.4M lives). Northgate’s notice went out Oct 5 — the cure period ends Nov 4. Marlowe and Silverpine tightened access too, but there is no access agreement with them.

How fast do we catch changes?

Median 0.9 days — about 21 hours — from a plan posting a policy to the alert over the last 30 days; Crestline was caught 26 hours after posting. The sweep runs every 4 hours over 412 sources. Before, changes surfaced at the quarterly review, often 45–90 days later — an estimate, not a measured baseline.

Alert me when any plan adds a step through Ostrelix

Done — a new watch rule: “Step through Ostrelix before Veltrimab or Corventa”, all 64 plans, alert immediately and route to the account director. Today one plan matches: Crestline Health. The rule is in Settings, where you can switch it off.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Coverage pulseWhat needs the payer intelligence lead today: changes to decide, contract terms not met, posting-to-alert time and where patients can get the medicine as contracted.
Every changeEvery new policy version, compared with the last one and with the contract, filterable by breach, adverse, favourable and form changes.
The change reviewThe policy redline, what changed and what did not, how the agents found it, and the contract check with the clauses quoted.
Criteria before and nowEach criterion before and after, marked harder or the same, with its source.
The source passageAny criterion opens the exact passage of the stored policy version it was read from.
ImpactCovered lives, patients on therapy, open hub cases and new patients at risk — counts only, estimates marked.
The notice, draftedA notice of non-compliance in the legal-approved template, every statement cited, ready for the account director.
Signed and sentSigned electronically by the account director; the cure clock runs from the day it is sent.
The field briefWhat changed, who it affects and what offices need to send — approved coverage wording, for compliance approval.
The criteria databaseCoverage criteria by plan, product and indication, today or as published, every cell opening the passage it came from.
The coverage dashboardChanges detected by week, days from posting to alert, lives by access level and what is changing, by plan.
Open contract flagsEvery breach with its term, lives, notice or cure clock, owner and status.
Your watch list and routingThe sweep schedule, the sources watched, who decides a breach, the large-plan threshold and who approves field briefs.
Governance

Built for contract and compliance work: cited, confirmed, signed.

Every criterion cites its pageClick any criterion, redline or sentence of a notice to open the exact passage of the policy, formulary file or contract it came from — the policy and the clause shown side by side.
A person confirms every breachThe Contract Guard proposes; the payer intelligence lead confirms or records “not a breach” with a reason, which is kept with the alert.
The account director signs the noticeNotices are drafted in the legal-approved template and never sent by an agent. The account director signs electronically, and the cure clock starts when it goes out.
Contracts are read, never changedAccess terms are read from the contract system, which stays the record. Licensed formulary data is used within its licence.
Field briefs approved before releaseBriefs use approved coverage wording only, make no efficacy claims, never predict approval for a patient, and need access compliance approval before the field sees them.
Counts only, every step on the recordNo patient-level data leaves the hub — impact is counts, with estimates marked. Each agent step and each human decision is on the change’s activity trail, with who, what and when.
Configuration

Your watch list and routing, not ours

What the agents watch, who decides and how alerts are routed are settings, changed in a minute and recorded in the audit trail.

SettingDefaultChoose from
Sweep scheduleEvery 4 hours (06:00, 10:00, 14:00…)Every 4 hours · Daily at 06:00 · Weekly on Monday
Who decides a contract breachLena Ortiz → account directorLena Ortiz → account director · Account director only
An adverse change goes to “Needs you” when the plan covers at least500,000 lives500,000 · 1 million · 2 million lives
Who approves field briefsDr. Maya Chen · access complianceDr. Maya Chen · access compliance · Omar Haddad · field reimbursement
Close label-matching changes automaticallyOnQuantity limits and specialist rules that match the label need no review
Push new PA forms to open hub casesOnHub cases on the plan get the new form and a note
Licensed formulary data feedOnOptional vendor feed for covered lives and tiers · licence terms apply
Watch rulesAny step through a competitor product · approval length shortened · new PA form versionDescribe a rule in plain words
Connections

Works with the sources you already watch

Payer portals and medical policiespolicy pages and PDFs, medical and pharmacy benefit
PBM formulary filesexclusion lists and UM criteria, CSV and XLSX
Medicaid preferred drug listsstate and managed-care lists
Your contract systemaccess commitments, read only
Covered-lives dataplan directory and an optional licensed formulary feed
Hub and patient servicesopen hub case counts, new PA forms pushed to cases
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0.9days
median from a policy posting to a cited alert
Quarterly45–90 days
With agents≈ 0.9 days
target
412policies
checked every 4 hours across 64 plans and benefit managers
target
18changes
that moved access found among 62 in a month, each priced in covered lives
18 of 62 moved access
last 30 days

“demo” = seen in the working solution, on its sample plan data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published payer-intelligence analyses (claims data shows a policy change 60–90 days late; the quarterly-review baseline is an estimate). People, plans, products and companies named on this page are characters in the working solution.

Questions

What market access teams ask us.

What is payer coverage policy monitoring?

Watching payer and PBM medical policies, formularies, preferred drug lists and PA forms for new versions, reading what changed for each drug and indication, and acting on it. The Payer Coverage Policy & PA Criteria Monitor does this on a schedule with six agents and checks every change against the plan’s access commitments.

How does it extract prior authorization criteria?

The Criteria Extractor reads each policy and fills the criteria for every product and indication — formulary status and tier, PA, step therapy and the named agents, clinical thresholds, prescriber specialty, labs, initial and renewal approval length, quantity limits and site of care. Every field carries its page and line, it never infers a criterion that is not written, and anything below 0.85 confidence goes to a person.

How does it check a policy change against our contracts?

The Contract Guard reads the plan’s access terms from your contract system — competitor steps, parity with named products, PA no stricter than the label, notice and cure periods — and decides for each changed criterion whether the term is met, not met, or needs a person. It quotes the clause and the policy passage side by side.

Does it send notices to payers on its own?

No. A person confirms every breach, the account director signs every notice, and field briefs need access compliance approval before release. The agents draft and check; people decide, and every decision is on the activity trail.

Which sources does it watch?

Payer portals and medical policy PDFs, PBM formulary files with exclusion lists and UM criteria, Medicaid preferred drug lists and PA request forms — plus an optional licensed formulary feed for covered lives and tiers, used within its licence terms.

How quickly does it catch a policy change?

The design goal is a median of 0.9 days from a plan posting a policy to a cited alert, with 412 policies checked every 4 hours. In the working solution, Crestline Health’s revision was caught 26 hours after posting. The sweep schedule is a setting.

Does patient data leave the hub?

No. The Impact Estimator works with counts only — covered lives, patients on therapy and open hub cases on the plan — and marks estimates as estimates.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements — your watch list, your products and indications, your access commitments and notice template — and it goes live once every quality gate has passed. We will walk you through it on your own plans first.

See it on
your payer policies.

We’ll run the Coverage Policy Monitor on your own watch list and access commitments.