> 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-compositional-grammar-specification/examples/6.3-expression-with-refinements.md).

# Expression With Refinements

One or more refinements may be added to a concept to qualify it. This is done by putting the concept to be qualified before a colon and the qualifying expression after. The qualifying expression is of the form "attribute = value". The example below describes an operation to remove an ovary (i.e. an 'oophorectomy') using a laser.

```
83152002 |Oophorectomy| : 405815000 |Procedure device| = 122456005 |Laser device|
```

The next example, shown below, describes the right hip joint.

```
182201002 |Hip joint| : 272741003 |Laterality| = 24028007 |Right|
```

Where more than one qualifying attribute is required, these can be separated using a comma. The example below describes the removal of an ovarian structure using a laser device.

<pre><code><strong>71388002 |Procedure| :
</strong>405815000 |Procedure device| = 122456005 |Laser device| ,
260686004 |Method| = 129304002 |Excision - action| ,
405813007 |Procedure site - direct| = 15497006 |Ovarian structure|
</code></pre>

A further example, below, describes the emergency removal of the appendix:

```
65801008 |Excision| :
405813007 |Procedure site - direct| = 66754008 |Appendix structure| ,
260870009 |Priority| = 25876001 |Emergency|
```

Refinements may also be applied to a conjoined concept. For example, the following two expressions are equivalent (because an 'ulna' is a bone in an 'upper limb'):

{% code overflow="wrap" %}

```
313056006 |Epiphysis of ulna| : 272741003 |Laterality| = 7771000 |Left|
```

{% endcode %}

{% code overflow="wrap" %}

```
119189000 |Ulna part| + 312845000 |Epiphysis of upper limb| : 272741003 |Laterality| = 7771000 |Left|
```

{% endcode %}

Note that there are no brackets around " [119189000 |Ulna part|](http://snomed.info/id/119189000) + [312845000 |Epiphysis of upper limb|](http://snomed.info/id/312845000) " in the above example, as the refinement automatically applies to the conjoined concept.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Compositional-Grammar-Specification&#x26;entry.670899847=Expression%20With%20Refinements" 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-compositional-grammar-specification/examples/6.3-expression-with-refinements.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.
