> 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-practical-guides/snomed-ct-extension-guide/5-key-steps/5.4-authoring/5.4.5-authoring-reference-sets/5.4.5.2-modify-reference-set-in-an-extension.md).
# Modify Reference Set in an Extension
## Purpose
Depending on the type of reference set, there may be different reasons for modifying the reference set, including:
* Promoting the reference set to a parent module, for example the International Edition
* Transfer of responsibility for maintenance to an organization that is responsible for a module on which the current module depends, see [End Support for a Reference Set](broken://spaces/qOI2v58ZsXOoklmwBOk4/pages/6Z0H4l1A6YEwHxZrWLID)
## Principles
Principles for modifying reference sets include:
* Reference sets can be modified by changing the value of the *active* attribute or the value of the *moduleId* attribute, i.e. for activating or inactivating the reference set, or moving the reference set to another module (a module on which the current module depends).
* The reference set metadata concept is always primitive and the concept can therefore not be changed from primitive to fully defined, or from fully defined to primitive, i.e. the value of the *definitionStatusId* attribute should be primitive for all versions of the reference set
* The reference set type should ***not*** be changed, i.e. the |is a| relationship, linking the reference set to the appropriate reference set type concept should not be changed
* The only situation where the the reference set type may change is if the reference set was originally misplaced in the SNOMED CT hierarchy.
* If the reference set needs to be changed to a different type, (for example, from a simple reference set to an ordered component type reference set) then it would require the original reference set to be inactivated and a new reference set to be created in accordance with the Descriptor for that reference set type.
* Reference sets that belong to a module which is not managed by the extension producer should not be modified.
## Process
**Modifying a reference set created within the extension module**
The process for modifying the reference set concept, is similar to the general process for modifying concepts in SNOMED CT. Therefore, please refer to [Modify Concept in an Extension](/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.4-authoring/5.4.2-authoring-concepts/5.4.2.2-modify-concept-in-an-extension.md) for further guidance.
Provide Feedback
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.4-authoring/5.4.5-authoring-reference-sets/5.4.5.2-modify-reference-set-in-an-extension.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.