TECH-VER (Technical Verification Checklist)
TECH-VER is a checklist designed to help reviewers check that a health economic model has been built correctly in software. It ensures the computer code accurately reflects the intended model design and helps catch technical errors that could affect results.
At a glance
Use when
Verifying technical accuracy of health economic models during peer review, regulatory submission, internal quality assurance, or training new modelers
Avoid when
Model documentation or code is unavailable or incomplete; when only high-level validation (not technical verification) is needed
Inputs
Executable model, input data sources, detailed documentation (e.g., technical report or scientific paper), conceptual model description
Outputs
Documented verification report identifying implementation errors, inconsistencies, or confirmation of technical correctness
How it works
TECH-VER is a structured, five-domain checklist for verifying the technical implementation of health economic decision analytical models. Domains include: (1) input calculations, (2) event-state (patient flow) calculations, (3) result calculations, (4) uncertainty analysis calculations, and (5) other overall checks (e.g., validity, interface). It supports a hierarchical verification process: black-box testing (checking outputs against expectations), white-box testing (reviewing code logic), and model replication (parallel programming), recommended sequentially when prior steps fail. Developed through literature review and iterative testing across diverse models, it promotes transparency, credibility, and efficiency in model review. The checklist is intended for use by independent reviewers or developers and is designed as an open-source, living document.
- HTA domains
- Clinical Effectiveness, Costs & Economic Evaluation, Organisational aspects
- Assumptions
- The model is transparent and well-documented; a reviewer has sufficient access and technical expertise; verification can be conducted independently
- Strengths
- Comprehensive coverage of key model components,Structured, hierarchical approach reduces verification time,Promotes transparency and reproducibility,Applicable across different modeling software and development contexts,Supports both external review and internal quality control/training
- Limitations
- Requires access to source code, inputs, and detailed documentation,Dependent on reviewer expertise for white-box and replication testing,May be time-intensive if black-box tests fail and deeper testing is needed,Not a substitute for conceptual model validation
- Also known as
- TECHnical VERification Checklist
Questions this answers
- › Is the health economic model implemented correctly in the software?
- › Does the programmed model accurately reflect the conceptual model?
- › Are input data and calculations correctly programmed?
- › Are patient flows and event probabilities accurately computed?
- › Are results and uncertainty analyses correctly derived?
- › How can model verification be conducted efficiently and transparently?
References & sources
Similar by meaning
Beta record. Generated from the primary source via AI extraction and independent audit, pending final human review.