Briefing Note
Why supportability depends on when you ask
A claim is not simply true or false. It is supportable or not supportable at a specific time, under a specific evidence record, for a specific use. Change any of those, and the answer changes.
The claim that was fine last quarter
Consider a market-access team preparing a payer deck in March. The deck includes a claim: "Therapy X reduces hospitalization-related outcomes in high-risk patients with Condition Y." At the time, the evidence supports it — the pivotal trial showed benefit in the high-risk subgroup, the label includes the indication, and the guideline recommends use.
By August, three things have changed: a new trial readout shows no benefit in moderate-risk patients, the guideline narrows its recommendation to patients with prior hospitalization, and the label adds a safety signal. The claim is still in the deck. The deck is still in circulation.
Is the claim still defensible? That depends on when you ask. In March, yes. In August, no — at least not as written.
Five timelines, one claim
Every healthcare claim lives on several different clocks simultaneously:
- Evidence time
- When did the studies, safety data, endpoint analyses, or real-world evidence appear? A trial published after the claim was written can either strengthen or weaken it.
- Wording time
- When did the claim’s language change? "May reduce hospitalization-related outcomes" became "reduces hospitalization" — two words dropped, supportability changed.
- Authority time
- When did a guideline, label, payer policy, or regulator adopt, weaken, or retire the claim? A guideline change can undermine a claim even if no new evidence appeared.
- Use time
- When did the claim move into a higher-stakes context? An internal scientific note may tolerate uncertainty that a payer-facing deck cannot.
- Review time
- When was the claim last checked, under what threshold, and what would force re-review? The longer the gap, the more drift accumulates.
What a evidence check reconstructs
A claim supportability evidence check gives you an as-of record: what the claim asserted, what the evidence supported at the time, what changed since, and whether the claim is still safe to use as written.
It answers questions that most evidence tools do not:
- Was this claim supportable when the deck was approved?
- Has a guideline softened since the claim was written?
- Did the claim broaden — lose a caveat, drop a subgroup — between versions?
- Has the evidence base shifted so that the claim now requires narrowing?
- Is the claim being used in a higher-stakes context than it was written for?
Why "as of" matters
Most evidence tools answer from the present: "What does the current corpus say?" That tells you whether a claim is supportable now. It does not tell you whether a claim was supportable then — at the time of MLR approval, at the time of a payer meeting, at the time of an investment memo, at the time of a formulary review.
For audits, disputes, diligence, and quality review, the as-of question is the one that matters. The system should be able to reconstruct what the world looked like at the decision point — not just what it looks like after the fact.
From snapshot to memory
The strongest defense against claim drift is not more frequent manual review. It is a supportability record — a structured trace that tells you what the claim asserted at each point in time, what supported it, what changed, and when re-review became necessary. That record becomes institutional memory: what the organization has claimed, reviewed, approved, challenged, narrowed, and retired.
Start with the claim your team relies on and the review window in front of you. Build the record. Let the system tell you when the claim is no longer safe to use as written.