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

# Interoperability

The final important aspect of SNOMED CT implementations is how interoperability is implemented. SNOMED CT is a very powerful tool to ensure the safe, unambiguous transfer of patient data between organizations and the use of SNOMED CT concept identifiers is at the foundation of this.

1. Use SNOMED CT concept identifiers and/or SNOMED CT expressions to populate SNOMED CT coded data elements for all relevant message exchanges.
2. Use SNOMED CT to share data, based on national/local data standards.
3. The system shall have the capacity to take in mappings to other terminologies/classifications where available such as ICD-10, ICPC2, LOINC, Orphanet codes, and make the mappings available in the relevant contexts. This may include on-screen display and inclusion in generated documents, reports and data extracts.

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