> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blis.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Accessions

> Understand how accessions group test orders, specimens, and subjects together.

## What is an Accession?

An **accession** is the central work order in bLIS. It represents a batch of test orders for a specific [subject](/concepts/subjects) (patient or donor) and one or more samples. Each accession is uniquely identified by an **8-digit accession number**.

Accessions belong to a subject and track:

* **Subject** — The patient or donor being tested (parent entity)
* **Samples** — The biological specimens collected for testing
* **Test orders** — The specific tests to be performed
* **Organizations** — The client who requested the tests, the lab performing them, and any reference labs involved

A single subject can have many accessions over time, creating a longitudinal testing history.

## Accession Lifecycle

An accession moves through several stages from creation to final reporting:

<Steps>
  <Step title="New">
    The accession is created with subject information, requested tests, and sample details. The accession status is "new" until specimens are received.
  </Step>

  <Step title="Received">
    Samples arrive at the lab and are logged into the system. The accession status changes to "received" when specimens are checked in.
  </Step>

  <Step title="In Progress">
    Lab technicians perform the ordered tests and enter results. The accession is "in progress" while testing is underway.
  </Step>

  <Step title="Completed">
    All test results have been entered and validated. The accession is "completed" and ready for reporting.
  </Step>

  <Step title="Final">
    A report has been generated and finalized. This is the terminal state for a completed accession.
  </Step>
</Steps>

<Note>
  An accession can be **cancelled** at any stage if testing cannot proceed. Cancelled accessions do not continue through the normal lifecycle.
</Note>

## Key Fields

| Field             | Description                                                  |
| ----------------- | ------------------------------------------------------------ |
| **Accession ID**  | A unique identifier automatically assigned to each accession |
| **Priority**      | The urgency level (routine, urgent, STAT)                    |
| **Status**        | Current stage in the accession lifecycle                     |
| **Subject**       | The patient or donor linked to this accession                |
| **Creating Org**  | The organization that submitted the request                  |
| **Receiving Lab** | The lab responsible for processing                           |

## Working with Accessions

<CardGroup cols={2}>
  <Card title="Managing Accessions" icon="list-check" href="/guides/managing-accessions">
    Step-by-step guide for creating, receiving, and tracking accessions.
  </Card>

  <Card title="Test Orders" icon="clipboard-check" href="/concepts/test-orders">
    Learn about the individual tests within an accession.
  </Card>
</CardGroup>

## Data Hierarchy

Understanding how accessions fit into bLIS's structure:

```mermaid theme={null}
graph LR
    Subject[(Subject<br/>Patient/Donor)]
    Accession[(Accession<br/>Work Order)]
    Sample[(Sample<br/>Blood, Urine, etc.)]
    TestOrder[(Test Order<br/>Specific Test)]
    Result[(Result<br/>Measured Value)]

    Subject -->|has many| Accession
    Accession -->|contains| Sample
    Accession -->|contains| TestOrder
    Sample -.->|used for| TestOrder
    TestOrder -->|produces| Result

    style Subject fill:#e3f2fd
    style Accession fill:#fff3e0
    style Sample fill:#f3e5f5
    style TestOrder fill:#e8f5e9
    style Result fill:#fce4ec
```

<Tip>
  You can search for accessions by accession ID, subject case ID, or date range using the search bar (press `/` anywhere in bLIS).
</Tip>