Skip to content

Compared with your ELN or LIMS

Should your bio-IT team build the qPCR analysis?

A bio-IT team can program qPCR into your LIMS. Clarida brings the plate rules and the methods ready-made, and files carry the results back.

4 in your first month, then 2 a month. No card.

You keepSamples, signatures, the release
You addqPCR methods your team doesn’t code
On this page

When is your ELN or LIMS the better home?

Platforms that combine both, like Labguru and Revvity’s Signals Notebook, count here too; Benchling has its own page.

Your samples, stock and requests live thereEvery result lands beside them: LabWare tracks specimens end to end
Your protocols are versioned thereSciNote keeps a version history its owner publishes; eLabFTW starts from a template
A liquid handler fills your platesIn Sapio’s LabCorp setup, the LIMS builds the plates, robot instructions and worklists
Your lab needs signatures and audit trailsLabWare has both as standard; SampleManager asks for a reason at each change
The assay is a fixed test with a release stepDiagnostic labs run qPCR this way: Sapio lists qPCR and dPCR among the algorithms its LIMS runs at LabCorp
Your bio-IT team codes in the platformLIMS Basic, Sapio’s Python library, Labguru’s code blocks or LabArchives’ custom widgets
Data from every cycler must flow into one systemBenchling connects over 200 instruments, Dotmatics Luma more than 100
You want a free notebook you hosteLabFTW: open source, with no features behind a paywall

Does your LIMS team now maintain qPCR code?

  • If the analysis is one person’s code, whoever inherits it has to learn it before changing anything.
  • Every platform upgrade means a code review. LabWare consultants advise reviewing LIMS Basic code at each new version, and Sapio’s Python library has to match the platform version.
  • The method stopped at ΔΔCq. MIQE 2.0 recommends against relying on it, and efficiency per target, several reference genes and error carried to the result are code someone has to write, test and keep.
  • The code needs assessing for as long as it lives. EU GMP Annex 11 asks custom software for formal assessment over “all the life-cycle stages of the system” (§4.6), and puts each edit through change control.
  • The first result can be a year away. A LIMS implementation takes from a couple of months to a year or more, says the consultancy CSols, and more customization means longer testing.
  • If the Cq values go to Excel for analysis, the LIMS only stores them.

Side by side

What you needBuilt in your ELN or LIMSClarida
Define
Protocols and the plan
Details
Stronger: Versioned protocolsProtocol templates with a version history, published by their owner; experiment templates for what you often runGoal and presetBackground, goal and linked papers; a preset brings the settings set and the steps
Design
Samples, stock and requests
Details
Stronger: System of recordSamples, stock and requests tracked end to end, linked to every resultqPCR onlySamples and assays per experiment and in a shared library, with their source positions
The plate layout
Details
Plates, worklistsPlate builds, robot instructions and worklists, configured for your workflowLaid out for youFrom your grouping and fill rules, replicates side by side for a multichannel pipette, the reason shown
Execute
Mixes and volumes
Details
Yours to buildA form or calculator widget someone writes and keeps upStronger: Worked outEvery mix per reaction and in total, surplus included, recomputed when the design changes, until the runs are ready
Import
qPCR run files
Details
Via a parserConnectors such as Luma and LabStation read instrument output; the curves depend on the parserStronger: Read nativelyCFX, QuantStudio, LightCycler 480, Rotor-Gene and RDML files with raw curves, matched to your plate
Analyze
qPCR methods
Details
Yours to writeIn the platform’s own code: LIMS Basic, Python or code blocksStronger: Built inEfficiency per target, several reference genes with geNorm and NormFinder, error carried to the result
Checking the math
Details
Your testsCustom code needs a life-cycle validation process that your team runsStronger: Published, testedBuilt on the published qBase model; NormFinder checked against its authors’ Excel add-in, geNorm’s M values match qbase+
Report
The result on record
Details
Beside the sampleStored with the sample it came from; reports built in the LIMSReport, Excel, RDMLA PDF or HTML report; the whole experiment written into your Excel notebook; RDML with the raw curves
Throughout
Audit trail and signatures
Details
Stronger: Part 11 featuresLabWare has signatures and audit trails as standard; SampleManager keeps old and new values, with a reason; SciNote offers a Part 11 add-onDecisions storedSetting changes, automatic exclusions and accepted QC deviations, with who and when; no e-signatures
After a software update
Details
Code to recheckCustom code is reviewed at each upgrade; add-on libraries match the platform versionStronger: Maintained for youMethods kept current by Clarida; a saved analysis never changes after an update
Changing a method
Details
Change controlThrough your change process and user roles, then revalidationVersioned settingsNamed settings sets freeze once used; each experiment keeps its own copy; owner, admin and member roles
Connecting the rest of the lab
Details
Stronger: APIs, connectorsBenchling lists over 200 instruments; APIs such as eLabFTW’s serve scripts and integrationsFilesExcel, CSV and RDML in; Excel, RDML and a PDF report out (each table as CSV); no public API
First result
Details
A projectAn implementation takes months to a year or more, then the qPCR codeStronger: No projectStart free and import a run file; nothing to install

