> 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-specifications/snomed-ct-owl-reference-set-specification/introduction/1-introduction.md).

# Introduction

## Background

SNOMED CT is a clinical terminology with a comprehensive coverage of wide clinical specialties and requirements. The development and maintenance of SNOMED CT relies on Description Logics (DL) and its reasoning services. The stated relationship file has been used to represent DL definitions. However, it is unable to fully represent semantics of the DL expressivity due to the limitation of its relational structure.

The new OWL refsets are designed to replace the stated relationship file and it represents the DL definitions for SNOMED CT content by following the international standard of OWL 2 Web Ontology Language.

## Purpose

The purpose of this document is to define and describe the OWL Reference Set.

## Scope

The document presents the specification of OWL refsets. It also documents the background, design considerations, quality assurance, and distribution format of the OWL refsets.

The implementation of the OWL refsets in the applications, and transformation of it to an OWL ontology, are out of the scope.

## Audience

The target audiences of this document include:

* SNOMED CT national release centers;
* SNOMED CT terminology content developers and technical developers;
* SNOMED CT implementers, analysts, and developers of electronic health records and information systems.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=OWL+Specification&#x26;entry.670899847=1.%20Introduction" 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-ct-specifications/snomed-ct-owl-reference-set-specification/introduction/1-introduction.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.