> 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-international-documents/snomed-ct-glossary/r/role-group.md).

# role group

## role group

**This is a synonym for relationship group.**

## relationship group

**This is used to refer to a group of relationships representing an attribute group.**

## attribute group

An association between a set of attribute value pairs that causes them to be considered together within a concept definition or postcoordinated expression.

#### Notes

* When an *attribute group* is represented as a group of defining relationships it is usually referred to as a *relationship group.*

#### Example

* [| Cholecystectomy with exploration of common duct|](http://snomed.info/id/45993005) has two different attribute groups:
  * [| Method|](http://snomed.info/id/260686004) [| Exploration - action|](http://snomed.info/id/281615006) *is grouped with* [| Procedure site - Direct (attribute)|](http://snomed.org/fictid#) [| Common bile duct structure|](http://snomed.info/id/79741001)
  * [| Method|](http://snomed.info/id/260686004) [| Excision - action|](http://snomed.info/id/129304002) *is grouped with* [| Procedure site - Direct (attribute)|](http://snomed.org/fictid#) [| Gallbladder structure|](http://snomed.info/id/28231008)
* If these attributes were not grouped, this procedure would incorrectly classified as a subtype of [| Excision of common bile duct|](http://snomed.info/id/6402000) .

## Alternatives

* **Relationship group**
* **Role group**

##

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=role%20group" class="button primary">Provide Feedback</a>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snomed.org/snomed-international-documents/snomed-ct-glossary/r/role-group.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.