> 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/8-references.md).
# References
The Vendor Introduction is intended as a useful starting point for Vendors. More detailed information and a range of informative documents and training materials can be accessed from the SNOMED International web site [www.snomed.org](http://www.snomed.org) and the [SNOMED CT Document Library](https://docs.snomed.org/).
The table below provides links to many of the key resources for further learning about SNOMED CT.
| **Topic** | **Key reference** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **General information about SNOMED CT** Materials include what is SNOMED CT?, value and benefits, and information about licensing, software and tools, other SNOMED products.Also focused sites for vendors, members and implementers. |
|
| **SNOMED CT Document Library** | |
| Access to a wide range of documents about SNOMED CT | [http://snomed.org/doc](https://docs.snomed.org/) |
| **SNOMED CT Browsers** | |
| The SNOMED International Browser and a list of other tools for exploring SNOMED CT content | |
| **SNOMED CT in Action** | |
| Examples of how SNOMED CT is being used around the world. | |
| **SNOMED CT Starter Guide** | |
| A general purpose introduction to SNOMED CT which complements this guide. | [http://snomed.org/starterguide](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-starter-guide/) |
| **SNOMED CT E-Learning Server** | |
| Access to a growing range of online training resources about SNOMED CT. Including formal courses and open-access materials. | [http://snomed.org/elearning](https://www.snomed.org/education) |
| **SNOMED CT Expo Presentations** | |
| Presentation materials | |
| **About SNOMED International** | |
| More information about the organization that owns and maintains 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/vendor-introduction-to-snomed-ct/8-references.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.