> 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
**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.**
## 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
Stated view of 895470004 |Amputation of bilateral upper limbs (procedure)|
{% hint style="info" %}
Other synonyms may be added if requested, e.g. *L* *eft and right* *X* ; *Bilateral X,* etc.
{% endhint %}
Provide Feedback
---
# 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/procedure/index-1/lateralized-procedure-naming-conventions.md?ask=&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.
.png?alt=media)