> 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/context-representation-implementation-guide/2-terminology-and-information-models-in-healthcare.md).

# Terminology and Information Models in Healthcare

Efficient healthcare data management relies on two fundamental components: terminology and information models. Although distinct in their functions, these elements work together to organize and structure healthcare data, enabling seamless communication, decision-making, and interoperability across healthcare systems.

## Terminology

Terminologies, such as SNOMED CT and other classifications, serve as standardized vocabularies for representing medical concepts and entities. They excel at answering questions related to "What, how, and why?" by precisely defining and categorizing types (classes) of diseases, symptoms, signs, procedures, body structures, morphologies, substances, drugs, devices, organisms, and objects. By providing a common language for healthcare professionals, terminologies ensure semantic consistency and support accurate documentation and retrieval of patient information.

## Information Models

Information models, such as HL7 FHIR and openEHR, provide the structural framework for organizing and representing healthcare data. They focus on addressing questions related to "Who, when, and where?" by capturing temporal aspects (dates, times, durations), quantities, textual information, and about specific individual instances of people, organizations, and places involved in healthcare processes. Information models define the relationships, constraints, and attributes of data entities, enabling interoperability, data exchange, and integration across diverse healthcare systems and settings.

## Separation and Overlap

While terminology and information models serve distinct purposes, there is significant overlap in their functionalities, particularly in the representation of clinical situations and contexts. Some terminologies like SNOMED CT and many information models capture clinical statuses, such as the presence, absence, or uncertainty of medical conditions, as well as document family history, past medical history, and the status of requested, planned, or completed procedures.

However, managing the complexity of overlapping data representations can present challenges. Inconsistent mapping between terminologies and information models, variations in data interpretation, and discrepancies in data capture practices can lead to semantic interoperability issues and hinder the seamless exchange and integration of healthcare data.

Addressing these challenges through standardized approaches, semantic mapping, and interoperability initiatives is essential for healthcare organizations to ensure interoperability and effectively leverage the full potential of healthcare data.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Context+Representation+Guide&#x26;entry.670899847=Terminology%20and%20Information%20Models%20in%20Healthcare" 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/implementation-guides/context-representation-implementation-guide/2-terminology-and-information-models-in-healthcare.md?ask=<question>&goal=<endgoal>
```

`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.