# Shunt Naming and Modeling

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

## Naming

<table data-header-hidden><thead><tr><th width="138.38836669921875"></th><th></th></tr></thead><tbody><tr><td>FSN</td><td><p>Use the following naming pattern for the FSN; align terming and case sensitivity with the FSN for the concepts selected as the attribute values, excluding the semantic tag.</p><p>[compositional material] [body structure] shunt (physical object)</p><ul><li><p>For example,</p><ul><li>Ventricular shunt (physical object)</li><li>Pleuroperitoneal shunt (physical object)</li></ul></li></ul></td></tr><tr><td>Preferred Term</td><td><p>Use the following naming pattern for the PT; align terming and case sensitivity with the PT for the concept that is selected as the attribute value.</p><p>[compositional material] [body structure] shunt</p><ul><li><p>For example,</p><ul><li>Ventricular shunt</li><li>Pleuroperitoneal shunt</li></ul></li></ul></td></tr><tr><td>Synonym</td><td>Synonyms are not generally added for concepts in this hierarchy.</td></tr></tbody></table>

## Modeling

<table data-header-hidden><thead><tr><th width="323.4271240234375"></th><th></th></tr></thead><tbody><tr><td>Stated parent concept(s)</td><td><p>257351008 |Shunt (physical object)|</p><p>Additional parent, if applicable:</p><ul><li>258166002 |Custom made implant (physical object)</li></ul></td></tr><tr><td>Semantic tag</td><td>(physical object)</td></tr><tr><td>Attribute:Has device intended site</td><td><ul><li>Note this attribute is used to model the proximal site of the shunt only.</li><li><p>Range: &#x3C;&#x3C;123037004 |Body structure (body structure)|</p><ul><li>NOTE: While the MRCM allowed range includes the top-level concept, 123037004 |Body structure (body structure)|, only the descendants should be used in modeling shunt concepts.</li></ul></li><li>Cardinality: 0..1</li></ul></td></tr><tr><td>Attribute: Has compositional material</td><td><ul><li><p>Range: &#x3C;&#x3C;105590001 |Substance (substance)|</p><ul><li>NOTE: While the MRCM allowed range includes the top-level concept, 105590001 |Substance (substance)|, only the descendants should be used in modeling shunt concepts.</li></ul></li><li>Cardinality: 0..*</li></ul></td></tr></tbody></table>

## Exemplars

The following illustrates the **stated** view for 258593008 |Ventricular shunt (physical object)|:

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-434e0ac5a0b0a7a1652937d5e2b870cb954fda67%2Fimage%20(366).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://github.com/SNOMED-Documents/snomed-editorial-guide/blob/main/authoring/physical-object/images/174691266.png" alt=""><figcaption></figcaption></figure>

The following illustrates the **inferred** view for 258593008 |Ventricular shunt (physical object)|:

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-4e9f3ba0f128bcbd7b4585cc8d46b9f13d4b007d%2Fimage%20(367).png?alt=media" alt=""><figcaption></figcaption></figure>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Shunt%20Naming%20and%20Modeling" 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/physical-object/physical-object-naming-and-modeling-conventions/shunt-naming-and-modeling.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.