> 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.md).
# Information Models and Terminology Binding
This chapter delves into two crucial aspects of cancer synoptic reporting with SNOMED CT: information models and terminology bindings.
Information models serve as the framework for organizing cancer data elements, guaranteeing consistency and interoperability across various systems.
Terminology bindings forge the essential connection between these data elements and SNOMED CT concepts, ensuring uniform representation and exchange.
The chapter provides practical insights into designing the general cancer report structure, including sample forms to demonstrate cancer synoptic reporting protocols.
Additionally, detailed explanations of SNOMED CT bindings are provided, highlighting their significance in seamlessly implementing standardized cancer data capture and exchange mechanisms.
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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.snomed.org/implementation-guides/cancer-synoptic-reporting-implementation-guide/4-information-models-and-terminology-binding.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.