How Clinical Trials Fit Into Technology Assessment
Clinical trials are the backbone of technology assessment. Without them, you are working from theoretical models and anecdotal evidence, which does not hold up well in a health technology assessment report. When a new device, drug, or surgical technique comes along, assessors need comparative data that shows whether it actually improves patient outcomes relative to existing standards of care. The role is precise and somewhat unforgiving. Clinical trials provide the primary evidence for clinical effectiveness and safety. But they do not provide the full picture on their own. Health technology assessment pulls from multiple evidence streams, and clinical trials feed directly into two of them: the clinical benefit dossier and the economic modelling input. I spent years reviewing submissions for regional assessment bodies. The submissions that got the most attention were the ones where the trial design matched the decision problem. That sounds obvious until you see how often it does not. A company would submit a single-arm phase II trial for a technology that needed head-to-head comparison against a standard treatment, and then wonder why the assessment panel asked for a network meta-analysis instead of accepting the results at face value.
Here is what most people miss about clinical trials in this context. The trial design matters more than the sample size. A well-conducted pragmatic trial with 300 patients often carries more weight in an assessment than a tightly controlled explanatory trial with 1,200 patients, because the pragmatic trial reflects how the technology performs in real-world settings. Assessment committees are increasingly weighting practical effectiveness over idealized efficacy. Another thing beginners get wrong is the timing of trial reporting. If a pivotal trial is still ongoing when the technology assessment deadline approaches, assessors will mark the evidence as incomplete. This does not necessarily sink the assessment, but it triggers a recommendation for research uncertainty provisions, which can delay reimbursement decisions by months. I have seen this happen repeatedly with gene therapies where the follow-up period was too short to capture late adverse events. The workaround I learned after a few painful rejections is to structure trial protocols around the assessment endpoints from the beginning. Do not design a trial purely for regulatory approval and then hope it satisfies an HTA body. Regulatory pathways and HTA pathways have different endpoint preferences. Regulatory agencies want safety and efficacy. HTA bodies want quality-adjusted life years, comparative effectiveness, and subgroup analyses that show who benefits most. If your trial only reports overall response rates, you are leaving money and credibility on the table.
Specific pitfalls to watch for: Adverse event reporting granularity is one. Assessment panels need detailed safety data stratified by patient population, dosage, and concomitant medications. Vague adverse event summaries from trials get flagged immediately. I once reviewed a submission where the adverse event table grouped five distinct types of hepatic reactions under a single code. The assessors asked for reclassification, which took the sponsor three weeks and pushed the entire review timeline backward. Missing cost-of-illness data from trials is another silent killer. Some trial protocols collect health economic data, but the analysis plans are never finalized before the database locks. When I have controlled assessment workflows, I insist that economic data collection be pre-specified in the statistical analysis plan, not added retrospectively. You can analyze costs after the fact, but you cannot manufacture cost data that was never captured during patient visits.
Get the Full Details

There is a limit to what clinical trials can do in technology assessment, and it is important to state that plainly. Trials cannot answer every question an assessor has. They rarely capture long-term outcomes beyond five years. They do not reflect real-world adherence patterns. They are expensive and slow. When a technology has a long shelf life and subtle but meaningful downstream benefits, trial data alone will not suffice, and assessors will request modelling extrapolations, which introduces their own set of uncertainties. The most reliable approach I have found combines direct trial evidence with indirect comparative methods. When head-to-head trials are unavailable, use network meta-analysis to bridge the gap, but only after verifying that the transitivity assumptions hold across the studies you are linking. I ran into a case last year where a network meta-analysis was built on studies with different outcome definitions, and the pooled estimate was essentially meaningless. The assessors caught it, but it added six weeks to the review cycle. For anyone preparing evidence for a technology assessment, the practical takeaway is straightforward. Design your clinical trials with the assessment process in mind from day one. Align endpoints with HTA criteria. Collect granular safety and economic data prospectively. Plan for long-term follow-up if the technology claims durable benefits. And do not assume that a statistically significant result in a regulatory trial automatically translates to a favourable assessment outcome.