> ## 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.

# Test Orders

> Learn how individual tests are ordered, organized, and tracked within accessions.

## What is a Test Order?

A **test order** is an individual test to be performed as part of an [accession](/concepts/accessions). Each test order references a specific **test specification** — the definition of what the test measures, its expected result type, and reference ranges.

Test orders can also be grouped into **panels** — predefined collections of tests that are commonly ordered together (for example, a "Complete Blood Count" panel includes multiple individual test measurements).

## Test Order Status

Test orders don't have an explicit status field. Instead, their state is derived from the results and other factors:

* **Active** — The test order exists and has not been cancelled
* **Has Results** — One or more results have been entered for this test
* **Validated** — All results for this test have been validated by a second technician
* **Finalized** — Results have been approved and locked for reporting
* **Cancelled** — The test order has been cancelled and will not be completed

The status of a test order's results determines whether it's ready to include in a report. See [Results](/concepts/results) for more details on the result validation pipeline.

## Panels vs. Individual Tests

<Tabs>
  <Tab title="Panels">
    A **panel** is a group of related tests ordered together. When you order a panel, bLIS automatically creates individual test orders for each test in the panel.

    Common examples:

    * Complete Blood Count (CBC)
    * Basic Metabolic Panel (BMP)
    * Liver Function Panel
    * HLA Typing Panel
  </Tab>

  <Tab title="Individual Tests">
    You can also order **individual tests** outside of a panel when only a specific measurement is needed. Individual tests follow the same lifecycle as panel tests.
  </Tab>
</Tabs>

## Reflex Testing

Some test results may automatically trigger additional tests based on predefined rules. This is called **reflex testing**. For example:

* An abnormal screening result may trigger a confirmatory test
* A result that falls outside expected ranges may trigger a repeat test

<Note>
  Reflex tests are configured by your lab administrator. When a reflex test is triggered, you'll see it appear as a new test order linked to the original accession.
</Note>

## Key Fields

| Field           | Description                                           |
| --------------- | ----------------------------------------------------- |
| **Test Name**   | The name of the test being performed                  |
| **Panel**       | The panel this test belongs to (if applicable)        |
| **Status**      | Current stage in the test order lifecycle             |
| **Result Type** | The kind of result expected (numeric, text, or other) |
| **Sample**      | The sample this test is being performed on            |

## Related

<CardGroup cols={2}>
  <Card title="Results" icon="chart-simple" href="/concepts/results">
    Learn about entering and managing test results.
  </Card>

  <Card title="Accessions" icon="flask" href="/concepts/accessions">
    Understand the accession that contains test orders.
  </Card>
</CardGroup>