> 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/body-structure/index-1/cell.md).

# Cell

## Modeling of cells expressing antigens

As the cell hierarchy is primitive, careful attention is needed to manually identify and add the appropriate supertypes.

Undifferentiated cell concepts with a single positive or negative antigen expression (e.g. cell vs. lymphocyte or blast) are immediate subtypes of 362837007 |Entire cell (cell)|.

* For example,
  * 725316009 |Cell positive for CD1 antigen (cell)| Is a 362837007 |Entire cell (cell)|

Undifferentiated cell concepts with multiple positive or negative antigen expressions should be subtypes of the appropriate cell concepts with those same single and combinations of positive/negative antigen expressions.

![](https://4060284305-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuoSxuN6wQMDYcvuq2wNX%2Fuploads%2FGBBneomeJccVH8ofk1mW%2Funknown.png?alt=media\&token=76b6c529-6d2c-4417-8a73-6ffff1ccbe82)

Differentiated cells concepts with positive or negative antigen expression(s) should be subtypes of both: a) the differentiated cell concept of differentiation; and b) the appropriate undifferentiated cell concept with the appropriate positive or negative antigen expression(s).

* For example,
  * 117507002 |FMC7+ lymphocyte (cell)| should be a descendant of 56972008 |Lymphocyte (cell)| and also 1373072009 |Cell positive for FMC7 antigen (cell)|.

{% hint style="info" %}
See also [*Naming Convention for Cells Expressing Antigens*](/snomed-ct-specifications/snomed-ct-editorial-guide/readme/authoring/domain-specific-modeling/body-structure/index/naming-convention-for-cells-expressing-antigens.md)
{% endhint %}


---

# 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 dynamically 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/body-structure/index-1/cell.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 `build a script that syncs our docs to a CMS` 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.
