Follow the specimen lifecycle
Selection should cover collection, processing, aliquoting, storage, issue, return, and disposal. Every step needs location, quality, responsibility, and change evidence.
Walk representative scenarios with real operating data. A system should express local specimen types and workflows without overwriting history.
Six core capabilities
- Continuous lifecycle events from receipt through disposal.
- A precise location hierarchy from site and device to box and position.
- Structured quality events for freeze-thaw cycles, excursions, contamination, and insufficient volume.
- Organization, project, specimen-type, and action permissions with approval and audit.
- Barcode, scanner, printer, temperature, and automation integration.
- Authorized, purpose-bound search, cohort selection, request, and reporting.
Selection guidance
Demonstrate three to five frequent and error-prone workflows with site data, including bulk accessioning, scan-based moves, exception handling, and rejected approvals.
Define specimen, derivative, container, location, project, and participant relationships before migration. Preserve source and confidence when historical data cannot be verified.
Acceptance checklist
- Can a random specimen be traced through origin, processing, location, and use?
- How are duplicate scans, occupied positions, and interrupted bulk operations handled?
- Do responsibility records survive staff or organization changes?
- Can a temperature excursion identify affected devices, time ranges, specimens, and disposition?
- Do exports and APIs enforce the same permissions and audit rules as the user interface?