> 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-data-analytics-guide/5-preparing-data-for-analytics.md).
# Preparing Data for Analytics
As discussed in the Section about Substrates for Analytics, not all electronic health records represent clinical data using SNOMED CT. However, even when health records use free text or other code systems, it is still possible to use SNOMED CT for analytics over this data if the data is prepared appropriately. For example, Natural Language Processing can be used to encode free text data in SNOMED CT, subsequently enabling more sophisticated analytics to be performed. Similarly, clinical data using other code systems can be mapped into SNOMED CT to provide similar benefits.
In this section, we discuss these alternative ways of preparing clinical data for analytics using SNOMED CT.
Provide Feedback
---
# 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-data-analytics-guide/5-preparing-data-for-analytics.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.