# Foundation Metadata Concept Hierarchy

## Foundation Metadata Concept

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/900000000000454005">900000000000454005 | Foundation metadata concept|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">This concept is a supertype for metadata used to support SNOMED CT reference sets.</td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>No new subtype children may be added in an extension.</p><p>See tables below for concept addition rules for each of the subtypes of <a href="http://snomed.info/id/900000000000454005">900000000000454005 | Foundation metadata concept|</a> </p></td></tr></tbody></table>

## Reference Sets

<table data-header-hidden><thead><tr><th width="240.21484375" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/900000000000455006">900000000000455006 | Reference set|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">The subtype children represent reference set types. Subtype descendents represent either reference sets of the type specified by their supertype parent or groups of reference sets of a type specified by their supertype parent.</td></tr><tr><td valign="top"><strong>Examples</strong></td><td valign="top"><p></p><p>Reference set types</p><ul><li><p><a href="http://snomed.info/id/609331003">609331003 | Extended map type reference set|</a></p><ul><li><a href="http://snomed.info/id/447562003">447562003 | ICD-10 complex map reference set|</a><br></li></ul></li><li><p><a href="http://snomed.info/id/900000000000521006">900000000000521006 | Association type|</a></p><ul><li><p><a href="http://snomed.info/id/900000000000522004">900000000000522004 | Historical association|</a>   <em>(This is a grouper concept not an actual reference set)</em></p><ul><li><a href="http://snomed.info/id/900000000000526001">900000000000526001 | REPLACED BY association reference set|</a>  </li><li><a href="http://snomed.info/id/900000000000527005">900000000000527005 | SAME AS association reference set|</a></li></ul></li></ul></li><li><a href="http://snomed.info/id/900000000000480006">900000000000480006 | Attribute value type|</a> </li></ul></td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>New subtype children may be added in an extension, as long as they represent a new and distinct Reference Set Type (i.e. not an individual reference set).</p><p>New subtype descendants may be added in an extension, as long as they represent a Reference Set of the type defined by its supertype ancestors.</p></td></tr><tr><td valign="top"><strong>Concept Addition Uses Cases</strong></td><td valign="top"><p></p><ul><li>To create a new reference set</li><li>To define a new reference set type</li><li>To define a group of related reference sets</li></ul></td></tr><tr><td valign="top"><strong>Additional Notes</strong></td><td valign="top"><p>When a new reference set type is defined, an appropriate set of reference set descriptor rows must be created in the reference set descriptor reference set to specify the order and format of the reference set columns. Furthermore, the intended use and format of the new reference set type must also be documented.</p><p>Appropriate documentation should also be provided to describe the specific use of each individual reference set. The addition of reference set descriptor rows for individual reference sets is also recommended. However, this is optional if there are no additional constraints over and above those specified for its reference set type.</p></td></tr></tbody></table>

## Reference Set Attributes

<table data-header-hidden><thead><tr><th width="240.39453125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"><a href="http://snomed.info/id/900000000000457003">900000000000457003 | Reference set attribute|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top"><p>The subtype children represent named attributes used to represent columns in reference sets.</p><p>Also includes two special subtypes: <a href="http://snomed.info/id/900000000000459000">900000000000459000 | Attribute type|</a> and <a href="http://snomed.info/id/900000000000491004">900000000000491004 | Attribute value|</a> which are separately documented.</p></td></tr><tr><td valign="top"><strong>Examples</strong></td><td valign="top"><p></p><ul><li><p><a href="http://snomed.info/id/900000000000511003">900000000000511003 | Acceptability|</a></p><ul><li><a href="http://snomed.info/id/900000000000549004">900000000000549004 | Acceptable|</a></li><li><a href="http://snomed.info/id/900000000000548007">900000000000548007 | Preferred|</a></li></ul></li><li><a href="http://snomed.info/id/900000000000501005">900000000000501005 | Map group|</a></li><li><a href="http://snomed.info/id/900000000000536009">900000000000536009 | Source effective time|</a></li></ul></td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>Subtype children can be added in an extension to represent new column names for use in additional reference set type definitions.</p><p>See separate notes on subtype descendance of the special subtypes <a href="http://snomed.info/id/900000000000459000">900000000000459000 | Attribute type|</a> and <a href="http://snomed.info/id/900000000000491004">900000000000491004 | Attribute value|</a></p></td></tr></tbody></table>

## Reference Set Attribute Types

<table><thead><tr><th width="239.79296875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top">  <a href="http://snomed.info/id/900000000000459000">900000000000459000 | Attribute type|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">These concepts represent data types associated with reference set attributes.</td></tr><tr><td valign="top"><strong>Examples</strong></td><td valign="top"><p></p><ul><li><p><a href="http://snomed.info/id/900000000000459000">900000000000459000 | Attribute type (foundation metadata concept)|</a></p><ul><li><p><a href="http://snomed.info/id/900000000000460005">900000000000460005 | Component type (foundation metadata concept)|</a></p><ul><li><a href="http://snomed.info/id/900000000000461009">900000000000461009 | Concept type component|</a></li></ul></li><li><a href="http://snomed.info/id/900000000000476001">900000000000476001 | Integer (foundation metadata concept)|</a></li><li><p><a href="http://snomed.info/id/900000000000465000">900000000000465000 | String (foundation metadata concept)|</a><br></p><ul><li><a href="http://snomed.info/id/762678002">762678002 | OWL 2 language syntax (foundation metadata concept)|</a><br></li><li><a href="http://snomed.info/id/707000009">707000009 | SNOMED CT parsable string (foundation metadata concept)|</a><br></li><li><a href="http://snomed.info/id/900000000000466004">900000000000466004 | Text (foundation metadata concept)|</a></li><li><a href="http://snomed.info/id/900000000000475002">900000000000475002 | Time (foundation metadata concept)|</a></li><li><a href="http://snomed.info/id/900000000000469006">900000000000469006 | Uniform resource locator (foundation metadata concept)|</a><br></li><li><a href="http://snomed.info/id/900000000000474003">900000000000474003 | Universally Unique Identifier (foundation metadata concept)|</a></li></ul></li></ul></li></ul></td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>No new subtype children or subtype descendants may be added in an extension.</p><p>If new subtypes are required these should be requested for addition to the International Edition.</p></td></tr></tbody></table>

## Reference Set Attribute Values

<table data-header-hidden><thead><tr><th width="240.25390625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Hierarchy</strong></td><td valign="top"> <a href="http://snomed.info/id/900000000000491004">900000000000491004 | Attribute value|</a></td></tr><tr><td valign="top"><strong>Purpose</strong></td><td valign="top">These concepts represent values that can be applied to specified columns in a reference set.</td></tr><tr><td valign="top"><strong>Concept Addition Rules</strong></td><td valign="top"><p>Additional subtype children may be added in an extension to represent values applicable to a newly added reference set or reference set type.</p><p>Subtype descendants should <strong>not</strong> be added in an extension, except where they are descendants of a subtype child added to support a newly added reference set.</p></td></tr><tr><td valign="top"><strong>Potential Problems</strong></td><td valign="top">Adding subtype descendant to pre-existing subtype children would have the effect of changing the permitted value set for a pre-existing reference set type and reference sets defined as having that type.</td></tr></tbody></table>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=5.3.2.2.2%20Foundation%20Metadata%20Concept%20Hierarchy" class="button primary">Provide Feedback</a>


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/5-key-steps/5.3-assessing-requests/5.3.2-constraints-on-concept-requests/5.3.2.2-model-metadata-concept-hierarchies/5.3.2.2.2-foundation-metadata-concept-hierarchy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
