> 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/information-models-and-terminology-binding/5.2-terminology-bindings.md).

# Terminology Bindings

This chapter defines the model meaning binding and value set binding between data elements in the Logical Model and their corresponding SNOMED CT concepts and value sets. These bindings ensure precise alignment between the Logical Model and SNOMED CT, supporting consistent and interoperable representation of laboratory orders, specimens, and results.

### Laboratory Order <a href="#id-5.2terminologybindings-laboratoryorder" id="id-5.2terminologybindings-laboratoryorder"></a>

The laboratory orders represent the request that starts the laboratory process. In the context of this implementation guide for the LOINC Ontology, the recommendation is to use Observable entities for this purpose, selected from a subset that is marked as "Orderable" entities by LOINC.

<table><thead><tr><th width="106.44921875">Attribute</th><th width="147.65234375">Type</th><th>Value Set Binding</th></tr></thead><tbody><tr><td>code</td><td>Structured</td><td><code>&#x3C; 363787002 |Observable entity (observable entity)| {{ C moduleId = 11010000107 }} AND ^ |Orderable LOINC Concepts|</code></td></tr><tr><td>priority</td><td>Structured</td><td><code>&#x3C; 272125009 |Priorities (qualifier value)|</code></td></tr><tr><td>status</td><td>Structured</td><td><code>&#x3C; 288532009 |Context values for actions (qualifier value)|</code></td></tr></tbody></table>

### Specimen <a href="#id-5.2terminologybindings-specimen" id="id-5.2terminologybindings-specimen"></a>

SNOMED CT includes a hierarchy of specimens and is used to define observable entities in the LOINC Ontology. The specimens used in the LOINC Ontology can be extracted using the SNOMED CT Expression Constraint Language by selecting concepts used as values for the 704327008 |Direct site (attribute)| or 704319004 |Inheres in (attribute)| attribute within the LOINC Ontology.

<table><thead><tr><th width="125.1484375">Attribute</th><th width="124.3671875">Type</th><th>Value Set Binding</th></tr></thead><tbody><tr><td><strong>code</strong></td><td>Structured</td><td>(&#x3C; 363787002 |Observable entity (observable entity)| {{ C moduleId = 11010000107 }} . (704327008 |Direct site (attribute)| OR 704319004 |Inheres in (attribute)|) ) AND ( &#x3C;&#x3C; 123038009 |Specimen (specimen)|)</td></tr><tr><td><strong>collection method</strong></td><td>Structured</td><td>&#x3C;&#x3C;(&#x3C;&#x3C;17636008 |Specimen collection (procedure)|.260686004 |Method (attribute)|)</td></tr></tbody></table>

### Result <a href="#id-5.2terminologybindings-result" id="id-5.2terminologybindings-result"></a>

In the results, the codes for tests can be different from those ordered. In cases like "panels", the order concepts are transformed into a set of observable concepts that can be reported as results. The LOINC Ontology identifies a subset of observable concepts that are valid to report as "observed" results.

<table><thead><tr><th width="133.93487548828125">Attribute</th><th width="202.48046875">Type/Note</th><th>Value Set Binding</th></tr></thead><tbody><tr><td><strong>Test code</strong></td><td>Structured</td><td>&#x3C; 363787002 |Observable entity (observable entity)| {{ C moduleId = 11010000107 }} AND ^ |Observable LOINC Concepts|</td></tr><tr><td><strong>Value</strong></td><td>Unstructured</td><td>N/A</td></tr><tr><td><strong>Structured</strong></td><td>Variable: depends on each observable.</td><td></td></tr><tr><td><strong>Reference Range</strong></td><td>Unstructured</td><td>N/A</td></tr><tr><td><strong>Units</strong></td><td>Structured</td><td>&#x3C;&#x3C; 767525000 |Unit (qualifier value)|</td></tr><tr><td><strong>Interpretation</strong></td><td>Structured</td><td>Variable: depends on each observable.</td></tr><tr><td><strong>Status</strong></td><td>Structured</td><td>&#x3C; 288532009 |Context values for actions (qualifier value)|</td></tr></tbody></table>

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=LOINC+Implementation+Guide&#x26;entry.670899847=Terminology%20Bindings" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snomed.org/implementation-guides/loinc-implementation-guide/information-models-and-terminology-binding/5.2-terminology-bindings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.