Pathology runs on chain of custody. Tissue, block, and slide: every transition between accessioning, processing, staining, and review carries a name, a time, and a record. LabRelations builds LIMS for that work, with tracking that follows specimens through internal handoffs and out to external labs and consultants without breaking. QMS sits alongside for ISO 15189 (or CAP) accreditation: documents, training, deviations, supplier qualification, and CAPA.
The technologist works in software designed for specimens, and QA works in software designed for quality. They share data where it counts (a deviation linked to the specimen that triggered it, an SOP read by the tech logged the same way as the test), but each system stays focused on the team using it.
LIMS for the specimens, QMS for the accreditation work. Used independently. Connected when the work crosses over.
Accessioning, specimen tracking, processing, staining, slide management, instrument data, results, and reporting. Chain of custody follows the specimen through every internal handoff and out to external consultants and reference labs.
Documents, SOPs, training, deviations, supplier qualification, and CAPA. Built for ISO 15189 and CAP accreditation. Audits go faster because the records the assessor wants are already organised.
Send-outs and consults are tracked as part of the specimen's chain of custody, with their own status and TAT. Results coming back land against the original case so the report is complete without manual reconciliation.
Each block, slide, and derivative is registered as its own object linked to the parent specimen. Barcoding is built in. The system knows where each item is, who handled it last, and when.
A non-conformity opens against the specimen, case, or batch that triggered it. Investigation, root cause, and CAPA all live in QMS, with the original LIMS context attached. Unrelated work keeps moving through the lab.
Workflows, fields, approvals, and reporting templates are configured in the UI. No code, no waiting on a vendor. Configuration sits inside the validation envelope, so a change isn't a re-validation project.
A mix of people who've actually worked in the industry supported by technical people for configuration needs inside the platform itself.
