> 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/snomed-ct-specifications/snomed-ct-compositional-grammar-specification/implementation-guidance/7.6-exchanging.md).

# Exchanging

There are a number of alternative techniques that may be used when exchanging SNOMED CT expressions in messages. These include:

* Placing the full SNOMED CT compositional grammar expression in the relevant *code* field of the message.
  * For example, the HL7 version 3 CD data type (Release 2) allows the 'code' property to include SNOMED CT expressions (see [HL7 TermInfo guide](http://wiki.hl7.org/index.php?title=File:V3_IG_SNOMED_R1_D5_2014JAN.docx)).
* Using an alternative structure for representation of the logical structure of an expression.
  * For example an OWL serialization.
* Placing a unique expression identifier in the relevant *code* field of the message
  * This approach requires the use of a shared expression repository enabling the recipient system to look up and resolve this identified to the relevant expression.
* Decomposing the expression into separate codes that can be placed in different fields within the message structure.
  * This approach assumes alignment between the message structure and the relevant parts of the SNOMED CT concept model.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Compositional-Grammar-Specification&#x26;entry.670899847=Exchanging" 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/snomed-ct-specifications/snomed-ct-compositional-grammar-specification/implementation-guidance/7.6-exchanging.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.
