NGS LIMS that still knows which patient or study a FASTQ came from
Extraction, library, pool, and run are different objects. LabPi keeps the parent specimen attached through every one of them.
- CAP / CLIA where clinical
- HIPAA for identified specimens
- GLP for regulated studies
- Consent flags
What these labs track in LabPi
Sample types and work products for this lab, not a generic tube list.
- gDNA and RNA
- Libraries
- Pools
- Single cells
- FFPE
- cfDNA
How the work actually runs
Extraction batch
Yield and quality metrics stay on the extract, and failed extracts do not proceed into library prep unnoticed.
Library and index
Index assignments are unique inside the pool. LabPi flags a collision before the run is queued.
Run to pipeline
The sequencing run record points at the pool members and can hand identifiers to the analysis pipeline by API.
LabPi capabilities this lab uses
Each card opens the product page for that capability, so you can see the feature behind the industry claim.
Parent-child lineage
Specimen, extract, library, and pool remain one tree.
View capabilityStep-by-step prep
LES steps for extraction and library kits, with lots recorded as they are used.
View capabilityELN for method development
Assay development notes sit next to the samples they used.
View capabilityAPI to analysis
Webhooks and REST so the pipeline is not fed from a sample sheet export.
View capabilityRelated labs
See LabPi on a genomics workflow
A 30-minute demo uses your sample types, your reports, and the regulations on this page.