> 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/procedure/index-1/lateralized-procedure-naming-conventions.md).

# Lateralized Procedure Naming Conventions

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

## Procedure concepts with a body structure that has a left/right side

When creating a lateralized procedure concept, two concepts should be created:

1. concept for the left side
2. concept for the right side

When creating a lateralized procedure concept, if a non-lateralized parent does not exist, then it should be created as well. In other words, do not just create the right and left versions, but also create a concept to represent the laterality-agnostic parent.

* For example,
  * When creating *Excision of left mastoid* and *Excision of right mastoid*, also ensure a concept for *Excision of mastoid* exists.

The acceptable naming pattern for procedures with lateralizable body parts:

* FSN: of bilateral (procedure)
* PT: of bilateral
* SYN: of both

Bilateral procedures should be modeled using two relationship groups, one for each lateralized body structure.

* For example,
  * 895470004 | Amputation of bilateral upper limbs (procedure)|

    * FSN: Amputation of bilateral upper limbs (procedure)
    * PT: Amputation of bilateral upper limbs
    * SYN: Amputation of both upper limbs

    <figure><img src="/files/ywqCPkT7ZrVqMgHw8ei7" alt=""><figcaption><p>Stated view of 895470004 |Amputation of bilateral upper limbs (procedure)|</p></figcaption></figure>

{% hint style="info" %}
Other synonyms may be added if requested, e.g. *L* *eft and right* *X* ; *Bilateral X,* etc.
{% 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=Lateralized%20Procedure%20Naming%20Conventions" 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/procedure/index-1/lateralized-procedure-naming-conventions.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.