> 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/general-naming-conventions/person-naming-conventions.md).
# Person Naming Conventions
## Patient vs Subject
The |Situation with explicit context (situation)| hierarchy is intended for concepts that explicitly include contextual information. Context can include whom the finding is about, or on whom a procedure is performed. These concepts can be used to represent different meanings, e.g., past history, family history, planned care, excluded diagnosis, etc.
In contrast, a concept in the Clinical Finding or Procedure hierarchy has a default [Intended Use](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/snomed-ct-introduction/intended-use.md) of the subject of the record. This context can be overridden by the information model.
* For example,
* The concept |Asthma (disorder)| could be used in a family history field to represent a family history of asthma.
However, including the term *subject* or *patient* within a Clinical finding or Procedure concept prevents that concept’s context from being overridden by the information model.
* For example,
* The concept |Patient immunocompromised (finding)| could not be used in a family history field to represent that a family member is immunocompromised.
Therefore, the use of *patient* and *subject* should be used only when necessary.
Descriptions should use the word *subject*, not *patient*, if required, as *subject* is broader than *patient*.
* For example,
```
420058008 | Provider of history other than subject (person)|
```
*Subject* refers to the subject of record, who may, in some circumstances, not be the patient.
Best practice is to create a contextless concept.
* Example - finding,
* Patient unable to chew with denture (finding) - incorrect
* Unable to chew with denture (finding) - correct
* Example - procedure,
* Positioning subject in supine position (procedure) -incorrect
* Positioning in supine position (procedure) - correct
## Caregiver vs Carer
Descriptions with *caregiver* should be as follows:
* An FSN should use *caregiver* as (one word).
* There should be a synonym using *carer*.
For example,
```
425578005 | Caregiver able to cope (finding)|
```
* Synonym: Carer able to cope
Provide Feedback
---
# 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/general-naming-conventions/person-naming-conventions.md?ask=&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.