> 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/allergy-implementation-guide/4-information-model-and-terminology-binding.md).
# Information Model and Terminology Binding
The use of SNOMED CT for recording Allergy, Hypersensitivity, and Intolerance requires the definition of an information model and terminology bindings. This will ensure that the information is captured in a consistent and standardized way, which can be used to facilitate better communication and decision-making between healthcare providers. Furthermore, it will enable the sharing of health information between different systems and facilitate better analysis of health data. By defining an information model and terminology bindings, healthcare organizations can ensure that their data is accurately recorded and can be used in a meaningful way.
The use of HL7® FHIR® with SNOMED CT has gained considerable momentum in recent years, and HL7 FHIR has therefore been selected as the preferred information model in this guide. The following pages will discuss recommended approaches for binding SNOMED to HL7 FHIR for documenting Allergies, Hypersensitivity, and Intolerance in the EHR.
* [FHIR model](/implementation-guides/allergy-implementation-guide/4-information-model-and-terminology-binding/4.1-fhir-model.md)
* [Terminology Bindings](/implementation-guides/allergy-implementation-guide/4-information-model-and-terminology-binding/4.2-terminology-bindings.md)
* [Examples](/implementation-guides/allergy-implementation-guide/4-information-model-and-terminology-binding/4.3-examples.md)
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/allergy-implementation-guide/4-information-model-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.