HEOR Systematic Literature Review Protocol Template

Practical HEOR/HTA protocol resourceBy Dr. Esmaeel Saeedy RobatEvidence checked: 10 August 2026

A decision-ready HEOR or HTA review needs more than a conventional systematic-review protocol. It must preserve the connection between the institutional decision, the relevant comparator set, the populations that matter to that decision, the evidence streams needed to support it, and the timing at which the evidence package will be judged. NICE explicitly organizes evidence submissions around a decision problem and relevant comparators; PBAC begins clinical evaluation from the proposed indication and nominated comparator; current EU joint clinical assessment uses a PICO-defined assessment scope that may contain several decision questions.1,2,7,13

This template is designed for that planning layer. It does not reproduce PRISMA-P fields, Boolean search syntax, screening mechanics, risk-of-bias tutorials or meta-analysis instructions. Those remain important, but they are generic review infrastructure rather than the distinctive problem this page solves. Here, the task is to configure an evidence program that remains usable for a payer, HTA body, comparative-effectiveness team or economic model when the review moves beyond publication and into a decision process.15,17,18

Distinct task: use the builder to document the decision context, comparator/PICO architecture, evidence streams, source and update plan, study lineage, downstream-readiness fields and governance. The generated blueprint is a planning record, not a registration form and not a claim that every proposed synthesis will later prove feasible.

What this protocol adds beyond a generic systematic-review protocol

A generic protocol can be methodologically strong and still produce evidence that is poorly suited to HTA. The failure usually occurs before screening. The review may include the population used in pivotal trials while the reimbursement decision concerns a narrower treatment line. It may compare the technology only with placebo even though the relevant payer comparator is active treatment. It may collect efficacy endpoints but omit treatment switching, subsequent therapy, candidate effect modifiers or data-cut maturity that later become necessary for comparative-effectiveness work. It may finish six months before submission without any rule for handling a new pivotal readout.

Conventional protocol questionHEOR/HTA extension in this resourceWhy the extension matters
What is the review question?What decision is being supported, in which jurisdiction, for which proposed use and deadline?The same clinical evidence can have different relevance when the reimbursement population, treatment line or comparator changes.1,12
What is the PICO?Which PICOs or comparator mappings are needed across the decision scope?One technology can create several decision questions. A single static PICO can hide subgroup and comparator obligations.6,7
Which studies are eligible?Which evidence streams need different eligibility, sources, appraisal and outputs?Clinical-effectiveness trials, utility studies, natural-history cohorts and resource-use evidence should not be processed as one undifferentiated evidence class.3,16
What data will be extracted?What data must remain available for downstream direct synthesis, ITC/NMA feasibility or economic inputs?Prospective capture reduces later rework without prejudging whether an indirect analysis is credible or even possible.2,8
When was the search run?What are the search date, evidence cutoff, analysis freeze, submission date and update triggers?HTA evidence has a clock. Search currency and trial data maturity can change before the institutional decision.11,22
Which publication supplies the result?How are multiple reports and data cuts linked to one underlying study?Registries, abstracts, journal papers, CSRs and regulatory reports can describe the same trial and contain different endpoint maturity.14,15
Decision-linked protocol architecture Three horizontal layers show decision controls, evidence-program modules, and decision-ready outputs. Arrows connect decision context to PICO and comparator mapping, evidence streams, lineage and currency controls, then to direct synthesis, indirect-comparison readiness, and economic evidence handoffs. A protocol built around the decision, not around the manuscript Each layer answers a different planning question. None of the downstream analyses is assumed feasible in advance. DECISION CONTROLS Jurisdiction & decision PICO & comparator map Submission & evidence dates EVIDENCE-PROGRAM MODULES Evidence streams clinical · RWE · utility · cost Eligibility & sources stream-specific rules Study lineage records · data cuts · conflicts Currency & amendments triggers · freeze · governance DECISION-READY OUTPUTS Direct/narrative synthesis ITC/NMA feasibility handoff Economic-input evidence handoff
Figure 1. Decision-linked protocol architecture. The review is configured so that evidence remains traceable to the decision and reusable downstream; the diagram does not imply that every project needs every stream or that an indirect analysis will be feasible.

