> 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/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/malformation-deformity-anomaly.md).

# Malformation, deformation, anomaly

<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>

The word *anomaly* is, by itself, ambiguous as it may mean either a structural or functional abnormality, depending on the body structure to which it is applied. Concepts using the term *anomaly* must be evaluated to determine whether it represents a structural or functional abnormality. Using the term "anomaly" in new concept FSNs is not allowed. The terms "structural abnormality" should be used when it is unclear whether the morphology results from malformation or deformation.

A *deformity* is a structural abnormality that is due to an extrinsic physical force. Newly created concepts representing a deformity should be considered disorders.

*A malformation* is a structural abnormality that results from intrinsically disordered development.

* For example,
  * *Congenital anomaly of* is currently modeled as a structural abnormality but is not the same as *C* *ongenital malformation* (structural abnormality due to intrinsically disordered development present at birth). Therefore, it can be regarded as having the more general meaning of *structural abnormality present at birth*.

When referring to a broad term to denote an intrinsic structural abnormality (e.g., Structural abnormality of fetal bladder) and plan to include 49755003 |Morphologically abnormal structure (morphologic abnormality)| in the model, use the pattern *Malformation of fetal X* or *Congenital malformation of X*.

{% hint style="success" %}
**See other related section in the guide**

* Genetic, developmental, congenital, and physical origin
* Acquired abnormality of congenital anomaly
* Congenital
  {% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Malformation%2C%20deformation%2C%20anomaly" 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/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/clinical-finding-and-disorder/clinical-finding-and-disorder-modeling/specific-clinical-finding-and-disorder-modeling/malformation-deformity-anomaly.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.
