> For the complete documentation index, see [llms.txt](https://docs.snomed.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snomed.org/implementation-guides/cancer-synoptic-reporting-implementation-guide/2-use-cases.md).

# Use Cases

Cancer synoptic reporting plays a pivotal role in delivering not only clinical advantages but also an array of benefits that extend to areas such as interoperability, surveillance, quality assurance, and research. This structured and standardized approach to documenting cancer-related information brings forth a harmonized approach that fosters seamless data exchange, enhances monitoring capabilities, ensures high-quality care standards, and contributes to the advancement of medical research.

In the subsequent pages, a range of general and clinical use cases will be outlined, and two detailed use cases will be presented to illustrate the use of cancer synoptic reports.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Cancer+Synoptic+IG&#x26;entry.670899847=Use%20Cases" class="button primary">Provide Feedback</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/implementation-guides/cancer-synoptic-reporting-implementation-guide/2-use-cases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.