Before you fill the template: define the evidence program, not just the review

Start by asking which evidence functions the decision actually needs. A clinical-effectiveness stream is common in reimbursement work, but epidemiology, natural history, treatment patterns, RWE, health-state utilities, resource use or published economic evaluations are conditional. NICE separates several of these evidence classes in company submissions, and Cochrane’s economics guidance similarly distinguishes full economic evidence review from lighter or absent economic components depending on the decision and available resources.1,16

The protocol should therefore assign each stream a purpose. “Utilities” is not a purpose by itself. The team should know whether utility evidence is needed to populate a particular health state, test the applicability of trial-derived EQ-5D values, or identify a mapping source. “RWE” is equally incomplete unless the intended use is stated: external control, natural history, treatment patterns, safety, resource use or contextualization. NICE’s RWE framework is explicitly use-case oriented, and that logic is more useful than treating observational evidence as one broad category.5

Core question

What decision must this evidence survive?

Record the assessment route, proposed population, treatment line, comparators and downstream consumers before the search is frozen.

Conditional modules

Which evidence streams change the decision?

Include only streams with a stated decision use. Keep their eligibility, sources, appraisal and outputs separate when those differ materially.

Future analysis

What must be captured now?

Collect the trial, comparator, outcome and data-version information that a later quantitative or economic team will need, without choosing the later model prematurely.

Build the HEOR/HTA protocol blueprint

The builder below is intentionally modular. It is not a scoring tool. A blank field is not a methodological failure; it is a prompt to decide whether the information is known, genuinely not applicable, or unresolved and therefore governed by an amendment or feasibility rule. Entries are stored only in the current browser through local storage.

Decision-linked HEOR/HTA protocol builder

Complete the modules that apply to your evidence program. Generate a narrative protocol blueprint when the planning decisions are sufficiently mature.

1 Decision and submission context

Define the institutional decision before specifying the evidence architecture. Jurisdiction can change the comparator, target population, evidence sources, applicability test and timing.

2 PICO and comparator architecture

Use a matrix when one technology creates several decision questions. The master evidence universe may overlap, but each PICO should retain a stable identifier and its own comparator mapping.

PICO A
Comparator(s)
Why this comparison matters
PICO B
Comparator(s)
Why this comparison matters
Comparator uncertainty
How it will be resolved
Amendment trigger
3 Evidence-program stream map

Select streams because they serve a stated decision use, not because they appear on an HEOR checklist.

Economic evidence is conditional. A full economic-evidence review is not automatically required for every project or parameter. The depth of searching should reflect the decision use, uncertainty, competing estimates and whether an authoritative local source is the correct evidence source.3,16
4 Stream-specific source architecture and evidence currency

Do not copy one database list across all streams. Record the source architecture and the dates that govern currency. Detailed search syntax belongs in the dedicated search documentation.

There is no single cross-jurisdictional month threshold that should be presented as a universal HTA rule. Agency procedures and project risk determine the appropriate trigger structure; Cochrane’s own update timing standards should not be relabeled as payer requirements.10,22

5 Eligibility rules and controlled refinement

Prespecification remains the default. Where an HTA-specific method legitimately anticipates refinement, define the trigger and governance before seeing the results that could bias the decision.

Controlled refinement is not permission for post hoc cherry-picking. NICE DSU TSD 27 addresses prioritization in NICE HealthTech literature reviews when the volume of evidence differs from expectations. If that logic is relevant to the project, the refinement should be governed, documented and separated from result-driven exclusions.4
6 Study lineage, records and data-cut reconciliation

The unit of evidence is the underlying study, not each publication. Build a plan for linking records before extraction begins.

7 Extraction and appraisal map by decision use

Do not force every stream through one extraction form or one quality tool. Map fields and appraisal to the study design and the decision use.

8 Downstream-readiness and contingent synthesis plan

Prespecify the feasibility assessment and the data it will need. Do not promise an NMA or population-adjusted comparison before the evidence structure is known.