marks the stronger tool for that need.

In short

Stronger in your ELN or LIMSProtocols and the plan · Samples, stock and requests · Audit trail and signatures · Connecting the rest of the lab
Stronger in ClaridaMixes and volumes · qPCR run files · qPCR methods · Checking the math · After a software update · First result
A drawThe plate layout · The result on record · Changing a method

How do you check it on one run?

  • Export one finished run and its sample list. From the instrument and the LIMS, as files; nothing gets connected.
  • Put the workbook beside the LIMS record. It holds the plan, the data, the settings and the results.
  • Ask your QA what they would need to see. The settings it started from, the stored decisions and the frozen analysis are what Clarida can show.

What stays in your LIMS, and what moves?

Keep in your LIMSSamples, stock, signatures and the release, beside every result
Keep in your ELNThe protocol; Clarida writes the experiment into your lab’s Excel notebook once you attach it
Bring to ClaridaSample and assay lists as Excel, CSV or text, into Design with their source positions, then the run file
Work as a teamOwner, admin and member roles in one workspace, on a paid plan; colleagues can join by their email domain
What does not connectNo direct link to an ELN or LIMS and no public API: files carry the data both ways (RDML, Excel, a PDF report)

Frequently asked questions

Could your bio-IT team build this instead?

Yes, it could. Much of the effort comes after the first version: plate layout rules and mix volumes, efficiency per target, several reference genes and error propagation, each tested, rechecked after every platform upgrade, and kept alive when its author leaves. In Clarida that work is done and kept up by us, which leaves your team’s time for the integrations specific to your lab.

What does Clarida add if your LIMS already makes plates and worklists?

For a liquid handler, keep the LIMS worklist: Clarida writes none. Where plates are filled by hand, Clarida lays them out by qPCR rules (grouped by assay or sample, replicates side by side for a multichannel pipette), works out every mix with its surplus and guides the filling, one stage at a time. Notes left on a well come back beside its measurement when you analyze, and the run file is matched to the plate you filled.

Does Clarida have electronic signatures?

No. That is a row your LIMS wins. Clarida stores each setting change, each automatic exclusion and each accepted QC deviation with who and when, keeps imported data unchanged, and freezes saved analyses. A LIMS with Part 11 features does not settle compliance by itself either: eLabFTW’s documentation says of its own ELN that it depends on how the system is configured, validated and used.

Can Clarida release a pass or fail result?

No. Clarida calls each sample per target, from a cut-off you set per assay, for research use; the release decision stays in your LIMS.

What does a first try cost beside your LIMS?

Nothing, and no system gets connected. Clarida’s free plan: 4 experiments in your first month, then 2 a month. No card.

Sources

Each source with the day we last checked it. Something out of date? Tell us.

Checked

No integration project before the first result.

Import a run file, then save the Excel workbook to your ELN. Your LIMS stays as it is. 4 experiments in your first month, then 2 a month. No card.

Other comparisons

All comparisons
  • Spreadsheets

    You keep
    Your own formulas, Prism for figures
    You add
    Plate, mixes and analysis, linked
  • Instrument software

    You keep
    The run, the protocol, signed records
    You add
    The plan, and runs from four makers
  • Dedicated qPCR software

    You keep
    GenEx for PCA and replicate planning
    You add
    Plate layout and mixes, from your lists
  • R and Python scripts

    You keep
    New methods, the wider pipeline
    You add
    The plan, the mixes, published methods
  • Benchling

    You keep
    The record, stock and sign-off
    You add
    The qPCR layout, mixes and method