> 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/snomed-ct-practical-guides/snomed-ct-ehr-requirements-guide/4-analytics-and-reporting.md).

# Analytics and Reporting

One of the main drivers for deploying SNOMED CT is to structure data and benefit from the ontology to gain clinical insights into patient data that may otherwise be unavailable in unstructured data. The use of maps of data already coded using local systems to SNOMED CT will help to move towards the rich analysis that SNOMED CT enables, as well as using maps to provide the step from SNOMED CT to national & international classifications for statistical reporting.

1. Use maps from local code systems to SNOMED CT to enable ad hoc querying, reporting and analysis of legacy clinical data or for national or local reporting.
2. Use maps to national and international classifications to enable analysis and reporting of data, including legacy and current data.
3. Applications supporting data reporting, extraction and/or clinical decision support rules shall (where appropriate) use SNOMED CT’s defining relationships in the determination of the correct results or outcomes.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=EHR+Requirements+Guide&#x26;entry.670899847=4.%20Analytics%20and%20Reporting" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-ehr-requirements-guide/4-analytics-and-reporting.md?ask=<question>&goal=<user_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.
