Skip to main content

​
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?

Batch Efficiency

Process multiple samples at once instead of one at a time, saving time and reagents.

Quality Control

Run controls and calibrators alongside patient samples to ensure accuracy.

Instrument Management

Optimize instrument usage by grouping compatible tests together.

Traceability

Link results back to specific run conditions, controls, and timestamps.

​
Creating a Test Run

1

Navigate to Test Runs

From the main menu, go to the Test Runs page.
2

Create New Run

Click New Test Run or Create Run.
3

Select test type

Choose which test or panel the run will process (e.g., “CBC”, “Chemistry Panel”).
4

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

Add controls

Include quality control samples if required by your SOPs.
6

Start the run

Begin processing. The test run status changes to In Progress.

​
Test Run Lifecycle

1

Created

Test run is set up with selected test orders.
2

In Progress

Testing is underway. Results are being entered as they become available.
3

Completed

All results for the run have been entered and the run is finished.

​
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
QC requirements vary by test type and regulatory standards. Check your lab’s SOPs for specific QC protocols.

​
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

​
Permissions

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

Test Orders Concept

Understand individual test orders.

Entering Results Guide

Learn how to enter results.

Results Concept

Understand the result validation pipeline.