> 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/implementation-guides/cancer-synoptic-reporting-implementation-guide/4-information-models-and-terminology-binding/4.3-snomed-ct-bindings.md).
# SNOMED CT Bindings
Terminology binding of cancer pathology reporting protocols is specific to each particular malignant neoplasm type as defined by the publishing entity, such as the College of American Pathologists or the International Collaboration on Cancer Reporting.
Association of SNOMED CT concept with published data elements entails understanding the protocol content, the terminology definitions, and any conditional logic based on "nesting" of questions, that is, the necessary observable entity/observation data to record.
Optimally, the publishing bodies of the reporting protocols will incorporate and distribute SNOMED CT - Data element bindings as part of their documentation or software functionality. Given their domain expertise and the stakeholders they represent, these organizations are well-positioned to be qualified stewards of content and domain-specific distribution of encoded reporting protocols.
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/implementation-guides/cancer-synoptic-reporting-implementation-guide/4-information-models-and-terminology-binding/4.3-snomed-ct-bindings.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.