Detailed assumptions for NMA and ITC belong in the Academy’s dedicated NMA assumptions guide and indirect treatment comparison guide.

9 Governance, registration, amendments and automation

Define who can change the protocol and how automated steps remain auditable. Registration is conditional on the review and registry scope.

HTACG’s July 2026 JCA principles require accountability, human oversight and transparent reporting of AI-assisted evidence-synthesis steps; they do not lower the underlying methodological standard.9

Protocol blueprint

The generated text summarizes the planning architecture. It does not replace a full registered protocol or jurisdiction-specific dossier form.

Complete the relevant modules, then select “Generate protocol blueprint”.

A master evidence universe can serve several PICOs—if the mapping stays explicit

Multi-PICO work creates a common design error: teams either duplicate the entire search for every small variation or, at the opposite extreme, treat several decision questions as though they were one. The safer architecture sits between those extremes. When the disease, intervention and broad evidence universe substantially overlap, one coordinated identification strategy may serve several PICOs. Eligibility mapping, comparator relevance, subgroup definitions and analysis still need to remain PICO-specific. PBAC similarly distinguishes searches needed to identify direct evidence and comparator trials for indirect comparison, while EU JCA operational experience shows that missing evidence for some PICO questions can leave large parts of an assessment scope unanswered.7,8,13,14

Do not interpret this as a rule that all PICOs should share one search. Separate strategies become more defensible when the evidence streams use different study designs and terminology, when the intervention or disease area changes materially, or when an economic/utility question has a different source architecture from the clinical-effectiveness question. The protocol should justify the architecture rather than use a fixed number of searches as a marker of rigor.

Multi-PICO evidence lattice A master evidence universe flows into a study-level evidence map, then branches into three PICO-specific mappings. A separate utility evidence stream enters from the side to show when a distinct search architecture is justified. One evidence universe can feed several decision questions Shared identification does not mean shared eligibility or identical analysis. MASTER IDENTIFICATION clinical databases · registries · regulatory STUDY-LEVEL MAP master Study ID · arms · reports population · outcome · data cut PICO MAPPING same evidence universe different decision filters PICO 1 Population A · Comparator X own eligibility map & analysis PICO 2 Population B · Comparator Y own eligibility map & analysis PICO 3 different line SEPARATE EVIDENCE STREAM Health-state utilities / local resource use different sources · designs · appraisal · outputs Share governance, not necessarily the search.
Figure 2. Multi-PICO evidence lattice. Shared identification can reduce duplicate retrieval when the evidence universe overlaps, while PICO-specific mapping preserves decision relevance. A utility or resource-use stream may require a genuinely different search architecture.

Treat a trial as an evolving evidence object

Study lineage is one of the most useful additions a decision-oriented protocol can make. Cochrane requires review authors to link multiple reports of the same study and to plan how discrepancies across sources will be handled. PBAC goes further operationally by asking for a master list of trials and associated reports. In HTA work, the same study may appear as a registry record, conference abstract, primary paper, CSR, regulatory assessment and later survival update. Counting those records as separate evidence is an obvious error, but silently replacing one with another is also risky.14,15

The protocol should not use a crude hierarchy such as “peer-reviewed article always wins” or “latest source always wins.” Different sources can be strongest for different variables. A later data cut can provide more mature survival while the original CSR may contain fuller safety or protocol information. The safest general rule is variable-specific reconciliation: retain a master study ID, record each source and data-cut date, mark supersession status, document the preferred source for each variable, and preserve unresolved conflicts. This is an Academy synthesis of well-established study-linkage principles rather than a claim that every HTA body mandates an identical hierarchy.

Early EU JCA practice reinforces the point. In the 2026 lurbinectedin JCA, assessors explicitly distinguished different clinical cutoff dates and treated the later prespecified cut as more relevant for several HTA questions because of greater maturity. That is a concrete reason to capture data-cut identity during the SLR rather than reconstruct it after synthesis begins.23

Evidence currency is a governance problem, not a calendar slogan

