Pathology laboratories
Collection to signed report: barcoded custody, bench worklists, analyser interfacing, Westgard QC with lockout, autoverification, histopath and micro — a complete standalone LIS.
A complete laboratory system and a complete radiology system on one cloud platform. The patient who walks in with "CBC, LFT, chest X-ray, USG abdomen" gets one queue, one payment and one set of results — not two systems wearing one signboard.
Built for India's diagnostic centres — pathology labs, imaging centres, and the very common centre that runs both under one roof and one brand. Buy the lab floor, the imaging floor, or both.
A site declares which floors it operates, so a chain of mixed sites — processing labs, collection centres, imaging centres, combined centres — runs on one system.
Collection to signed report: barcoded custody, bench worklists, analyser interfacing, Westgard QC with lockout, autoverification, histopath and micro — a complete standalone LIS.
Booking to signed report: modality worklist, DICOM archive, zero-footprint viewer, teleradiology routing, dose tracking and AERB / PC-PNDT gates — a complete standalone RIS·PACS.
The segment this product exists for. One registration, one order across bloods and scans, one invoice, one delivery — and two production floors that each work the way their discipline expects.
Collection centres feeding a processing lab, satellite centres feeding a reading hub, camps and home collection — one custody model for specimens and studies alike.
Everything commercial is built once and serves both floors. Everything clinical is built per discipline, so a pathologist and a radiologist each recognise their own floor. Pick a group to browse the highlights.
One patient record for both floors, with duplicate detection — because a duplicate costs the prior result and the prior study at once.
The entity that joins the two floors: one requisition that may contain tests and procedures, fanning out to specimens and studies.
One catalogue, two item types — analytes and panels on one side, procedures and protocols on the other — with shared pricing and scheduling.
One invoice, one receipt, one payment for the visit. A patient billed twice for one visit has bought two products.
One contract that prices a blood panel and a chest film on the same sheet, with one reconciliation.
The cross-discipline package — a panel plus a chest film plus an ultrasound — the clearest commercial expression of one platform.
One ladder, one clock, one read-back record, two detectors. A critical potassium and a critical finding escalate identically.
The envelope: one delivery carrying whatever is signed — both reports plus an expiring image link — with partial delivery marked as partial.
One login shows both result types. The referring doctor sees their patients across both floors, with their own access log.
One relationship, one statement — a referring doctor who sends both bloods and scans has one commission arrangement and one statement, not two implementations and an argument every month.
Container and additive per analyte, label printed at the patient's side, collector and time recorded.
Custody transfer, identity verification, stability windows, coded rejection with an automatic recollection order.
What each bench runs next, batched by method and instrument, with holds visible.
Instrument and manual results, delta and absurd checks, and rule-based release without a human — inside a versioned rule set.
Template, interpretation, digital signature, immutable artefact — amendment as a new version, never an edit.
The high-volume numeric disciplines: panels, dilutions, repeats, instrument-native workflows.
A workflow that runs over days, with interim reporting at every stage.
Grossing, blocks, slides, staining — and a descriptive report with its full chain of custody.
Routes, slots, collection at the patient's side with offline capture, and a hand-over scan into custody.
Pregnancy, implants, renal function, prior reactions — and Form F before an ultrasound proceeds. Refusal blocks acquisition, not annotates it.
Started from a worklist entry by barcode, never a typed name. Dose captured at acquisition.
Each study matched to a credentialed, available reader within a turnaround commitment — checked at assignment, not trusted from cache.
Digital signature, immutable artefact, addendum as a new version carrying its reason — with every original recipient re-notified.
Durable receipt with storage commitment returned only after the cloud confirms — a scanner is never told "kept" optimistically.
Progressive streaming into a browser — first image in under three seconds, no plug-in, no install, no local copy.
Relevant priors fetched before the reader opens the study, laid out the way that reader expects.
Multiplanar reformatting served from the viewer service rather than a workstation.
Sampled double reading and discrepancy classification, with both reports retained — recorded without attaching blame.
Control charts and multi-rule evaluation with analyte-scoped lockout: a failing control holds the analyte, never the whole bench.
Scheme enrolment, cycle samples, submission, score and follow-up.
Acceptance and periodic performance testing — physics about a machine, kept as its own evidence chain.
Dose per study compared to the reference level for the protocol, with excursions explained.
Licence per radiation-emitting device. A lapse blocks acquisition on that equipment — enforced, not advised.
One Act, two entry points, one module: Form F before a covered ultrasound, the register for covered genetic testing. Both gate work.
TB and notifiable-disease submissions triggered by results, confirmed by a person, queued and reconciled — never blocking the counter.
One assembly mechanism, two packs — a laboratory pack and an imaging pack, each against its own standard and scope, never merged.
One consent conversation per visit covering both report types and the images; one withdrawal switch that revokes across the whole envelope.
Two regimes, one shell — document control, CAPA and competency are one engine; the evidence is two bodies. A combined evidence pack would fail both assessments, so the product never builds one.
One box per site carrying both protocol stacks — ASTM/HL7 to analysers, DICOM to modalities — with one certificate and one fleet console.
One store-and-forward queue, two payload classes, strict priority — so a 500 MB CT upload never delays a 2 KB blood result.
One broker answering analyser host queries and DICOM modality worklists — from cloud, or from local cache marked as cached.
One inventory covering analysers and modalities, with code and tag mapping pushed to each gateway. An unmapped code blocks, never defaults.
What this tenant bought — including which floors. The floor check is an entitlement enforced below the interface, not a hidden menu.
Transactions on one floor, stored bytes by tier on the other — both metered from day one, because storage never counted can't be counted later.
One append-only record of change and of access across both floors — including who opened a study, which leaves no other trace.
One MIS across both floors — utilisation, turnaround by floor, referrer mix, dose trend, storage growth — and never an average across disciplines.
Results, reports and studies out in a usable form, on request and on exit. Your data is yours.
A shared login over two systems bills your patient twice. A single generalised engine recognises neither discipline. This product is the honest middle: one commercial spine, two real production floors.
"CBC, LFT, chest X-ray, USG abdomen" is one order, priced on one rate card, paid once, with one GST invoice. The patient is asked for their identity once, pays once, and receives once — the three claims we hold every build to.
A pathologist never signs a radiology finding and a radiologist never signs a blood result — each signs within their own accredited scope. What's unified is delivery: one notification, one portal, one share link set. If one floor finishes first, the envelope releases partial and says exactly what's still pending.
Neither floor depends on the other — verified mechanically on every single build. Run the lab today, switch on imaging next year: same platform, same data, same logins. No migration, no re-implementation.
An analyser result is kilobytes; a CT study is hundreds of megabytes — and they share one gateway and one uplink. Strict priority partitioning keeps result posting under ten seconds even while a full imaging backlog drains. It's an acceptance-tested guarantee, not a hope.
A failing QC state locks the analyte. An expired AERB licence blocks acquisition on that machine. A covered ultrasound doesn't proceed without Form F. Every gate writes its evidence at the moment of the decision.
Degraded modes are designed per floor, and the status banner says so: "imaging transfer delayed, laboratory processing normal" — so your centre never stops taking bloods because a viewer is slow.
Kilobyte results with morning peaks; gigabyte studies with evening reading. The platform decisions below exist so both behave impeccably on one deployment.
A single box per site speaks ASTM/HL7 to your analysers and DICOM to your modalities — one certificate, one console, one upgrade path, with 72 hours of results and about a week of studies buffered through any outage.
A scanner is told its study is safe only after the replicated, versioned cloud archive confirms it. There is no application delete path for a study — a result can be re-run; a study cannot be re-acquired.
Forced row-level security per tenant, per-tenant object prefixes for pixels, and an independent floor-entitlement check below the interface. None depends on a WHERE clause being right.
A value changed without a reason and a study viewed without clinical need are both first-class audit events — with per-tenant anomaly reporting on viewing volume built in.
One notice, one consent artefact set, one withdrawal switch covering both reports and the images. Two separate products can't offer that without an integration neither would own.
Imaging is ~99% of stored bytes, so the floors are metered and priced separately — a lab-only centre never sees an object-storage line on its invoice, and tiering is a plan feature where it matters.
A lab stores PDFs; an imaging centre stores terabytes. A blended price would overcharge one and lose money on the other — so the floors are priced separately, and the combined plan is simply both, joined by one spine.
Pricing announced soon
Per centre, per month · lab floor entitlementPricing announced soon
Per centre, per month · both floors · storage metered by tierPricing announced soon
Per centre, per month · imaging floor · storage metered by tierStart with either floor and add the other any time — same platform, same data, no migration · full data and image export on request and on exit
Book a demo and follow a walk-in patient with "CBC, LFT, chest X-ray, USG abdomen": one registration, one payment, two tubes, two studies, two signed reports — and one delivery, with the audit trail behind every gate.