# Representation of the Logical Model

> **This** **Figure shows how SNOMED CT release files represent the logical model.**

The following figure shows how SNOMED CT release files represent the logical model.

<div data-full-width="true"><figure><img src="/files/eq2DisTvauH37koFpiz5" alt=""><figcaption><p>Representation of the logical model of SNOMED CT</p></figcaption></figure></div>

***

**Release file representation of the logical model**

<table data-full-width="false"><thead><tr><th width="188.5093994140625">Logical Model</th><th width="351.90625">Description</th><th width="257.8515625">References</th></tr></thead><tbody><tr><td><strong>Concepts</strong></td><td>Each concept is represented by a row in the concept release file.</td><td><a href="/pages/D27iHtoMThoOZWaFUJ0q">Concept File Specification</a></td></tr><tr><td><strong>Descriptions</strong></td><td>Each description is represented by a row in the description release file.</td><td><a href="https://github.com/SNOMED-Documents/snomed-release-file-specification/blob/main/4%20component-release-files-specification/4.2%20file-format-specifications/4.2.2%20description-file-specification">Description File Specification</a></td></tr><tr><td><strong>Stated Concept Definitions</strong></td><td><p>Each stated concept definition is represented by a set of rows in the OWL axiom reference set file, which follows the format of an OWL Expression Reference Set. Each row contains an axiom that forms part of the definition of the concept identified by the referencedComponentId.</p><p><strong>Notes:</strong></p><ul><li>As well as representing the definitions of individual concepts, the OWL axiom reference set represents characteristics of attributes including transitivity, reflexivity and property chains.</li><li>The OWL Ontology Reference Set also follows the OWL Expression Reference Set pattern. It contains general information about the terminology, which is required by a description logic classifier but is not subject to significant changes between release versions.</li></ul><p><strong>Change Note</strong></p><p>This representation was introduced in July 2018 and, following a transitional period, now fully represents all stated concept definitions.</p></td><td><p><a href="/pages/aGUxKhnbV0xEnXMiXg8b">OWL Expression Reference Set</a></p><p><a href="/spaces/UVgNFMSypqSsi48DpFEe">SNOMED CT OWL Guide</a></p><p><a href="/spaces/hRUJsLa2ant5L63pkp1O">SNOMED CT Logic Profile Specification</a></p></td></tr><tr><td><strong>Inferred Concept Definitions</strong></td><td>Each inferred concept definition is represented by a set of rows in the relationship release file. Each row in the set that defines a concept, represents a necessary, defining relationship with another concept. The definitionStatusId column in the concept file row indicates whether the set of defining relationships is sufficient to define the concept.</td><td><a href="/pages/ZcWSMK53FJSJi7JeKdN9">Relationship File Specification</a></td></tr><tr><td><strong>Other Related Information</strong></td><td><p>Represented by a range of reference set release files that conform to the extensible reference set file format.</p><p>Each row in a reference set refers to a concept or description as a member of the set.The extensible structure allows different types of related information to be associated with the referenced component.</p></td><td><p><a href="https://github.com/SNOMED-Documents/snomed-release-file-specification/blob/main/5%20reference-set-release-files-specification/5.2%20reference-set-types">Reference Set Types</a></p><p><a href="/spaces/qOI2v58ZsXOoklmwBOk4">SNOMED CT Reference Set Guide</a></p></td></tr></tbody></table>

{% hint style="warning" %}
Prior to July 2018 the stated view of concept definitions were represented by relationships in the stated relationship file. During a transitional period between July 2018 and July 2019 the OWL reference sets were introduced. Since the end of that transitional period in July 2019, the stated relationship file is no longer maintained or distributed.\
The representation of the inferred view of concept definitions is unchanged from the perspective of the release file structure. However, the nature and quality of the inferred relationships changed as a result of inferences derived from the enhanced definitions represented as axioms in the OWL axiom reference set.\
More information on these changes is available in this document in Section [OWL Expression Reference Set](/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/5.2-reference-set-types/5.2.1-content-reference-sets/5.2.1.9-owl-expression-reference-set.md) and a historical note on [Representation of the Logical Model - Before July 2018](https://github.com/SNOMED-Documents/snomed-release-file-specification/blob/main/2%20snomed-ct-logical-model/broken-reference/README.md). Detailed information about the representation of SNOMED CT definitions using OWL axioms is provided by the [SNOMED CT OWL Guide](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-owl-reference-set-specification/) and [SNOMED CT Logic Profile Specification](https://docs.snomed.org/snomed-ct-specifications/snomed-ct-logical-profile-specification/).
{% endhint %}

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Release+File+Specification&#x26;entry.670899847=Representation%20of%20the%20Logical%20Model" 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-specifications/snomed-ct-release-file-specification/logical-model/2.2-representation-of-the-logical-model.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.