A review can be complete and still be stale for its decision. The protocol should distinguish at least four dates: search execution, evidence cutoff, analysis/data freeze, and target submission or assessment milestone. They answer different questions. Search execution documents when a source was queried. Evidence cutoff defines which new evidence can enter the current analytical dataset. Data freeze identifies the trial-data maturity used for outcomes. Submission timing determines whether surveillance or a rerun may be necessary before the evidence package is locked.

Do not invent a universal “update within three months” or “six months” rule. HTA agencies use different procedural cutoffs, and a high-velocity oncology evidence base has a different risk profile from a stable utility search. The protocol should instead define material triggers: a new pivotal trial, a new relevant comparator, a revised scope, an abstract-to-full-publication transition, a new data cut, a regulatory change, a safety signal, a delayed submission or a resubmission. Cochrane’s review-update standards demonstrate that currency matters, but their own timing requirements should not be presented as universal HTA rules. If a project is deliberately maintained as a living systematic review, PRISMA-LSR can guide transparent reporting of that living process; it does not create a universal HTA update cadence.19,22

Use proportional search depth for economic inputs

An HTA evidence program can waste substantial effort by treating every model parameter as if it requires a full systematic review. NICE DSU TSD 13 addresses the identification and selection of evidence used to inform model structure and parameters, while Cochrane’s economics guidance explicitly recognizes different levels of economic-evidence incorporation. The practical implication is not a numeric scoring algorithm. It is a transparent decision about search depth based on the decision use of the parameter.3,16

Full evidence stream

Competing evidence could change the decision

Use a systematic stream when important estimates are uncertain, heterogeneous or plausibly decision-changing and no single authoritative source resolves the question.

Targeted systematic search

The parameter needs evidence, but not an entire parallel review

Use a focused strategy when the evidence question is narrow and the intended parameter is secondary or bounded.

Authoritative local source

The value is jurisdiction-defined

Use current tariffs, official prices, coding schedules or national statistics when those are the relevant source. A bibliographic SLR can be less appropriate, not more rigorous.

Worked planning example: an oncology reimbursement evidence program

Suppose a new oncology medicine has a pivotal single active-control trial, but the target payer considers two additional active therapies relevant in later-line practice. The economic model also needs health-state utilities and local resource use. A generic protocol might define the pivotal-trial PICO, search MEDLINE and Embase for the new medicine, and plan meta-analysis “if possible.” That protocol could be publishable and still fail operationally.

A decision-linked protocol would begin by recording the reimbursement population, treatment line and all decision comparators. It would then create a clinical master evidence universe broad enough to identify trials of the new medicine and relevant comparator evidence, while assigning each comparison a stable PICO mapping. The clinical stream would prospectively collect trial arms, comparator identity, baseline characteristics, outcomes, timepoints, switching/subsequent therapy and data-cut/source information. It would mark IPD and aggregate-data availability without assuming that an ITC or NMA will later be valid. Pair 31 and Pair 32 methodology would be applied only after the evidence structure is known.

The utility question would be a separate stream because its eligible study designs, sources and extraction fields differ. The resource-use question might rely partly on targeted literature and partly on authoritative local costing sources. Every record from the pivotal trial would be linked to one master study ID so that a conference readout, journal article and later regulatory data cut do not become three “studies.” The update plan would specify what happens if a new comparator trial or mature survival cut appears before submission. If the payer changes the required comparator, the protocol amendment would identify which searches, PICO mappings, extraction fields and downstream feasibility checks need to be reopened.

The value is the architecture. None of these steps guarantees a favorable reimbursement conclusion. They make the evidence program auditable and reduce the chance that a late analytical requirement reveals that the SLR captured the wrong comparator, wrong data version or insufficient downstream variables.

What this planning resource does not decide

This resource does not replace a complete systematic-review protocol, a search-strategy protocol, a jurisdictional dossier template, a risk-of-bias manual, or an economic model specification. PRISMA-P remains reporting guidance for systematic-review protocols; PRISMA-S covers search reporting; PROSPERO and OSF provide registration infrastructure with different scopes. The builder should sit alongside those requirements rather than pretending to supersede them.17,18,20,21

