> 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-diagramming-specification/6-examples.md).

# Examples

This section shows some example uses, diagramming existing content from SNOMED CT.

<figure><img src="https://4166631172-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM5YwUfVkVdFLDT6IXbBg%2Fuploads%2Fgit-blob-e9078ec69b65a5517256b089168483f226dbda80%2F29950859.png?alt=media" alt=""><figcaption><p><strong>Figure 25–Definition of</strong> [ 12676007 | Fracture of radius|](http://snomed.info/id/12676007 "12676007 | Fracture of radius |") <strong>in distribution normal form including identifiers</strong></p></figcaption></figure>

The concept definition shown in Figure 25 shows that the concept [`12676007 | Fracture of radius|`](http://snomed.info/id/12676007) is equivalent to the following distribution normal form expression -

[`429353004 |Injury of radius|`](http://snomed.info/id/429353004) `+` [`65966004 |Fracture of forearm|`](http://snomed.info/id/65966004) `:`\
`{` [`116676008 |Associated morphology|`](http://snomed.info/id/116676008) `=` [`72704001 |Fracture|`](http://snomed.info/id/72704001) `,`\
[`363698007 |Finding site|`](http://snomed.info/id/363698007) `=` [`62413002 |Bone structure of radius|`](http://snomed.info/id/62413002) `}`

<figure><img src="https://4166631172-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM5YwUfVkVdFLDT6IXbBg%2Fuploads%2Fgit-blob-92f2d0855073670f6b3df902ea6596a803d973d8%2F29950860.png?alt=media" alt=""><figcaption><p><strong>Figure 26–Definition of</strong> [ 12676007 | Fracture of radius|](http://snomed.info/id/12676007 "12676007 | Fracture of radius |") <strong>in long normal form without identifiers</strong></p></figcaption></figure>

Figure 26 shows the definition of `| 12676007 | Fracture of radius |` again, however, this time in long normal form and without identifiers. The expression on the right had side of the diagram equates to the text expression - `| 64572001 | Disease | : {116676008 | Associated morphology | = 72704001 | Fracture |, 363698007 | Finding site | = 62413002 | Bone structure of radius |}`

***

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Diagramming+Specification&#x26;entry.670899847=Examples" 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-diagramming-specification/6-examples.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.
