Sample Partitions & Aliquots
Sample partitioning creates aliquots from a received sample. Use it when different portions of one physical sample need separate handling, departments, containers, subcontractors, or analyses.
When to Partition
| Scenario | Why Partition Helps |
|---|---|
| Chemistry and microbiology need separate handling | Each aliquot has the right workflow context |
| A subcontractor receives part of the sample | Traceability remains linked to parent sample |
| Different preservation or container rules apply | Each partition can carry its own metadata |
| Parallel bench work | Analysts work independently while parent record stays connected |
Create Partitions
- Select the received sample from a list or open the sample view.
- Choose Create Partitions.
- Enter the number of partitions.
- Preview and configure each partition’s sample type, container, preservation, and analyses.
- Save.
Internal Use Partitions
Internal-use partitions can be hidden from client-facing reports where configured. Use this for prep, internal checks, or aliquots that should not appear as separate client deliverables.
State Cascading
Partitions follow normal sample workflow. The parent sample state reflects the lowest active state among child partitions, preventing release before all required aliquot work is complete.
Detach a Partition
Some labs detach aliquots that become independent primary samples, such as reference testing at another lab. Use this only when your lab process requires independent lifecycle tracking.