> 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-ct-user-guides/authoring-user-guide/faqs/concept-editor-field-color-coding.md). # Concept Editor Field Color Coding In the Authoring Platform Concept Editor, the background color of concept fields—including **Concept Descriptions**, **Parent Concepts**, and **Relationship Attribute Target Values**—indicates the concept's **definition status** and whether it is modeled using **General Concept Inclusion (GCI)** axioms. *** ### Color Coding Summary | Field Color | Definition / Axiom Status | Meaning & Editorial Impact | | ----------------------------------------------- | ----------------------------- | --------------------------------------------------------------------------------------- | | **Blue** | **Primitive** | The concept is primitive and does **not** have any active GCI axioms. | | **Purple** | **Fully Defined** | The concept is fully defined by its stated relationships/axioms (sufficiently defined). | | **Salmon / Peach** *(often referred to as red)* | **Primitive with Active GCI** | The concept has one or more **active General Concept Inclusion (GCI) axioms**. | {% hint style="info" %} **Fully Defined Concepts with GCIs:**\ If a concept is **Fully Defined** and also possesses one or more GCI axioms, the field displays in **Purple** (the Fully Defined status takes visual precedence). {% endhint %} *** ### Where Color Coding Appears in the Editor #### 1. Concept Description Fields When editing a concept in the Edit panel, the background color of the description rows reflects the definition and GCI status of the concept currently being worked on. #### 2. Parent Concept Fields Proximal primitive or fully defined parent concept fields display their corresponding blue or purple background. #### 3. Relationship Attribute Target Values (Destination Concepts) When selecting or dropping a target concept into an attribute value field (such as *Finding site*, *Associated morphology*, or *Method*), the field immediately adopts the target concept's color coding: * **Purple:** The chosen target concept is Fully Defined. * **Blue:** The chosen target concept is Primitive. * **Salmon:** The chosen target concept is modeled with an active GCI axiom. *** ### Axiom Status & Behaviour * **Active GCIs:**\ A concept with at least one active GCI axiom displays a salmon background in its description fields and when selected as an attribute target value. * **Inactivated GCIs:**\ If all GCI axioms on a concept are inactivated, the salmon highlighting is removed. The field automatically reverts to its base definition status color (**Blue** if Primitive, **Purple** if Fully Defined). * **Taxonomy & Concept Header Badges:**\ While the editor field backgrounds use this color coding, the taxonomy navigation tree and concept badges continue to represent definition status using standard iconography (solid yellow circle for Primitive; circle with three horizontal lines `===` for Fully Defined). *** ### Visual Examples | Example | Indicator | Description | | | | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | -------- | | **Primitive Target Concept** | Primitive target concept |

Standard primitive concept selected as an attribute relationship value without GCIs.
Example:
195967001 | Asthma (disorder) |

| | **Fully Defined Target Concept** | Fully defined target concept |

Fully defined concept selected as an attribute relationship value.

Example:
22298006 | Myocardial infarction (disorder) |

| | **GCI Target Concept** | Target concept with an active GCI axiom |

Concept with an active GCI axiom selected as an attribute relationship value.

Example:
11314841000119105 | Secondary osteoporotic fracture (disorder) |

| | **GCI Concept Header / Descriptions** | GCI concept description rows |

Concept editor displaying salmon-highlighted description rows for a GCI concept.
Example:
703264005 | Secondary osteoporosis (disorder) |

| --- # 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-ct-user-guides/authoring-user-guide/faqs/concept-editor-field-color-coding.md?ask=&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.