> 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/3-use-case.md).

# Use Case

The following use cases highlight how addressing context representation challenges can enhance data capture, interoperability, and analytics in healthcare.

## Use Case 1: Designing a Data Model for Clinical Data Capture

Establishing a well-structured data model with appropriate terminology bindings ensures accurate clinical data recording and meaningful documentation. This supports patient care and enables long-term health data analysis.

## Use Case 2: Seamless Data Exchange Across Systems

Standardizing context representation allows systems with different approaches—such as terminology-driven or model-based contexts—to seamlessly exchange data. This improves interoperability and ensures comprehensive patient information sharing.

## Use Case 3: Accurate Data Interpretation for Analytics

Consistent context representation enables accurate integration and interpretation of data across systems. This supports reliable analytics, research, and population health management by ensuring semantic consistency.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Context+Representation+Guide&#x26;entry.670899847=3.%20Use%20Case" 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 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/context-representation-implementation-guide/3-use-case.md?ask=<question>&goal=<user_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.
