Sunquest is a mature, broad pathology LIS — a sensible choice for large hospital and reference labs that need a full anatomic and clinical pathology backbone. For a focused molecular genetics or NGS lab, though, molecular is one part of a wide suite, and structural changes such as a new gene panel or workflow state are typically vendor-led. A lab whose whole operation is molecular — cases, panels, runs, variant curation and sign-out — often gets to steady state faster with a system built around that specific workflow, layered over the LIS it already has.
CassianLab vs Sunquest, at a glance
Positioning reflects general market reputation as of 2026 — confirm specifics directly with Sunquest during evaluation.
| CassianLab | Sunquest | |
|---|---|---|
| System shape | Custom workflow layer / middleware over your existing EMR & LIS | Established, broad pathology LIS |
| Best-fit lab | Focused molecular genetics & pathology labs | Large hospital & reference labs, AP-heavy |
| Molecular / NGS depth | Native case, sample, panel, run, variant & family models | Mature AP; molecular a smaller part of a broad suite |
| Speed of change | Lab-controlled workflow states; new panel/status without a vendor ticket | Configurable; vendor-led for structural change |
| Implementation | Dedicated instance, typically live in weeks | Enterprise deployment and validation cycle |
| Data & hosting | Isolated instance; in-country hosting; full export | Enterprise LIS environment |
When Sunquest is the right choice
When CassianLab fits better
CassianLab vs Sunquest: questions
Is CassianLab an alternative to Sunquest?
For a focused molecular genetics or pathology lab, it can complement or partly replace the molecular-workflow side of a Sunquest deployment. Sunquest is a broad pathology LIS; CassianLab is a custom workflow layer built specifically around molecular cases, panels, runs and variant curation, and is designed to sit over an existing LIS rather than replace the whole thing.
Does CassianLab replace our LIS?
No. CassianLab is middleware — it does not replace your LIS for order entry, billing or instrument interfaces. It builds the molecular case management, sample tracking, variant curation and sign-out workflow on top of the LIS you already run, connecting via HL7, FHIR, REST and CSV.
Why do molecular labs look beyond a general pathology LIS?
Because molecular genetics workflows revolve around cases, gene panels, sequencing runs, variant curation and family relationships rather than single specimens. In a broad pathology LIS, molecular is one module among many, and structural changes are usually vendor-led — which is why molecular-focused labs often add a dedicated, lab-controlled workflow layer.