> For the complete documentation index, see [llms.txt](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/concept-model/editing-mrcm/module-scope.md). # Module scope To start authoring MRCM content and to be able to validate extension content through MRCM rules you will need to set up the module scope reference set for your extension. This reference set helps establish the scope of editable rules. They also tell the validation processes and which rules to run against your extension content. You can create the necessary module scope members from the editor with the help of the ![](/files/0pyAXsnftdOQP4uspBT6) *Initialize MRCM reference set* button at the top right corner of the editor. The warning and the hint in the header will prompt you to use this action as well.

{% hint style="info" %} The MRCM editor always opens using the current codesystem's module scope. If you haven't created the necessary module scope members yet, it will have no rules to display, even if you are working with a data set that has international MRCM rules in it already. {% endhint %} This action will open the following wizard.

Under module scope, you will be able to choose one of the modules that belongs to your extension. Once you've made a choice the rest of the wizard will become enabled too and you will have to choose one of two options.

You can either extend an existing rule set by choosing the first option *Existing MRCM rules* or you can choose to create all MRCM rules needed by your extension from scratch by choosing the *Custom new MRCM rule reference sets*. In the first case, no new MRCM reference sets will be created, but three new entries will be added to the MRCM module scope reference set that link the current international reference sets to your extension module as can be seen below.

MRCM module scope refset members for existing MRCM refsets

In the second case, you will have to specify the names of the three new reference sets in which the three different types of MRCM members will be stored. The wizard will autofill a suggested name for these reference sets, but you may customize it as you see fit.

In this case, too, three new module scope members will be created, but this time they will link your extension module to the new reference sets.

MRCM module scope refset members for new MRCM refsets

In case you chose to maintain MRCM rules in custom new reference sets, the editor will still be empty as adding MRCM members is yet to be done. In case you chose to use an existing rule set those rules will appear in the MRCM editor now. If you would like to view an existing rule set, you can do so by using the ![](/files/YaQ7vwjmmTQiSBLFll1C) *Update module scope* button at the top right corner of the editor.

The resulting wizard will let you choose from modules that have been added to the Module scope reference set (in our example *SNOMED CT core* and *Example extension module*). After hitting **`Finish`**, the MRCM editor will be updated with content from the MRCM rule reference sets corresponding to the chosen module within the Module scope reference set. {% hint style="info" %} Note that this action doesn't change the module scope for your extension or what rules apply to your extension. It only lets you view content in other module scopes. You can use the same action to switch back to your extension's module scope. The header of the editor displays the current module scope selection for clarity. {% endhint %}

--- # 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.b2ihealthcare.com/snow-owl-authoring-platform/concept-model/editing-mrcm/module-scope.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.