> 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-specifications/snomed-ct-to-icd-10-map-specification/map-structure/7-data-structure-and-distribution-format.md).

# Data Structure and Distribution Format

Since January 2013, the SNOMED CT International Edition release package includes a mapping table from clinical concepts in SNOMED CT to codes listed in ICD-10. SNOMED CT to ICD-10 maps are represented as members of a single reference set called the ICD-10 Extended Reference Set. This reference set contains all Map member data.

Incremental changes to the ICD-10 will be documented employing the versioning mechanism supported by the standard SNOMED CT Release File Specification.

SNOMED International welcomes the opportunity to work with organizations or institutions who are interested in undertaking usage validation of the SNOMED CT to ICD-10 Map. Please contact <info@snomed.org> for more information.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=ICD-10+Map+Specification&#x26;entry.670899847=Data%20Structure%20and%20Distribution%20Format" 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-specifications/snomed-ct-to-icd-10-map-specification/map-structure/7-data-structure-and-distribution-format.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.