Not a LIS

PCR Lab Pro is not a LIS. Replacing your LIS is not the offer.

The reporting and release platform for molecular labs.

Your LIS holds the order and the accession. Your instrument makes the numbers. We are the layer in between the finished run and the signed report — and we’d rather be excellent at that span than mediocre at all of it.

Open the demo labFictional end to end. Nothing you do there leaves your browser.How it works
  1. YOUR LIS

    Holds the order

    stays
  2. YOUR INSTRUMENT

    Makes the numbers

    stays
  3. PCR LAB PRO

    Makes the report you’re willing to sign

  4. RELEASED REPORT

    A PDF on your letterhead

What your LIS does that we don’t, on purpose.

Order entry from the clinic. Specimen accessioning at receipt. Billing to payers. Instrument interfaces. Naming what we don’t do is what makes the rest of this page believable.

You will see orders and accessions inside the product. The line that holds: we hold them as report context, not as the record of the encounter.

What we do that a LIS module doesn’t.

“How is this different from our LIS?”

Short answer: your LIS is the record of the encounter. We’re the record of the report.

What we don’t touch, and don’t want to. We don’t register patients. We don’t take orders from your clients. We don’t accession specimens — your LIS does that, and it’s the accession of record. We don’t talk to your EMR, and we don’t send HL7 anywhere. We don’t do payer billing, claims, or inventory. We don’t hold your legal record. If your LIS went away tomorrow, we would not be able to stand in for it, and we’d be the first to tell you so.

What we do. We start from a file your LIS already knows how to produce — the order manifest, exported as CSV. From there we own the part your LIS was never really built for: the run and its plate, the controls, the call on every target against the CT window your lab validated on your instrument, the approval, the release, and the report itself — a branded PDF on your letterhead, with your director’s name, your license number and your template. Then the parts that only show up later: the corrected result that has to become version 2 with a reason and a name on it, and the stewardship section a clinician actually reads.

You will notice we hold orders and accessions too. We do. A report has to be bound to the specimen it describes, or it isn’t a clinical document. But we hold them as the report’s context, not as the system of record — which is why the binding between an order, a run and a specimen is read-only in a correction. A correction fixes a measurement. It can’t quietly reassign a sample to a different patient.

Why not just use the reporting module in the LIS? Sometimes you should. If your LIS produces a report your director is happy to sign, and corrections and stewardship are handled, you don’t need us. Labs come to us when the report is the part that’s still done by hand — when the LIS export goes into a spreadsheet, the spreadsheet goes into a Word template, and the approval is an email. That’s the stage we replace, and it’s the stage that costs you the most on a Friday afternoon.

What it costs you to find out. Nothing your LIS vendor has to approve. There’s no interface project, no HL7 spec, no change request. CSV in, PDF out — and your first released report is free.

How they meet: one file.

The interface between us and your LIS is a CSV export you already have: the order manifest your LIS exports. Upload it, review the parsed accessions, and the rest happens here.

See the manifest format — with a sample manifest and result file →

One more name you might know it by.

If you know this layer as the legacy “Molecular Infectious” reporting module, this is what replaced it — the app calls it Test Panels now.

The rest of the answer is in the demo lab.

An established lab, fictional end to end — runs, plates, accessions and released reports already in place. Open a run, try the release gate, read a report on the letterhead, and see whether the span we claim is the span you’re missing.

Open the demo labFictional end to end. Nothing you do there leaves your browser.How it works