It also deliberately stops before specialist quantitative judgments. Capturing candidate effect modifiers is different from deciding whether transitivity holds. Recording a common comparator is different from deciding that an indirect comparison is credible. Capturing economic-input evidence is different from choosing a model structure. Those boundaries protect the Academy’s separate methodology pages from becoming keyword-swapped versions of one another and keep this resource focused on a single task: making the SLR protocol usable for a real HTA/HEOR evidence program.

A protocol is decision-ready when it can explain what happens next

The practical test is not whether the protocol has more headings. It is whether the evidence team can trace each major decision requirement to an evidence stream, each PICO to its comparator logic, each study to its underlying record family and data cut, each planned downstream analysis to the variables it will require, and each update or amendment to a defined governance rule. That is the difference between adding “HEOR” to a conventional protocol and designing an evidence program that can survive an HTA decision.

Get every MetaSyn template free, including this one.

Leave your email and I’ll send this resource as an editable Word file and a printable PDF, plus access to the smart online version. You’ll also get every new template as it’s finished. No noise, just the resources.

Need the methodological reasoning behind the protocol?

Read How to Plan a Systematic Literature Review for HEOR and HTA for the decision logic behind multi-PICO planning, evidence streams, study lineage and evidence currency.

Frequently asked questions

Can one protocol cover both clinical effectiveness and utility evidence?

It can coordinate both streams under one evidence program, but they should not be forced into identical eligibility criteria, source lists, appraisal rules or extraction fields. If the methodological workflows differ materially, the protocol should define them as separate streams or linked subprotocols.

Should every HEOR evidence stream be registered in PROSPERO?

No. PROSPERO prospectively registers eligible systematic reviews with health-related outcomes, but not every cost, resource-use, scoping or internal evidence activity fits its scope. Registration should be matched to registry eligibility and project governance; OSF can provide a broader timestamped registration option.

Can eligibility criteria change after the protocol is approved?

Prespecification remains the default. In specific HTA settings where evidence volume cannot be known reliably in advance, a controlled refinement rule can be defensible if its triggers, decision authority and safeguards are defined and the change is documented before result-driven selection can influence the decision. NICE DSU TSD 27 is an example in the HealthTech context.

Should the latest publication automatically replace earlier reports of the same trial?

No. Later evidence may have a more mature data cut for one endpoint while an earlier CSR or regulatory source contains more complete information for another. Link all reports to a master study ID and use a variable-specific reconciliation rule rather than a single publication hierarchy.

Should an NMA be written into the protocol before searching starts?

Not as a guaranteed analysis. The protocol can prespecify that network or indirect-comparison feasibility will be assessed and can capture the fields needed for that assessment. Connectivity, comparability and analytical credibility can only be judged after the evidence is identified.

Does an HTA protocol need a fixed search-update interval?

No single interval applies across HTA jurisdictions. Record search and evidence dates and define update triggers tied to the project, therapeutic area and submission process rather than inventing a universal three-, six- or twelve-month rule.

What should be recorded if AI assists screening or extraction?

At minimum, preserve the task, tool and version, validation process, responsible human oversight and audit trail. If the work supports an EU JCA dossier, current HTACG principles add specific transparency expectations for AI-assisted steps, tool details and prompt records.

