> 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/6-technical-application/6.3-context-representation-transformations.md).

# Context Representation Transformations

In today's interconnected digital ecosystem, the seamless exchange of information between diverse systems is more critical than ever. A fundamental obstacle to achieving true interoperability lies in how different systems represent context information about concepts. Some systems embed this context directly within the terminology, using codes with rich, nuanced meanings. Others represent context through their information models, structuring data to convey context via relationships and attributes. This disparity creates a landscape where data exchanged between systems may lose its intended meaning unless carefully transformed and interpreted.

This chapter focuses on the strategies and methodologies for implementing transformations between these heterogeneous models. We will delve into the technical challenges of mapping context from terminologies to information models and explore practical solutions to bridge these differences. By examining real-world scenarios and leveraging interoperability standards, we aim to equip you with the knowledge and tools necessary to ensure that context is preserved and accurately conveyed during data exchange. Understanding these transformation processes is essential for developers, architects, and stakeholders striving to enhance interoperability and achieve consistent, reliable communication across varied systems.

**Example of a transformation from a "Situation with explicit context" concept to a FHIR FamilyMemberHistory Resource information model**

{% tabs %}
{% tab title="Pre-transformation: SNOMED CT Concept / Expression" %}

<figure><img src="/files/F2c4nMZ4YKGinL79eAvW" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Post-transformation: FHIR Resource" %}

<figure><img src="/files/lPSNciKkNsZbZacKCQSu" alt=""><figcaption><p>Figure 6.3-1:</p></figcaption></figure>
{% endtab %}
{% endtabs %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Context+Representation+Guide&#x26;entry.670899847=Context%20Representation%20Transformations" 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/6-technical-application/6.3-context-representation-transformations.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.