# Linkage Concept Hierarchy

## Linkage Concept

<table data-header-hidden><thead><tr><th width="240.1796875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/106237007">106237007 | Linkage concept|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">This concept is the supertype parent or ancestor of <a href="http://snomed.info/id/410662002">410662002 | Concept model attribute|</a> , <a href="http://snomed.info/id/416698001">416698001 | Link assertion|</a> , etc.</td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>No new subtype children may be added in an extension</p><p>See tables below for concept addition rules for the descendants of existing subtype children.</p></td></tr></tbody></table>

## Concept Model Attributes

<table data-header-hidden><thead><tr><th width="249.4375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/410662002">410662002 | Concept model attribute|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">These concepts provide the values for Relationship.typeId and represent the type of a defining relationship.</td></tr><tr><td valign="top"><strong>Examples</strong></td><td valign="top"><p></p><ul><li><a href="http://snomed.info/id/260686004">260686004 | Method|</a>  </li><li><a href="http://snomed.info/id/260870009">260870009 | Priority|</a>  </li><li><a href="http://snomed.info/id/363704007">363704007 | Procedure site|</a></li></ul></td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top">Additional attributes may be added in an extension, where required to support extensions to the SNOMED CT concept model.</td></tr><tr><td valign="top"><strong>Concept Addition Uses Cases</strong></td><td valign="top">Extending the SNOMED CT concept model to allow sufficient definitions to be applied to concepts that are not sufficiently defined in the International Edition.</td></tr><tr><td valign="top"><strong>Additional Notes</strong></td><td valign="top">Any attributes created in extensions need to be carefully managed and documented. Extension attributes may also need to be revised or inactivated to align with future changes to the concept model in the International Edition.</td></tr></tbody></table>

## Link Assertions

<table data-header-hidden><thead><tr><th width="258.15234375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/416698001">416698001 | Link assertion|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">These concepts represent clinical assertions about relationships between instances of clinical statement in an EHR. For example, they may assert that a particular symptom is caused by something.</td></tr><tr><td valign="top"><strong>International Edition Examples</strong></td><td valign="top"><p></p><ul><li><a href="http://snomed.info/id/417151001">417151001 | Has explanation|</a></li><li><a href="http://snomed.info/id/416271009">416271009 | Has problem member|</a>  </li><li><a href="http://snomed.info/id/416586004">416586004 | Has problem name|</a>  </li><li><a href="http://snomed.info/id/416083004">416083004 | Has reason|</a>  </li><li><a href="http://snomed.info/id/417569004">417569004 | Has support|</a>  </li><li><a href="http://snomed.info/id/416872009">416872009 | Is etiology for|</a>  </li><li><a href="http://snomed.info/id/417318003">417318003 | Is manifestation of|</a>  </li></ul></td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top">Additional subtype children may be added in an extension. However, it is recommended that proposed additions be submitted to the International Edition, unless they are highly specific.</td></tr><tr><td valign="top"><strong>Concept Addition Uses Cases</strong></td><td valign="top">Requirements to support additional types of assertion in clinical records</td></tr></tbody></table>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=5.3.2.2.3%20Linkage%20Concept%20Hierarchy" 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/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.3-assessing-requests/5.3.2-constraints-on-concept-requests/5.3.2.2-model-metadata-concept-hierarchies/5.3.2.2.3-linkage-concept-hierarchy.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.
