> 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/a/attribute/attribute-group-cardinality-constraint.md).

# attribute group cardinality constraint

## attribute group cardinality constraint

A constraint on the number of times that an attribute group may be included in the same concept definition or expression.

#### Notes

* Cardinality constraints are represented by square brackets containing a minimum value value represented as an integer, optionally followed by two dots and a maximum value represented as an integer or as an asterisk \*\*\*\*\*.
  * If the maximum is omitted then the maximum cardinality is the same as the minimum cardinality.
  * If the maximum is an asterisk \*\*\*\*\* the maximum cardinality is unlimited.
* *Attribute group cardinality* is NOT the same as attribute in group cardinality.

Attribute in group cardinality constraint is defined as:

```
* A constraint on the number of times that a specific attribute may be included in the same attribute group.
```

\_\_

#### Examples

* The expression constraint below is satisfied only by products with one, two or three attribute groups, which each contain at least one active ingredient relationship.

< [373873005 |Pharmaceutical / biologic product|](http://snomed.info/id/373873005) :\
\[1..3] { [127489000 |Has active ingredient|](http://snomed.info/id/127489000) = < [105590001 |Substance|](http://snomed.info/id/105590001) }

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=attribute%20group%20cardinality%20constraint" 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/a/attribute/attribute-group-cardinality-constraint.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.