> 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/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/body-structure/index-2/fracture.md).

# Fracture

<mark style="color:$danger;">**This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.**</mark>

Fractures should be agnostic as to whether they are pathologic or not, unless specified in the FSN or could only be caused by trauma (e.g. open fractures). Although most fractures are traumatic, there are some pathological fractures. Based on its FSN and text definition, if the word *pathological* is present, use Pathologic fracture (morphologic abnormality).

#### Example: Modeling Traumatic vs. Pathological Fractures

| Concept                                                           | Finding site                      | Associated morphology                         |
| ----------------------------------------------------------------- | --------------------------------- | --------------------------------------------- |
| 21351003 \|Fracture of phalanx of foot (disorder)\|               | Bone structure of phalanx of foot | Fracture (morphologic abnormality)            |
| 704168008 \|Pathological fracture of phalanx of foot (disorder)\| | Bone structure of phalanx of foot | Pathologic fracture (morphologic abnormality) |

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Fracture" 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/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/body-structure/index-2/fracture.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.