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
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.
Test Run Lifecycle
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:- Open the test run
- View all test orders in the run
- Enter results for each test order
- Results are automatically linked to their respective accessions
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
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
Test Orders Concept
Understand individual test orders.
Entering Results Guide
Learn how to enter results.
Results Concept
Understand the result validation pipeline.