> 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/6-storage.md).

# Storage

How SNOMED CT is used and stored against patient records is another factor that can drive a successful implementation or not. The use of the SNOMED CT concept identifier is a mandatory requirement and for all the points in this section, it is important that implementations are quality assured and prove that these requirements are met.

1. Must store SNOMED CT concept identifiers in the health records
2. Store the SNOMED CT concept identifier (or SNOMED CT expression) together with the term selected by the user in the EHR for SNOMED CT coded data element.
3. Ensure that the context of each SNOMED CT concept identifier or expression is clearly represented in either the information structure or the terminology (but not both).
4. Ensure that all inactivated concepts, descriptions and relationships remain available to support querying over historical clinical data.

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