> 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/review-workflow/synthesis/navigate-synthesis-outputs/critical-appraisal-outputs.md). # Critical Appraisal Outputs Learn how to navigate the critical appraisal outputs in Synthesis. Critical Appraisal Outputs visualize risk of bias across included studies and are automatically generated after Critical Appraisal is completed. Looking to run or configure the underlying appraisal rather than view its output? See [Critical Appraisal](/review-workflow/critical-appraisal.md) instead. ### The Two Visuals * **Domain Distribution** — shows how included studies are distributed across the specific quality domains being assessed (for example, how studies were randomized, or whether outcome assessors were blinded).

Domain Distribution chart showing the number of included studies at each critical appraisal rating for every assessed domain. — Domain Distribution shows how included studies are rated across each assessed quality domain.

* **Traffic Light diagram** — shows each study's rating per domain at a glance, using the familiar red/amber/green convention: green (low concern), amber (some concerns), and red (high concern).

Traffic Light diagram showing each included study's critical appraisal rating for every assessed domain. — Traffic Light diagram shows each study's rating across the assessed quality domains.

Both visuals are found on the Synthesis page, at the bottom of the Contributors column. ### Filtering Like other automatically generated Synthesis outputs, these visuals can be narrowed to a specific subset of studies through **Settings** — see [Filters on Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/filters-on-synthesis.md), including the **Critical Appraisal (Risk)** filter specifically. ### Exporting the Underlying Data The visuals summarize the appraisal at a glance; if you need the full per-study, per-domain data as a spreadsheet, that's available to the review's admin through [Download from Inspector](/review-workflow/study-inspector/download-from-inspector.md). ### FAQs

Why don't I see these visuals on this review's Synthesis page?

They only appear once critical appraisal has been completed for at least some included studies — if you expect to see them and don't, the reviewer may not have reached this step yet.

I'm not familiar with "risk of bias." What does that mean?

It's a structured way of asking "how much could this study's design or conduct have skewed its results?" — for example, whether patients were randomly assigned to treatments, or whether the people measuring outcomes knew which treatment each patient received. Lower risk means the finding is more likely to reflect a true effect rather than a quirk of how the study was run.

### Next Steps


Critical Appraisal	Configure and complete appraisal.	Critical Appraisal
Filters on Synthesis	Filter the studies shown in these visuals.	Filters on Synthesis
Download from Inspector	Export per-study appraisal data.	Download from Inspector

--- # 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/review-workflow/synthesis/navigate-synthesis-outputs/critical-appraisal-outputs.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.