> 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/range.md).

# Range

MRCM attribute range definitions are visualized on the right-hand side of the editor under the Ranges tab. When this tab is selected it will display the attribute range member(s) corresponding to the current attribute selection.

<figure><img src="/files/1orV9xEEwTlP1R56HgHx" alt=""><figcaption><p>MRCM Ranges</p></figcaption></figure>

<details>

<summary>Example</summary>

In the picture above the allowed range of *Direct device* attributes is defined as the descendants and self of the *Device* concept.

</details>

You can add a new range member by using the ![](/files/zi4dPtFbU8yBlRLHZ1mM) *Add new range member* button in the top right corner of the Ranges section. It will open the wizard below.

{% hint style="info" %}
The *Add new range member* action is only enabled for attributes in the Concept model object attribute hierarchy that don't yet have an MRCM attribute range member in the current module scope.
{% endhint %}

<figure><img src="/files/H1JQHYC1p2Az0xHmeDwq" alt=""><figcaption><p>Add new range member wizard</p></figcaption></figure>

The range constraint field allows you to specify any valid ECL expression defining acceptable values for the current attribute selection.

Rule strength and content type can be specified as well. These two fields are auto-filled with the most frequently used values.

{% hint style="info" %}
Rule strength and content type settings serve as guidance and do not factor into validation.
{% endhint %}

You can remove a range member from your extension using the *Remove range member* action in the top right corner of the range member section. Released members will be inactivated, unpublished members will be removed by this action. This action will inactivate released members and remove unpublished members

<figure><img src="/files/iv6b74D8Iph07DTSYqz1" alt=""><figcaption><p>Remove range member action</p></figcaption></figure>

{% hint style="info" %}
You can only remove/inactivate range members if they are in your extension's module.
{% endhint %}

{% hint style="info" %}
We limit allowed range members to one per attribute, but you may find multiple range definitions in the international MRCM attribute range reference set for different content types.
{% endhint %}

Once created you can still adjust the range members in your extension under the Ranges tab.

<figure><img src="/files/RgFikjZ71rTCtY5aUVSh" alt=""><figcaption><p>Range details tab</p></figcaption></figure>

ECL-valued fields can be edited by clicking on the ![](/files/rpvTRNQvv6FIZsbTfDpj) *Edit* button, which will open an ECL editor -, while other fields can be edited in place.


---

# 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/range.md?ask=<question>&goal=<endgoal>
```

`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.
