What lab and pharmacy teams ask first.

medDule is for everyone in the care chain who is not a doctor: lab technicians, pharmacists, nurses, phlebotomists, radiographers. Every care staff role has its own view in medDule.

No. medDule can function as a standalone lab management and pharmacy platform. Integration with docDule unlocks the end-to-end automation, but it is not required to start.

The system flags values outside reference ranges in red before the report is finalised. The doctor receives an in-app alert. For life-threatening values, a push notification is sent immediately.

We support HL7 and FHIR R4 standard integration for existing LIMS. For labs without a LIMS, medDule provides the full lab management stack natively.

Yes. Reports are authored from templates with structured fields, and your existing templates are part of what we set up during onboarding.

The correction is published as a visible addendum against the original. A signed report is never silently edited.

Samples are labelled and scanned through collection and processing, so status is visible at both ends without anyone making a phone call.

Yes. A referred-out test stays on the same order, and its status is visible alongside the tests you run yourself.

The lab and the clinician are, and the software is built so neither can lose it quietly. The flag is raised before finalisation, routed to the doctor who ordered the test, and left outstanding until somebody acknowledges it.

Yes. One order lifecycle spans collection centres and a central processing lab, so a sample taken in one place and run in another is one record rather than two systems and a courier note.

No, and this is a commitment rather than a current promotion. Laboratory platforms commonly tier their price by how many instruments and client logins you may connect. Connecting an instrument you already paid for should not be a pricing tier.

Almost all of them speak ASTM: the E1381 transport with E1394 record structure, now curated as LIS1-A and LIS2-A2. That is the instrument edge. HL7 v2 carries results onward to the clinical system and FHIR R4 carries them outside it. Three layers, and anyone offering a single-layer answer at the instrument is describing something that does not exist.

Label printers speaking ZPL, TSPL or EPL, and receipt printers speaking ESC/POS. A label is a definition file rather than code, so changing a layout is a change to one file instead of a software release. Media size is treated as a real constraint: a shorter roll genuinely does not fit some labels.

No, and we will not pretend otherwise. Vitals are captured through the capture engine against a template, which covers ward and OPD work well. Direct monitor integration is a per-device programme rather than a platform capability, and we would scope it with you rather than sell it as shipped.

GS1 DataMatrix carries the product code, serial, batch and expiry in one scan, and we parse it centrally. What differs by country is which elements are mandatory and where verification happens, not the parsing, so one parser serves several regimes.

The device layer has no dependency on our servers, so labels and dispensing paperwork still print. In healthcare that is a real difference: enterprise clinical systems typically go read-only in downtime.

No. The prescription arrives digitally and you dispense against it. Inventory updates itself with nothing re-keyed.

Batch and expiry are tracked per item, with alerts raised in time to act rather than after the stock is already dead.

Both are recorded against the prescription they relate to, with the reason, so what was written and what was actually handed over are both in the record. That is where an audit expects to find them.

Yes. The pack dispensed is the batch that was scanned, so "who received this lot" is a query rather than an afternoon in the store room with a notebook.

Every dispense moves stock, cost of goods, and revenue together at the moment it happens. The pharmacy is not a separate set of numbers that meets the accounts on Monday.

Per site, per month, with the tiers published rather than quoted on a call. Early access is free while we build together, and instrument count is never part of the calculation.

Migration is part of onboarding rather than a project you buy. Panels, templates, formulary and stock come across with you, and we scope it before you commit to anything.

It is yours. Orders, verified results, templates and stock history export in open formats at any time, with no exit fee. A lab that cannot take its archive with it does not really own it.

No. The platform is designed to meet DPDP, GDPR and HIPAA obligations and is built with audit logging and role-scoped access, and we hold no certificate today. We will name and date one when it exists rather than implying it now.

The people building it, during early access. It is a small cohort on purpose, and the arrangement is that your problems reach us directly.