> 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/implementation-guides/loinc-implementation-guide/technical-application/6.2-accessing-the-loinc-ontology.md).

# Accessing the LOINC Ontology

The LOINC ontology is represented as a SNOMED CT extension and is distributed as an independent package.

Each version of a SNOMED CT extension depends on a specific version of the International Edition (refer to section [Module Dependencies](/snomed-ct-practical-guides/snomed-ct-extension-guide/4-logical-design/4.2-modules/4.2.2-module-dependencies.md) for more details). Therefore, deploying the LOINC ontology requires access to both the LOINC ontology release package and the corresponding International Edition release package, upon which the specific version of the LOINC ontology is dependent.

<figure><img src="https://787158931-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvdInPDnQhewgUCH6BOCp%2Fuploads%2F0XuU87Mvb0DKlNCZIeL1%2F278302107.png?alt=media&amp;token=e919f3e9-0792-4620-9e01-e19a29f79354" alt=""><figcaption></figcaption></figure>

## License to Use SNOMED CT <a href="#id-6.2accessingtheloincontology-licensetousesnomedct" id="id-6.2accessingtheloincontology-licensetousesnomedct"></a>

To access and use the LOINC ontology, users must have a valid Affiliate License for SNOMED CT. SNOMED CT is a globally recognized clinical terminology standard, and its usage is governed by strict licensing agreements to ensure compliance and proper utilization. Licensing ensures that users are authorized to access and implement SNOMED CT in their systems.

Individuals or organizations interested in using SNOMED CT must obtain an Affiliate License through their National Release Center (NRC) or SNOMED International.

More information can be found here: <https://www.snomed.org/get-snomed>

The following points outline the key aspects of member licensing:

* **Member Countries:** Member countries have a national licensing arrangement with SNOMED International. Healthcare professionals and organizations within these countries can usually access SNOMED CT through their NRC without additional licensing fees.
* **Access via NRCs:** National Release Centers are responsible for distributing SNOMED CT within their respective countries. They provide access, support, and updates to licensed users. Users should contact their NRC for specific details on how to access the LOINC Extension to SNOMED CT.
* **Non-Member Countries:** In countries that are not members of SNOMED International, individuals and organizations must directly approach SNOMED International to obtain the necessary licenses. This may involve additional costs and compliance with international licensing requirements.

## Accessing the LOINC Extension <a href="#id-6.2accessingtheloincontology-accessingtheloincextension" id="id-6.2accessingtheloincontology-accessingtheloincextension"></a>

The LOINC Extension can be accessed via its main website hosted by Regenstrief:

<https://loincsnomed.org/downloads>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=LOINC+Implementation+Guide&#x26;entry.670899847=Accessing%20the%20LOINC%20Ontology" 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/implementation-guides/loinc-implementation-guide/technical-application/6.2-accessing-the-loinc-ontology.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.