> 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/vendor-introduction-to-snomed-ct/readme.md).

# Vendor Introduction to SNOMED CT

The Vendor Introduction to SNOMED CT provides an informative practical introduction to SNOMED CT focused primarily on the needs of vendors and developers of EHRs and other related applications in healthcare information technology.

It is targeted at people engaged in the development of EHR systems and related services. The document will also be of interest to a broader audience including anyone engaged in designing, developing, procuring, deploying, configuring or managing EHR systems and services.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/1-introduction.md">Introduction</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/introduction/1.-introduction.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/introduction/1.-introduction.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/2-benefits-to-vendors.md">Benefits to Vendors</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/what-is-loinc/2.-what-is-loinc.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/what-is-loinc/2.-what-is-loinc.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/3-introduction-to-snomed-ct.md">Introduction to SNOMED CT</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/clinical-use-case/3.-clinical-use-case.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/clinical-use-case/3.-clinical-use-case.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/4-choosing-an-approach-to-implementation.md">Choosing an approach to Implementation</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/content-development-principles/4.-content-development-principles.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/content-development-principles/4.-content-development-principles.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/5-implementation-strategies-and-considerations.md">Implementation Strategies and Considerations</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/information-models-and-terminology-binding/5.-information-models-and-terminology-binding.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/information-models-and-terminology-binding/5.-information-models-and-terminology-binding.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/6-enhancing-ehr-design-with-snomed-ct.md">Enhancing EHR design with SNOMED CT</a></td><td><a href="https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/technical-application/6.-technical-application.md">https://github.com/SNOMED-Documents/snomed-vendor-guide/blob/main/technical-application/6.-technical-application.md</a></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/7-licensing.md">Licensing</a></td><td></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/8-references.md">Useful References</a></td><td></td></tr><tr><td><a href="/snomed-ct-practical-guides/vendor-introduction-to-snomed-ct/appendix-1-user-experience-of-snomed-ct.md">Appendix 1 - User Experience of SNOMED CT</a></td><td></td></tr></tbody></table>

***

{% hint style="info" %}
© Copyright 2025 International Health Terminology Standards Development Organisation, all rights reserved.

This document is a publication of International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED International owns and maintains SNOMED CT®.

Any modification of this document (including without limitation the removal or modification of this notice) is prohibited without the express written permission of SNOMED International. This document may be subject to updates. Always use the latest version of this document published by SNOMED International. This can be viewed online and downloaded by following the links on the front page or cover of this document.

SNOMED®, SNOMED CT® and IHTSDO® are registered trademarks of International Health Terminology Standards Development Organisation. SNOMED CT® licensing information is available at <http://snomed.org/licensing>. For more information about SNOMED International and SNOMED International Membership, please refer to [http://www.snomed.org](http://www.ihtsdo.org/) or contact us at [info@snomed.org](mailto:info@ihtsdo.org).
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Vendor+Introduction&#x26;entry.670899847=Vendor%20Introduction%20to%20SNOMED%20CT" 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 dynamically 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/vendor-introduction-to-snomed-ct/readme.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 `build a script that syncs our docs to a CMS` 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.