# Creating new morphologies

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

When considering the creation of a new morphological abnormality concept, consider the following:

* When the name of a potentially new morphology is the same as the disease, creation of that new morphologic abnormality concept may not be beneficial since it would not be very morphologically descriptive.
* Determine if there is benefit in creating a new morphology for a very small number of rarely used leaf nodes. If the new morphology is needed to differentiate two non-leaf concepts, that would be sufficient to create the new morphology. Otherwise, use the nearest existing morphologic abnormality.
* Including a body site in a morphological abnormality concept is forbidden unless there is a clear modeling and pathological need.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Creating%20new%20morphologies" class="button primary">Provide Feedback</a>


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/education/snomed-ct-education-editorial-guide/readme/authoring/domain-specific-modeling/body-structure/index-2/creating-new-morphologies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.