# General Concept Inclusions - GCIs

<mark style="color:$danger;">**This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.**</mark>

## Draft guidance

See the background, use cases, and examples for general concept inclusion axioms as well as explanation of the definition status at [General Concept Inclusion 0.01](https://docs.google.com/document/d/1-Tvswkw5USXydVWpBsT3iORdOFzx3qKAyownS4Enor4/edit).

## Authoring Platform User Guide for GCIs

Reference the [Authoring - Description Logic (DL) Support Features](https://docs.snomed.org/snomed-ct-user-guides/authoring-user-guide/how-to/task-edit/add-a-general-concept-inclusion-gci-to-a-concept) for technical information describing how to add an additional axiom and general concept inclusion.

## GCI display in the browser

A concept with GCIs will display in the browser in the stated view only.

For example,

Below is 417163006 | Traumatic or non-traumatic injury (disorder)| in the *stated* view with the GCIs appearing to the right of the concept:

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-924b6a6be5e394f4e6abff6de584945928e8cc05%2F174691746.png?alt=media" alt=""><figcaption></figcaption></figure>

Here is the same concept in the *inferred* view without the GCIs appearing:

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-0b246553f02c286c1bbe5d9a4e2a6c15816a078a%2F174691745.png?alt=media" alt=""><figcaption></figcaption></figure>

### Modeling concepts with a GCI-modeled supertype

General concept inclusions allow multiple definitions of a concept. A group of subtypes may be defined using GCIs and be considered subtypes of the parent concept without fully defining that parent concept. That parent concept could have multiple definitions, each of which is valid but none of which completely describes the parent concept on its own.

When modeling a concept intended to be a subconcept of a GCI concept defined by General Concept Inclusion (GCI) axioms, it is unnecessary to state the GCI concept as a parent if the logic of the concept being modeled is already covered by a GCI axiom. This holds true even if the GCI-modeled concept is primitive, as the GCI axioms ensure that the correct subsumption relationship is inferred regardless.

* For example,
  * 281372009 |Lumbarized first sacral vertebra (disorder)|

The diagram below shows Lumbarized first sacral vertebra (disorder) incorrectly modeled on the right, with a stated primitive GCI-modeled parent of Transitional lumbosacral vertebra (disorder). Transitional lumbosacral vertebra (disorder) is modeled with a GCI, as notified by the salmon pink color. The left side of the diagram shows the inferred view with two parents.

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-717acd6ff3c0aec96c56410c08388ac092ae5f41%2F174691743.png?alt=media" alt=""><figcaption></figcaption></figure>

The GCI-modeled primitive concept, Transitional lumbosacral vertebra (disorder), is unnecessary to state as a parent. The diagram below shows correct modeling of Lumbarized first sacral vertebra (disorder) with the absence of Transitional lumbosacral vertebra (disorder) as a parent, and yet the inferred view diagram on the left is still the same as compared to the incorrectly modeled diagram above.

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-472fc133d22c7b5eb7394daa459ca14929d71ba0%2F174691742.png?alt=media" alt=""><figcaption></figcaption></figure>

Alternatively, if a GCI-modeled parent will not subsume an appropriate child concept, then the GCI-modeled concept should be stated as a primitive supertype.

Finally, the example below of 82271004 |Injury of head (disorder)| illustrates a concept with a GCI-modeled supertype of 417163006 |Traumatic or non-traumatic injury (disorder)|. In this case, the concept Injury of head (disorder) is sufficiently defined.

<figure><img src="https://3063935683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSZh4aZdgpviXMYp37bCy%2Fuploads%2Fgit-blob-f2804189d7d4b8a68e31a7c8f28e2c4a744380b0%2F174691739.png?alt=media" alt=""><figcaption></figcaption></figure>

## Defining GCI-modeled concepts

Though most are primitive, it is possible to define concepts modeled with GCIs. A concept must continue to meet the necessary conditions in order to be considered defined. GCIs can be added to extend the subtypes a defined concept will infer when appropriate.

## Points to Consider

* GCIs are not restricted to particular hierarchies; they can be used as applicable in any hierarchy that has a concept model.
* The Authoring Platform does not currently have the ability to create templates that include GCIs.
* A concept which has a stated "is a" relationship to a concept with GCIs will need to have GCIs added to it directly if GCIs are required to appropriately represent the concept. GCI axioms are not inherited from supertype to a subtype concept.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=General%20Concept%20Inclusions%20-%20GCIs" 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/education/snomed-ct-education-editorial-guide/readme/authoring/general-modeling/general-concept-inclusions-gcis.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.
