> 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/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-2/division-lysis-transection-bisection.md).

# Division, lysis, transection, bisection

### Division and lysis <a href="#division-and-lysis" id="division-and-lysis"></a>

*Division - action (qualifier value)* is a subtype of Incision - action (qualifier value). This does not mean that all procedures, that include the word *division*, should necessarily be modeled with Method (attribute) of Division - action (qualifier value), like those where the division is accomplished using *blunt dissection*, not incision.

* For example,
  * *Division of adhesion* concepts, like 173269002 |Division of adhesions of lip (procedure)|, should be modeled the same as *lysis of adhesion* concept&#x73;*,* like 45602008 |Lysis of adhesions of peritoneum (procedure)|

Both use *Dissection - action (qualifier value)*. Adhesions are *broken down* by blunt dissection, often without incising them. This does not exclude procedures that may also involve division by incision.

The preferred name of *division of adhesions* concepts can be changed to *lysis of adhesions* for consistency. The use of *lysis of adhesions* also helps with correct modeling and avoidance of interpreting *divisions* as necessarily being kinds of incision.

### Transection and bisection <a href="#transection-and-bisection" id="transection-and-bisection"></a>

*Transection* is defined as a division across the longitudinal axis of a structure by cutting. *Bisection* is defined as division into two parts by cutting. Transection - action (qualifier value) is a subtype of Bisection - action (qualifier value), which is a subtype of Division - action (qualifier value) and Incision - action (qualifier value).

* For example,
  * 53176004 |Transection of muscle of eye (procedure)|
  * 60158005 |Bilateral bisection of ovary (procedure)|

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Division%2C%20lysis%2C%20transection%2C%20bisection" 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/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/procedure/index-2/division-lysis-transection-bisection.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.