M14 · THE PRACTITIONER'S WORKSHOP

It's not a report. It's a case.

On your desk is a manufacturer's economic analysis for a new drug. It's immaculate. The modelling is competent, the references are current, the ICER comes out at £18,000 per QALY — comfortably under the threshold. You check the arithmetic: it's correct. You look for errors: there aren't any. By every technical standard, it's a clean, professional piece of work recommending that the drug be funded.

And yet an experienced assessor reads it with narrowed eyes. Not because they suspect a mistake — they don't — but because they know something about what they're holding. This document was produced by a company that will earn a great deal of money if the drug is funded, and nothing if it isn't. It was written by skilled health economists whose job was to make the strongest honest case for reimbursement. It is not a neutral scientific report that happens to favour the drug. It is a case — an argument, assembled to persuade.

That single shift in how you read it changes everything. The question is no longer "where is the error?" — because there usually isn't one. The question is "how was this built?" This lesson, and this whole final module, is about the craft of reading a case: not hunting for mistakes, but seeing the shape of the argument, and reconstructing what an impartial version would have said.

Advocacy, not fraud.

Let's be precise about what a manufacturer's submission is, because both naïve extremes are wrong. It is not fraud — the manufacturer is not lying, faking data, or miscalculating. Outright deception would be caught, and the consequences (regulatory, reputational, legal) would be catastrophic; no serious company plays that game. But it is also not a neutral, disinterested report. It sits in between, in a category that's easy to miss if you've only been taught to check for errors: it is advocacy.

Here's how advocacy works without a single lie. Any real economic analysis contains dozens of points where the methodology permits a range of honest, defensible choices — which comparator to use, which endpoint, how long a time horizon, how to extrapolate beyond the data, which source to take a utility value from, which population to analyse. At each of these forks, more than one answer is legitimately arguable. And at each one, the manufacturer — rationally, legally, and without any individual choice being wrong — selects the answer that happens to favour their drug. Each pick, examined alone, is defensible: "this comparator is used in some settings," "this extrapolation fits the data acceptably," "this subgroup was pre-specified." No error to point to.

The tell isn't in any single choice. It's in the pattern. Think of it as the testimony of a witness called by one side in court: every sentence they say may be true, and yet the whole testimony is shaped, selected, and sequenced to persuade. Your job as the assessor is not to catch a lie — there may be none — but to recognise that you are reading a case, and to work out what the impartial truth underneath it looks like. And the way you do that is by following the levers.

Follow the levers.

So how do you actually read a case, rather than a report? You go through it lever by lever — every point where a choice was made — and at each one you ask the same four questions:

  1. What choice was made here? Identify the fork: the comparator, the horizon, the extrapolation, whichever it is.
  2. Was it justified, or merely permissible? There's a world of difference between "this is the right choice, and here's the clinical and methodological reason" and "this is within the range of things you're allowed to do." Advocacy lives in the gap between justified and permissible.
  3. Which way does it push the result? Does this choice lower the ICER (favour the drug) or raise it (against the drug)? Almost every choice pushes one way or the other.
  4. What would an equally honest opposite choice do? If you flipped this to the impartial best answer, how much would the ICER move?

Notice what this is not. It's not checking the arithmetic — the arithmetic is fine. It's not hunting for a mistake — there isn't one. It's tracing direction: at each fork, which way did they turn, and were they entitled to? One lever, by itself, tells you little — any single defensible choice is, well, defensible. The power of the method comes from doing it across every lever and then stepping back to look at the pattern of directions. Because a case reveals itself not in any one turn, but in whether all the turns went the same way.

The map of levers.

Here's where this final module pays off everything that came before, because the levers are the course. Every place a manufacturer can tilt an analysis is a topic you've already learned to build — and now you learn to detect. The main levers, roughly in order of power:

You know each of these intimately, because you spent this course learning to construct them. Reading a manufacturer's case is that same knowledge, run in reverse: where you once asked "how do I model this properly?", you now ask "how might this have been tilted, and which way?"

Follow the levers, live.

Here's a manufacturer's submission with an ICER of £18,000 — under the £30,000 threshold, so "fund." Each lever below is currently set to the manufacturer's choice — defensible, but favourable. Flip any lever to the impartial choice and watch the ICER move. The lesson is in what it takes to change the verdict. (An illustrative additive model — real levers interact; here they're additive to show the mechanism.)

ICER

£18,000

Threshold: £30,000

FUND ✓

Levers on the manufacturer's side: 5 of 5

Comparator

Survival extrapolation

Endpoint

Time horizon

Utility source

All five levers are set to the manufacturer's favourable choice. Start flipping them to their impartial setting.

ICER: £18,000 · Verdict: FUND ✓ · Levers on the manufacturer's side: 5 of 5

