> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/best-practices/best-practices-by-review-type/evaluations-for-hta-submissions.md).
# Evaluations for HTA submissions
Learn about the best practices for conducting clinical effectiveness, epidemiological, and economic evaluations.
Here the best practices in conducting reviews for HTA submissions are covered.
For step-by-step instructions in **Nested Knowledge**, see the [HTA assessments](/guides/guidance-by-review-type/evaluations-for-hta-submission.md) guide. The guidance below applies regardless of the software you use, and regardless of which HTA body you're submitting to.
### Confirm Your Target Body's Specific Requirements Before You Start
HTA bodies (for example, NICE, ICER, G-BA) differ in required methodology, reporting format, and which comparators or perspectives they expect. Confirm your specific requirements before designing your search or extraction, since discovering a mismatch after screening means redoing work.
### Treat The Three Components As Related, Not Identical
Since clinical effectiveness, economic evaluation, and epidemiology each answer a different question and draw on different literature, plan each component's methodology separately.
### Keep Economic Model Inputs Traceable To Their Sources
Every cost, utility, or probability input in an economic model needs to be traceable to a specific cited source. Build your extraction hierarchy to preserve that traceability rather than summarizing inputs in a way that loses the link back to the original study.
### Address Indirect Comparisons Explicitly
Where a head-to-head trial against your comparator doesn't exist, state that gap explicitly and address it methodologically (for example, with a network meta-analysis) rather than presenting the closest available comparison as equivalent.
### Document Epidemiological Data Sources As Carefully As Trial Data
Registry and surveillance data often carry different limitations than published studies (reporting lag, population coverage) so document those limitations for your epidemiology component the same way you'd document a trial's risk of bias.
### Next Steps
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nested-knowledge.com/best-practices/best-practices-by-review-type/evaluations-for-hta-submissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.