> 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/f/focus-concept.md).

# focus concept

## focus concept

The part of a SNOMED CT expression that represents the primary clinical idea.

#### Note

* Typically the *focus concept* is a clinical finding, procedure, observable entity *.* However, it may be a concept from any domain that can be refined in accordance with concept model rules.
* The *focus concept* may have a refinement that provides more detailed information.
* The *focus concept* may be given context by a surrounding context wrapper.

#### Examples

* The [66308002 | Fracture of humerus|](http://snomed.info/id/66308002) is the *focus concept* in the following three examples:
* Example 1: Focus concept with a refinement that indicates the type and location of the fracture.

[66308002 |fracture of humerus|](http://snomed.info/id/66308002) : ⬅︎ Focus concept\
{ [363698007 |finding site|](http://snomed.info/id/363698007) = [20760004 |shaft of humerus|](http://snomed.info/id/20760004) , ⬅︎ Refinement\
[116676008 |associated morphology|](http://snomed.info/id/116676008) = [73737008 |Fracture, spiral|](http://snomed.info/id/73737008) } ⬅︎ ...

* Example 2: Focus concept in a context wrapper the fracture of the humerus is past history rather than a current condition.

[312850006 |History of disorder (situation)|](http://snomed.info/id/312850006) : ⬅︎ Context wrapper\
{ [66308002 |fracture of humerus|](http://snomed.info/id/66308002) } ⬅︎ Focus concept

* Example 3: Focus concept in a context wrapper with a refinement to add more detailed information.

[312850006 |History of disorder (situation)|](http://snomed.info/id/312850006) : ⬅︎ Context wrapper\
{ [246090004 |Associated finding|](http://snomed.info/id/246090004) = [66308002 |fracture of humerus|](http://snomed.info/id/66308002) : ⬅︎ Focus concept\
{ [363698007 |finding site|](http://snomed.info/id/363698007) = [20760004 |shaft of humerus|](http://snomed.info/id/20760004) , ⬅︎ Refinement\
[116676008 |associated morphology|](http://snomed.info/id/116676008) = [73737008 |Fracture, spiral|](http://snomed.info/id/73737008) } ⬅︎ ...\
}

##

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SNOMED+Glossary&#x26;entry.670899847=focus%20concept" 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/f/focus-concept.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.