Watch what it took. No single lever was the smoking gun — flip any one and the verdict mostly survives, exactly as the manufacturer would argue. But the £18,000 was never one number; it was five favourable choices stacked on top of each other, each defensible alone, together carrying the drug from "reject" to "fund." That's how advocacy works: not one lie, but a direction — every fork turned the same way. And here's the signature you're looking for: five independent choices, and all five happen to favour the drug. Flip them to impartial and the case dissolves. You never found an error. You found a slope.

Now you.

For each analytic choice, which way does it push the ICER?

1. Comparing the drug to an older, weaker treatment instead of the current standard of care.

2. Choosing a hard clinical endpoint over a favourable surrogate.

3. Extrapolating the survival curve with an optimistic long tail beyond the trial data.

4. Restricting the analysis to the subgroup where the drug performed best.

5. Widening the time horizon so a slowly-accumulating benefit keeps adding up.

6. Applying the reference-case discount rate to health benefits rather than a lower one.

Direction betrays intent.

Now the deep point, the one that separates an expert assessor from a checklist-follower. You will rarely be able to say "this choice is wrong." Each one is defensible; the manufacturer will defend each one, correctly. So if your critique is "I don't like this comparator," you'll lose the argument — they'll show it's been used elsewhere, and move on.

The power isn't in any single lever. It's in the distribution of directions. Ask yourself: if these choices were being made impartially — genuinely trying to model the truth — which way would they fall? Randomly. Some would happen to favour the drug, some would happen to go against it, scattering both ways, because an honest modeller isn't steering toward a result. So when you open a submission and find that every debatable choice, all of them, happens to favour the drug — comparator, endpoint, horizon, extrapolation, utilities, all tilting the same way — you are looking at something with the probability of ten coin-flips all landing heads. Not impossible for any single flip. Astronomically unlikely as a set. That improbability is your finding.

And here's why it's such a strong finding: you don't have to prove any individual choice is wrong. You concede that each is defensible — and then point out that their unanimous direction is not something impartial modelling produces. You're not attacking the assumptions; you're attacking the improbability of their alignment. That's an argument with no good rebuttal, because the manufacturer can defend each choice individually but cannot explain why all of them, independently, happened to help. Direction betrays intent — even when every step is clean.

The right response: rebuild, don't reject.

So what do you do with a case you've read this way? The immature move is to write "the analysis is optimistic and biased — we reject it." This is useless, for a simple reason: every manufacturer submission is optimistic and biased. Saying so is a truism, not an assessment. A decision-maker who's told "it's biased" still has no idea what the drug is actually worth. You've labelled the problem without solving it.

The expert move is harder and far more valuable: rebuild the base case impartially. Take the manufacturer's model — which is competently built, remember — and flip each lever to its impartial, best-justified setting: the true standard of care as comparator, the hard endpoint, the cautious extrapolation, the full uncertainty range. Then re-run it. Now you have two numbers to put in front of the committee: the manufacturer's £18,000, and your impartial reconstruction's £47,000. The difference between them is your assessment. It quantifies exactly how much of the claimed cost-effectiveness was real and how much was constructed.

And crucially, sometimes the benefit survives the reconstruction — you flip every lever and the ICER barely moves, which tells you the case was genuinely solid, and you can say so with confidence. Other times it collapses, and you can show precisely why. Either way, you've done something a mere accusation never could: you've replaced "I distrust this" with "here is the impartial number, and here is how it was reached." That's not hostility to the manufacturer — it's the highest form of respect for the process: instead of believing the case or rejecting it, you've measured how much truth remains once the advocacy is subtracted. Reading the levers tells you how it was built; rebuilding tells you what it's really worth.

What's the strongest and most useful thing to do?

You're assessing a manufacturer's submission. Every modelling choice is individually defensible, the arithmetic is correct, and the ICER is £19,000. But you notice the comparator is a weaker-than-standard treatment, the survival curve has an optimistic tail, the analysis uses a favourable subgroup, and the sensitivity analysis varies only minor parameters. What is the strongest and most useful thing to do?

Why this matters for HTA

Critically appraising a manufacturer's submission is the single most common thing many HTA practitioners actually do — and doing it well is a specific discipline, not general scepticism:

A manufacturer's submission is a witness for one side: every sentence may be true, and the whole thing is still built to persuade. Your task is not to catch it lying — it usually isn't — but to reconstruct the impartial testimony underneath. Read the levers to see how the case was built; rebuild the base case to learn what it was really worth.

Reading the manufacturer's case, in one breath.

Don't look for the lie — there usually isn't one. Look at the slope of the whole thing: which way every choice leaned, and whether an honest model would ever lean that consistently. Then rebuild it straight, and read off what the technology was actually worth.

You can now take a manufacturer's case apart and rebuild an impartial number from it — the analytical core of the job. But an assessment that no one reads or understands changes nothing. The number has to become a recommendation: written so a committee grasps it, trusts it, and can act on it. Turning analysis into a decision-ready HTA report is the next lesson.