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

> Learn how test runs batch multiple test orders together for efficient processing.

## What is a Test Run?

A **test run** is a batch of test orders that are processed together on laboratory equipment. Test runs allow technicians to group similar tests from multiple accessions and run them simultaneously, improving efficiency and reducing turnaround time.

## Why Use Test Runs?

<CardGroup cols={2}>
  <Card title="Batch Efficiency" icon="layer-group">
    Process multiple samples at once instead of one at a time, saving time and reagents.
  </Card>

  <Card title="Quality Control" icon="check-double">
    Run controls and calibrators alongside patient samples to ensure accuracy.
  </Card>

  <Card title="Instrument Management" icon="microchip">
    Optimize instrument usage by grouping compatible tests together.
  </Card>

  <Card title="Traceability" icon="list-check">
    Link results back to specific run conditions, controls, and timestamps.
  </Card>
</CardGroup>

## Creating a Test Run

<Steps>
  <Step title="Navigate to Test Runs">
    From the main menu, go to the Test Runs page.
  </Step>

  <Step title="Create New Run">
    Click **New Test Run** or **Create Run**.
  </Step>

  <Step title="Select test type">
    Choose which test or panel the run will process (e.g., "CBC", "Chemistry Panel").
  </Step>

  <Step title="Add test orders">
    Select test orders from pending accessions to include in this run. bLIS typically shows compatible test orders that are ready for processing.
  </Step>

  <Step title="Add controls">
    Include quality control samples if required by your SOPs.
  </Step>

  <Step title="Start the run">
    Begin processing. The test run status changes to **In Progress**.
  </Step>
</Steps>

## Test Run Lifecycle

<Steps>
  <Step title="Created">
    Test run is set up with selected test orders.
  </Step>

  <Step title="In Progress">
    Testing is underway. Results are being entered as they become available.
  </Step>

  <Step title="Completed">
    All results for the run have been entered and the run is finished.
  </Step>
</Steps>

## Working with Test Runs

### Adding Test Orders

Test orders can be added to a run:

* **Manually** — Select specific test orders from pending accessions
* **Automatically** — bLIS may auto-assign pending test orders based on test type and instrument

### Entering Results by Run

Instead of entering results one accession at a time, you can enter results for all test orders in a run:

1. Open the test run
2. View all test orders in the run
3. Enter results for each test order
4. Results are automatically linked to their respective accessions

This workflow is especially efficient when using instruments that process many samples simultaneously.

## Quality Control in Test Runs

Many labs include QC samples in each test run:

* **Controls** — Known samples to verify accuracy
* **Calibrators** — Standards used to calibrate instruments
* **Blanks** — Negative controls

<Note>
  QC requirements vary by test type and regulatory standards. Check your lab's SOPs for specific QC protocols.
</Note>

## Instrument Integration

When laboratory instruments are connected to bLIS:

* Test runs can be sent directly to the instrument
* Results are automatically uploaded from the instrument
* Run data (timestamps, instrument ID, operator) is captured
* QC data and flags are transferred with patient results

## Viewing Test Run History

Test runs provide a complete audit trail:

* All test orders in the run
* When the run started and finished
* Who performed the run
* Which instrument was used (if applicable)
* QC results and any flags

This history is valuable for troubleshooting, quality assurance, and regulatory compliance.

## Test Runs vs. Individual Test Orders

| Aspect          | Test Run                         | Individual Test Orders     |
| --------------- | -------------------------------- | -------------------------- |
| **Efficiency**  | High — batch processing          | Lower — one at a time      |
| **Best for**    | High-volume tests on instruments | Low-volume or manual tests |
| **QC tracking** | Centralized per run              | Per test order             |
| **Typical use** | Automated chemistry, hematology  | Manual tests, send-outs    |

## Permissions

* **Create test runs** — Lab Tech or higher
* **Enter results in runs** — Lab Tech or higher
* **Modify completed runs** — May require Lab Manager permissions

## Related

<CardGroup cols={2}>
  <Card title="Test Orders Concept" icon="clipboard-check" href="/concepts/test-orders">
    Understand individual test orders.
  </Card>

  <Card title="Entering Results Guide" icon="keyboard" href="/guides/entering-results">
    Learn how to enter results.
  </Card>

  <Card title="Results Concept" icon="chart-simple" href="/concepts/results">
    Understand the result validation pipeline.
  </Card>
</CardGroup>