> 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-international-documents/snomed-ct-glossary/m/meaning-binding.md).

# meaning binding

## meaning binding

A terminology binding that represents the clinical meaning of a data item or collection of data items.

#### Notes

* A *meaning binding* associates a clinical meaning with either a data entry context or a defined collection of data items in an electronic health record information model. The clinical meaning of an instance of a data item with a *meaning binding* is determined by applying the *meaning binding* to the value or set of values in that instance.
* SNOMED CT *meaning bindings* should be represented by expression templates containing one or more template slots that can be replaced by concepts entered or stored in a particular context.

#### Example

* An application that manages surgical procedure requests could identify requested procedures using concepts that are subtypes of [387713003 | Surgical procedure|](http://snomed.info/id/387713003) . In this case, the data item in which that *concept* is recorded should have a *meaning binding* that explicitly indicates that this is a request for that procedure. The *expression template* below represents this *meaning binding*. It indicates that the procedure selected should replace the "@procedure" template slot, resulting in an expression that means procedure has been requested, rather than suggesting incorrectly, that it has been done.

/\* Expression Template \*/

[400999005 |Procedure requested (situation)|](http://snomed.info/id/400999005) :\
{ [363589002 |Associated procedure (attribute)|](http://snomed.info/id/363589002) = \[\[ +id < [387713003 |Surgical procedure|](http://snomed.info/id/387713003) @procedure ]] }

/\* Resulting Expression if "38102005 Cholecystectomy (procedure)" is entered \*/

[400999005 |Procedure requested (situation)|](http://snomed.info/id/400999005) :\
{ [363589002 |Associated procedure (attribute)|](http://snomed.info/id/363589002) = [38102005 |Cholecystectomy (procedure)|](http://snomed.info/id/38102005) }

## Alternative

* ```
  Semantic binding
  ```

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=meaning%20binding" 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-international-documents/snomed-ct-glossary/m/meaning-binding.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.
