A native lab stack
Order lifecycle, collection, templates, verification, signing, and addenda for labs with no LIMS to connect. Sample in, barcode on, result out.
Connecting an instrument you already own should not be a pricing tier.
An existing LIMS, the analysers on the bench, the counter, and the record a clinician actually reads. What connects, where the handover closes, and the one commercial promise we are prepared to put in writing.
Bring your LIMS, or use ours
A lab with a system keeps it and connects over standards. A lab without one gets the full stack natively, and the pharmacy counter runs on the same record either way.
HL7 v2 and FHIR R4
Standard interfaces for an existing LIMS, so results move without anyone re-keying them. HL7 v2.5.1 on the lab hop, FHIR R4 as the external contract.
Dispensing against the Rx
The prescription arrives digitally and is dispensed against as written, with the formulary and interaction check happening before the pack reaches the counter.
Stock that moves itself
Every dispense decrements the batch it came from, and reorder is driven by real consumption rather than an estimate somebody updates when they remember.
What the bench actually speaks, and what we do about it
Analyser connectivity is the integration the category monetises. It is worth being precise about the protocol stack, because anyone promising a single-layer answer is describing something that does not exist.
ASTM and LIS2-A2, the analyzer edge
Chemistry, haematology and coagulation instruments have spoken ASTM E1381 transport with E1394 records for thirty years, now curated as LIS1-A and LIS2-A2. That is the edge. HL7 v2 carries it onward and FHIR R4 carries it outside.
Instrument count is never a tier
Laboratory platforms commonly price by how many analysers and client logins you may connect. We will not: a lab that adds an instrument it already owns should not pay for the privilege of plugging it in.
GS1 DataMatrix on the pack
The pharmaceutical 2D symbology carries the product code, serial, batch, and expiry in one scan. Three jurisdictions mandate different elements and different verification hops. One parser, three topologies.
Labels from definitions
Specimen and pack labels print through ZPL, TSPL, or EPL from a definition file rather than code. A new label is a new definition, not a new release, and media size is treated as a design constraint.
Vitals, captured honestly
Nurse vitals are entered through the capture engine against a template, and they are on the doctor's screen before the patient walks in. Direct monitor links are a per-device programme, and we will not put them on a page as a platform capability.
Prints with the network unplugged
The device layer holds no domain imports, so labelling and dispensing paperwork do not stop because a router did. In healthcare that is a real difference, not an engineering nicety.
Where results go once they leave the bench
Referred-out tests
A test sent to a partner lab stays on the same order, with status visible at both ends, so a referred test is not a hole in the record until it comes back.
ABDM and ABHA
Results can be linked to the patient's national health identity with their consent, on the ABDM sandbox track, and never as a condition of using the lab stack.
LOINC for results
On the roadmap. A result is only comparable across systems if the analyte is coded, and that coded layer is the prerequisite for any analytics worth trusting.
Imaging and DICOMweb
On the roadmap. QIDO-RS, WADO-RS, and STOW-RS are the services a viewer needs. We are not claiming imaging until images move end to end.
Where the orders come from, and where the results go
docDule
Orders arrive from the consult automatically, and the critical value alert goes back to the doctor who ordered it rather than to a printer.
hospiDule
Tests and dispensing land on the visit, so the bill, the stock, and the ledger move as one transaction.
patDule
The report reaches the patient the moment it is signed, without a second trip to collect a printout.
A versioned REST API
Orders, results, batches, and dispenses are all reachable over a documented HTTP API, with events for anything that needs to react.
Export, whenever you ask
Orders, verified results, templates, and stock history export in open formats. Your report archive is yours.
Early Access
Tell us what your lab runs on
Send us your current LIMS, your analyser list, and your report templates, and we will tell you what connects over standards, what medDule provides natively, and what is honestly not there yet.
medDule works standalone. Integration with docDule unlocks the end-to-end flow but is not required to start.
Explore
More from medDule
The full picture, one page at a time.
Features
Everything medDule does, from the sample on the tray to the report in the doctor's hand.
Use cases
Who medDule is for, across the lab bench, the pharmacy counter, and the ward.
Pricing
Labs, pharmacy, and the care handoff, priced per site. Every analyzer you own connected, with no tier for it.