Laboratory Module
The Eruntar Laboratory Module runs the whole diagnostic workflow for clinical, hospital, histopathology and molecular laboratories: orders, collection, specimen tracking, testing, verification, reporting and billing.
It stops mistakes where they start. A mismatched tube is blocked, a failed QC run holds the release, and a report that has gone out is corrected as a new version, never overwritten.
6
disciplines, each with its own reporting
5
Westgard rules evaluated on every QC run
6
ways a report can be delivered
3
phone apps for the field and patients
Laboratory Module
Solutions
Who it is for
Clinical, hospital, histopathology and molecular laboratories
Orders
Walk-in, collection or ward, routine, urgent or stat
Specimens
Barcode matched to the patient before anything is drawn on
Results
Flagged, delta checked and held when QC fails
Sign-off
Pathologist review, exclusive final sign-off, co-signature
Reports
Versioned and hash-verified, delivered six ways
Sites
Organisation, branch and collection point
Data
Isolated by tenant in the database, audit trail hash-chained
Works in
Any browser, plus phone apps for the field
Typed at the desk, received by HL7 or FHIR, or sent from the Doctor Module. External orders wait in a holding queue to be checked before they join the workflow.
Collection is scheduled and assigned, labels print from versioned templates, and the patient's barcode must match the specimen's before the tube is accepted.
Worklists go to instruments and results come back to the right order. Aliquots keep their lineage to the parent, and storage tracks freezer, rack and slot.
Reference ranges, delta checks and critical value rules run on every result, and a failed QC run holds the release.
Pathologist review, final sign-off, then the report goes out by the channel the recipient uses, with every delivery tracked.
Disciplines
Coagulation, immunology, serology, urinalysis and toxicology run on generic panels today, and blood bank is not part of the module.
Routine and specialised panels with reference ranges, flags and calculated results.
A CBC report layout, analyzer results routed to the right order.
Isolates and susceptibility as S, I or R with MIC and zone values, against CLSI or EUCAST breakpoints.
HGVS variant naming, allele frequency and ACMG classification, with public variant database references.
CAP-style synoptic reporting, TNM staging, smart phrases and resident to attending co-signature.
Bethesda-style reporting, including HPV results and specimen adequacy.
The bench floor
These are the places where the module stops something instead of reporting it afterwards, so a busy day cannot turn into a recall.
Positive specimen identification refuses the mismatch at collection, so a mislabelled tube never reaches the bench.
The Westgard rules 1-3s, 2-2s, R-4s, 4-1s and 10x are evaluated, and a failing run blocks the results that depend on it until a corrective action is recorded.
Delta checks compare with the patient's prior result by absolute change or percentage within a time window. Releasing past one takes a supervisor override, and it is on the record.
Critical results need an acknowledgement, and when none arrives in time the escalation moves up on its own timer.
Final sign-off takes an exclusive claim, so a report is never signed in parallel from two screens.
Storage checks the zone before a rack slot is assigned, and retrieval outside the rules goes through a break-glass step that is logged.
Reports are stored as immutable, hash-verified versions. A correction is a recall and a new version with the edit history kept, not an overwrite.
Every event is chained to the one before it with a hash, and the chain is verified daily, so an edit breaks the chain.
And once a result is out
Amendments carry a reason, reference ranges are effective-dated, and every version of a report is still there.
Turnaround is tracked as events, so the orders about to breach their target are flagged while there is still time to act.
Phone apps for phlebotomists and field teams, and for patients to see their results, work from the same records.
Connections
Registered devices, signed requests, test and barcode mapping and routing rules. Failed ingestion can be replayed or ignored, and drift is watched with a forecast of downtime.
A companion connector reaches serial, TCP and file-based instruments over ASTM and HL7, with an offline queue and retry so a dropped link does not lose a result.
HL7, FHIR and the Doctor Module send orders to a holding queue, with coverage checked before they are accepted.
FHIR export, bulk export and tracked delivery by email, SMS, WhatsApp, portal, health record and print.
It watches turnaround and answers questions about your own data. It does not make clinical decisions, and we do not call it autoverification.
Orders are tracked as events, with predicted breach risk, a likely root cause and escalation before the target is missed.
Command centres for operations and quality answer questions about the laboratory's records, with the sources cited.
Personal data is masked before it reaches a model, every use is audited, usage is capped, and an approval queue sits in front of anything that writes.
Questions
A cloud-native laboratory information system for clinical, hospital, histopathology and molecular laboratories. It runs the whole diagnostic workflow in one place: orders, collection, specimen tracking, testing, result verification, reporting and billing, across one or many sites.
An LIS is built around clinical and diagnostic laboratories and patient-centred work: orders, results and reports. A LIMS is usually built around samples in research or industrial laboratories. Eruntar is a clinical and diagnostic LIS.
With positive specimen identification. The patient's barcode is matched to the specimen's barcode at collection, and a mismatch is blocked rather than warned about. Labels come from versioned templates, accession numbers are issued by the system, and tube and container compatibility is checked against the test.
Results come into the laboratory module and worklists go out to instruments over a secured API, with device registration, signed requests, test and barcode mapping, routing rules, and replay or ignore of anything that failed to ingest. Serial, TCP and file-based instruments are reached through a companion connector that speaks ASTM and HL7 and keeps an offline queue with retry, so a dropped network does not lose a result. Which instruments we have already connected is something to settle in the demo.
Abnormal results are flagged against reference ranges that go through draft, approval and effective dating. Delta checks compare a result with the patient's prior result, by absolute change or percentage inside a time window, and holding the result needs a supervisor to override. Quality control runs the Westgard rules 1-3s, 2-2s, R-4s, 4-1s and 10x, and a failed QC run blocks release. Critical values need acknowledgement and escalate on a timer.
Results can be entered singly or in batches and amended with a reason. They then go to pathologist review and final sign-off, which takes an exclusive claim so two people cannot sign the same report. Resident work can be co-signed by an attending, and reports can carry a digital signature.
Chemistry, hematology, microbiology, molecular diagnostics, histopathology and cytology each have their own reporting. Microbiology records isolates and susceptibility as S, I or R with MIC and zone values against CLSI or EUCAST breakpoints. Molecular reporting handles HGVS variants, allele frequency and ACMG classification. Histopathology has CAP-style synoptic reporting, TNM staging and co-signature. Coagulation, immunology, serology, urinalysis and toxicology run on generic panels today. Blood bank is not part of the module.
As PDF, HTML or structured data, to the doctor, the patient or another system, by email, SMS, WhatsApp, the portal, a health record integration or print. Every delivery is tracked with retries and a delivery target. Each version of a report is stored immutably with a hash, and a report that has gone out can be recalled and corrected as a new version with its edit history kept.
Yes, over HTTP. Orders arrive by HL7 ORM, FHIR ServiceRequest or Bundle, or from the Eruntar Doctor Module, and land in a holding queue to be checked before they enter the workflow. Results and orders can be exported as FHIR, including bulk export.
Yes. Organisations, branches and collection points are separate levels, and isolation between tenants is enforced in the database on every row. Collection can be scheduled and assigned to collectors with route optimisation, and there are mobile apps for phlebotomists, field operations and patients viewing their results.
Test price lists, invoices, tax, insurance splits, claims and remittance, refunds, discounts and disputes with approval flows, receivables, reconciliation and financial reports that export to CSV or JSON. Patients can pay online, and multiple currencies are supported. For a hospital that needs the full revenue cycle, the Billing Module is the larger system.
Turnaround intelligence tracks every order as events, predicts which ones are likely to breach their turnaround time and escalates them. Command centres for operations and quality answer questions about your own laboratory data, with sources cited. Voice dictation is available for reports. Personal data is masked before it goes to a language model, every use is audited, usage is capped, and it supports staff rather than making clinical decisions. We do not describe it as autoverification.
Access is by role and capability, tenants are isolated in the database, and every change is written to a hash-chained audit trail that is verified daily. Sign-in is handled by the Eruntar identity service. We do not describe the module as certified against any standard. It is built with the controls an accreditation audit looks for in mind.
Quoted for your laboratory, by the number of sites and the volume you run. Talk to us through the demo form and we will put a figure on it and plan the onboarding and migration with you.
What is included
The Laboratory Module is quoted for your laboratory, by the sites you run and the volume you handle. Every capability on this page is part of it.
Sites & volume per agreement
Quoted for the number of sites and the test volume you run.
Talk to usNeed help choosing, or running several sites? Talk to our team.
A working session rather than a slide deck: an order placed, a specimen matched to its patient, a result checked against the last one, and a report signed and sent. Tell us what you run and we will set one up. You get onboarding support and a direct line to the team building it.
Billing the whole hospital? Explore the Billing Module.
