# Inactivate Relationship in an Extension ## Purpose There are a variety of reasons for inactivating a relationship in an extension, including: * An extension concept has been inactivated, which requires all relationships that it participates in to be inactivated * To correct errors in the definition of a concept * To remove any redundant [| is a|](http://snomed.info/id/116680003) relationships, generated when classifying the extension edition * To remove any 'temporary' relationships that were added to correct errors in the International Edition that have since been fixed in the International release ## Principles ### Inactivating Extension Relationships Relationships in an extension can be inactivated if required. This is done by creating a new version of the extension relationship with a more recent *effectiveTime* and the *active* attribute set to '0' (for 'inactive'). ### Inactivating Relationships from the International Release Relationships which belong to the International Edition (or to a module on which the extension depends) should *not* be inactivated in an extension. When relationships from the International Edition need to be excluded, this can be done by creating a simple reference set of either 'included' or 'excluded' relationships. The only situations in which an extension producer may inactivate a relationship specified in the international edition (or a module on which the extension depends) are: * Where an international [| is a|](http://snomed.info/id/116680003) relationship becomes redundant after classification is performed. For more information, refer to [Add Concept in an Extension](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.1-add-concept-in-an-extension) and [Classifying an Edition](https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.6-distribution/5.6.1-preparing-for-distribution/5.6.1.1-classifying-an-edition). * Where there exists an erroneous relationship in the International Edition (or in a module on which the extension depends), that may cause incorrect inferences in the extension edition. If this occurs, the error may need to be temporarily corrected in the extension edition. In addition, SNOMED International must be notified of the error so that it can be permanently corrected in the international edition. In these situations, the relationship from the International Edition (or module on which the extension depends) is inactivated by creating a new version of the relationship in the extension module with a more recent *effectiveTime* and the *active* attribute set of '0' (for 'inactive'). ## Process The table below provides a summary of the process to follow when inactivating a relationship in an extension.
File TypeProcess
RelationshipA new row representing a new version of the relationship being inactivated is added to the file.

The attributes of the new relationship version are set as follows:

  • id is set to the same relationship identifier as the relationship being inactivated
  • effectiveTime is set to the date the extension will be published
  • active is set to 0 to indicate that the relationship will become inactive at the time of publication
  • moduleId is set to identify a module in the extension
  • sourceId, destinationId, typeId, characteristicTypeId, typeId are set as per the previous version of this relationship
Provide Feedback --- # 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.4-authoring-relationships/5.4.4.3-inactivate-relationship-in-an-extension.md?ask= ``` 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.