> 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-editorial-guide/readme/authoring/domain-specific-modeling/snomed-ct-model-component-1.md).

# Social Context

<table><thead><tr><th width="323.46630859375">Definition</th><th>Examples</th></tr></thead><tbody><tr><td><p>Social context (social concept) represents social aspects affecting patient health and treatment.</p><p>Conditions and circumstances related to healthcare that are subtypes of this hierarchy include:</p><ul><li>ethnic group</li><li>occupation</li><li>person</li><li>racial group</li><li>religion/philosophy</li><li>social status</li></ul></td><td><ul><li>372148003 |Ethnic group (ethnic group)|</li><li>24413000 |Carpenter, general (occupation)|</li><li>133932002 |Caregiver (person)|</li><li>415794004 |Unknown racial group (racial group) |</li><li>61154002 |Hinduism (religion/philosophy)|</li><li>22575004 |Middle class economic status (social concept)|</li></ul></td></tr></tbody></table>

### Occupation <a href="#occupation" id="occupation"></a>

Interpretation of the meaning of various occupation codes is jurisdictionally specific. International occupation classifications generally do not go to the detailed level that is often required. Job titles are very idiosyncratic and in some cases do not represent the actual occupation, but a ranking or seniority within an occupation.

Because of these reasons, occupations should be added to national extensions. No changes are currently being made to the occupation hierarchy. NRCs are encouraged to provide implementation guidance to their users.

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=SCT+Editorial+Guide&#x26;entry.670899847=Social%20Context" 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-editorial-guide/readme/authoring/domain-specific-modeling/snomed-ct-model-component-1.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.