References

  1. National Institute for Health and Care Excellence. Single technology appraisal and highly specialised technologies evaluation: company evidence submission user guide (PMG24). Current web guidance, updated through March 2026. NICE.
  2. National Institute for Health and Care Excellence. Appendix B: Identification, selection and synthesis of clinical evidence. In: PMG24. NICE.
  3. Kaltenthaler E, Tappenden P, Paisley S, Squires H. NICE DSU Technical Support Document 13: Identifying, selecting and using evidence to inform the model structure and parameters. NICE Decision Support Unit. NICE DSU TSD index.
  4. NICE Decision Support Unit. Technical Support Document 27: Prioritising studies and outcomes for consideration in NICE HealthTech literature reviews. 2025. NICE DSU.
  5. National Institute for Health and Care Excellence. NICE real-world evidence framework. 2022. NICE.
  6. European Parliament and Council. Regulation (EU) 2021/2282 of 15 December 2021 on health technology assessment and amending Directive 2011/24/EU. Off J Eur Union. 2021. Official Journal / EUR-Lex.
  7. Health Technology Assessment Coordination Group. Guidance on filling in the joint clinical assessment (JCA) dossier template – Medicinal products. 2024. European Commission.
  8. Member State Coordination Group on Health Technology Assessment. Joint Clinical Assessment Summary Report of Tovorafenib, Version 1.0. European Union; 2026. European Commission.
  9. Health Technology Assessment Coordination Group. General principles on the use of Artificial Intelligence in the preparation of dossiers for Joint Clinical Assessments. Adopted 15 July 2026. European Commission.
  10. Canada’s Drug Agency. Pharmaceutical Reviews Update — Issue 61. 30 April 2026. CDA-AMC.
  11. Canada’s Drug Agency. Procedures for Reimbursement Reviews. Current procedures. CDA-AMC.
  12. Institute for Quality and Efficiency in Health Care. General Methods, Version 8.0. 1 July 2026. doi:10.60584/General-Methods_V8.0. IQWiG.
  13. Pharmaceutical Benefits Advisory Committee. Section 2.1: Literature search methods. PBAC Guidelines. Australian Government Department of Health.
  14. Pharmaceutical Benefits Advisory Committee. Appendix 3: Identify relevant trials. PBAC Guidelines. Australian Government Department of Health.
  15. Li T, Higgins JPT, Deeks JJ. Chapter 5: Collecting data. In: Higgins JPT, Thomas J, Chandler J, et al, eds. Cochrane Handbook for Systematic Reviews of Interventions. Version 6.5. Cochrane; 2024. Cochrane.
  16. Aluko P, Graybill E, Craig D, et al. Chapter 20: Economic evidence. In: Higgins JPT, Thomas J, Chandler J, et al, eds. Cochrane Handbook for Systematic Reviews of Interventions. Version 6.5. Cochrane; 2024. Cochrane.
  17. Shamseer L, Moher D, Clarke M, et al. Preferred reporting items for systematic review and meta-analysis protocols (PRISMA-P) 2015: elaboration and explanation. BMJ. 2015;350:g7647. doi:10.1136/bmj.g7647. See also the current PRISMA-P page.
  18. Rethlefsen ML, Kirtley S, Waffenschmidt S, et al. PRISMA-S: an extension to the PRISMA Statement for Reporting Literature Searches in Systematic Reviews. Syst Rev. 2021;10:39. doi:10.1186/s13643-020-01542-z.
  19. Akl EA, Khabsa J, Iannizzi C, et al. Extension of the PRISMA 2020 statement for living systematic reviews (PRISMA-LSR): checklist and explanation. BMJ. 2024;387:e079183. doi:10.1136/bmj-2024-079183.
  20. Centre for Reviews and Dissemination, University of York. PROSPERO: eligibility for inclusion. Current guidance. PROSPERO.
  21. Center for Open Science. OSF Registrations and Preregistrations. Current guidance. OSF.
  22. Cochrane. Chapter IV: Updating a review. In: Cochrane Handbook for Systematic Reviews of Interventions. Current version. Cochrane.
  23. Member State Coordination Group on Health Technology Assessment. Joint Clinical Assessment Report of Lurbinectedin, Version 1.0. European Union; 2026. European Commission.
Methodological scope note. This resource is an Academy planning framework synthesized from current systematic-review methods and HTA requirements. Jurisdiction-specific rules are labeled as such; early EU JCA reports are used as operational examples, not as universal law. TSD 27 applies specifically to NICE HealthTech prioritization and is not presented as permission for unrestricted eligibility changes. The resource does not teach NMA/ITC analysis, economic-model construction, PRO psychometrics or detailed search syntax. Evidence and guidance status were checked through 10 August 2026.