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

# Specimen

<mark style="color:$danger;">**This Editorial Guide is used for Education Purposes Only. It is used in the Authoring Courses and Certifications. It is based on the January 2026 Editorial Guide.**</mark>

| Definition                                                                     | Examples  |
| ------------------------------------------------------------------------------ | --------- |
| Entities that are obtained (usually from patients) for examination or analysis | 384744003 |

Specimen concepts can be defined by attributes which specify the:

* Normal or abnormal body structure from which they are obtained
* Procedure used to collect the specimen
* Source from which it was collected
* Substance of which it is comprised

## *Specimen* not *sample* in FSN

The Fully Specified Name for Specimen concepts should include the term *specimen,* not *sample*. This also applies to descriptions in other hierarchies in addition to the Specimen hierarchy.

Because of the differentiation between specimen and sample in some domains (e.g., biobanking), an additional description using the word *sample* should not be added to the specimen concept.

{% hint style="info" %}
Legacy concepts exist in SNOMED CT that contain both *specimen* and *sample* in descriptions. Those are being retained for historical purposes.
{% endhint %}

## Combined specimens and pooled specimens

A *combined specimen* refers to more than one specimen taken from the same subject and combined in a single container to form a single specimen. A *pooled specimen* refers to specimens taken from multiple subjects and pooled (mixed) together into a single container. SNOMED CT concepts will include the appropriate term in the FSN and will not treat *combined specimen* and *pooled specimen* as synonymous.

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