# Inactivate Concept in an Extension

## Inactivate Concept in an Extension

## Purpose

Concepts may be inactivated in an extension for various reasons including:

* The concept is erroneous, obsolete or out of scope
* The concept is ambiguous, and must be replaced with one or more concepts whose meaning is clear
* The concept is redundant, because another concept has the same clinical meaning or definition

Please note that concepts that are promoted from the extension into the International Edition (or a module on which the extension module depends) are **not** inactivated in the extension. For more information on concept promotion, please refer to [Promotion and Demotion](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.4-authoring/5.4.1-general-authoring-principles/5.4.1.1-promotion-and-demotion).

## Principles

### Inactivating Extension Concepts

Concepts in an extension can be inactivated if necessary. This is accomplished by creating a new inactive version of the concept, and new inactive versions of any relationships in which that concept participates. This inactivation process is explained in more detail below.

### Inactivating International Concepts

Concepts which belong to the International Edition (or to a module on which the extension depends) should generally not be inactivated in an extension (please refer to [Management of Inactivated International Concepts within an Extension](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.4-authoring/5.4.1-general-authoring-principles/5.4.1.3-management-of-inactivated-international-concepts-within-an-extension)). Extension producers should submit any requests for inactivation to SNOMED International (or the module owner). In most situations, in which an extension producer needs to exclude specific international concepts in their extension, this should be done by creating a reference set of either the 'included' or 'excluded' concepts. For more information, refer to [Exclude Content](https://app.gitbook.com/s/qOI2v58ZsXOoklmwBOk4/3-requirements-and-use-cases) in the [Practical Guide to Reference Sets](https://app.gitbook.com/o/h8Z6qGxuQrzM9vbx5bPT/s/qOI2v58ZsXOoklmwBOk4/).

Please note that if a situation arises in which an error is detected in the International Edition that causes inference errors in the extension, then this **must** be submitted to SNOMED International for correction. If a correction in the International Edition is not available prior to the release of the extension, then the error may be corrected in the Extension Edition, as long as this is reconciled in the next version of the extension that uses the corrected International Release.

## Process

When inactivating a concept in an extension, key steps include:

* Inactivating the concept
* Inactivating any relationship in which the inactive concept participates
  * This includes any relationship in which the inactive concept is the source concept, the destination concept or the relationship type
* Representing the reasons for inactivation and possible replacements in the appropriate reference sets

Please note that active descriptions should **not** be inactivated when a concept is inactivated. This provides a mechanism to see the terms associated with concepts that have previously been entered into a clinical record, and to support historical queries on data that was captured using a previous version of the terminology.

{% hint style="info" %}
Concepts should NOT be used for data entry once they have been inactivated. However, inactive concepts should be retained to support historical records entered prior to the inactivation.
{% endhint %}

The table below provides a summary of the process to follow when inactivating a concept in an extension.

<table><thead><tr><th width="206.00390625" valign="top">File Type</th><th valign="top">Process</th></tr></thead><tbody><tr><td valign="top"><strong>Concept</strong></td><td valign="top">A new row representing an inactivated version of the concept is added to the Concept file.</td></tr><tr><td valign="top"></td><td valign="top"><p></p><p>The attributes of the new version of the concept are set as follows:</p><ul><li><em>id</em> is set to the conceptId of the concept being inactivated</li><li><em>effectiveTime</em> is set to the date the extension will be published</li><li><em>active</em> is set to '0' to indicate that the concept will become inactive at the time of publication</li><li><em>moduleId</em> is set to identify a module in the extension</li><li><em>definitionStatusId</em> is set to <a href="http://snomed.info/id/900000000000074008">900000000000074008 | Primitive|</a></li></ul></td></tr><tr><td valign="top"><strong>Stated Axiom</strong></td><td valign="top"><p>Inactivating a concept's active relationships involves adding a new row to the OWL axiom reference set file, which inactivates the member of the reference set representing the stated axiom of the concept being inactivated.</p><p>For more information please refer to <a href="../5.4.6-authoring-reference-set-members/5.4.6.3-remove-members-from-a-reference-set">Remove Members from a Reference Set</a>. </p></td></tr><tr><td valign="top"></td><td valign="top"><p></p><p>The attributes of the new version of the concept are set as follows:</p><ul><li><em>id</em> is set to the UUID of the reference set member referencing the concept being inactivated</li><li><em>effectiveTime</em> is set to the date the extension will be published</li><li><em>active</em> is set to '0' to indicate that the reference set member will become inactive at the time of publication</li><li><em>moduleId</em> is set to identify a module in the extension</li><li><em>referencedComponentId</em> is set to the concept identifier of the concept being inactivated</li></ul></td></tr><tr><td valign="top"><strong>Inferred Relationships File</strong></td><td valign="top">An inactive concept does not participate in any active <strong>relationships</strong>. This means that when inactivating a concept, all active relationships, in which the concept was used as the source, destination or type, must be inactivated. As a result, the inactive concept is removed from the subtype hierarchy, and will no longer have any defining relationships. This reinforces the point that an inactive concept should not be used in any new data entry, as it will not be subsumed by any other concept.</td></tr><tr><td valign="top"><p><strong>Concept inactivation indicator reference set</strong></p><p><strong>+</strong></p><p><strong>Historical association reference set</strong></p></td><td valign="top"><p>A new row is added to the <a href="http://snomed.info/id/900000000000489007">| Concept inactivation indicator attribute value reference set|</a> , and the relevant <a href="http://snomed.info/id/900000000000522004">| Historical association reference set|</a> to indicate the reason that the concept was inactivated, and to specify any relevant associations with active concepts (e.g. possible replacements for the inactivated concept).</p><p>When inactivating a concept, it is best practice is to specify the reason that the concept was inactivated in the <a href="http://snomed.info/id/900000000000522004">| Historical association reference set|</a> . Please refer to <a href="https://app.gitbook.com/s/irKbJsZG57nSWZA4GT0M/reference-set-release-file-specification/5.2-reference-set-types/5.2.1-content-reference-sets/5.2.1.3-attribute-value-reference-set/5.2.1.3-attribute-value-reference-set">Attribute Value Reference Set</a> for an example of the <a href="http://snomed.info/id/900000000000489007">| Concept inactivation indicator attribute value reference set|</a> , and to <a href="https://app.gitbook.com/s/irKbJsZG57nSWZA4GT0M/reference-set-release-file-specification/5.1.3-naming-conventions-for-reference-sets#attribute-value-reference-set">Component Inactivation Reference Sets </a>for a list of valid inactivation indicator values.</p><p>Additionally, depending on the inactivation reason, a row should be added to the relevant <a href="http://snomed.info/id/900000000000522004">| Historical association reference set|</a> . This helps to support extension consumers with the change management process, by (for example) specifying possible replacements for the inactivated concept. Please refer to <a href="https://app.gitbook.com/s/irKbJsZG57nSWZA4GT0M/reference-set-release-file-specification/5.2-reference-set-types/5.2.1-content-reference-sets/5.2.1.4-association-reference-set/5.2.5.1-historical-association-reference-sets">Historical Association Reference Sets</a> for a list of historical association reference sets, and an example of the <a href="http://snomed.info/id/900000000000526001">| REPLACED BY association reference set|</a> .</p><p>Please refer to <a href="broken-reference">Managing Component Inactivation</a> for further information.</p></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.4.2.3%20Inactivate%20Concept%20in%20an%20Extension" 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.4-authoring/5.4.2-authoring-concepts/5.4.2.3-inactivate-concept-in-an-extension.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.
