Digital Diagnostic Lab System
The whole lab day — front desk to payout — in one system.
A role-based management system for diagnostic labs and imaging centres: registration and check-in, a live worklist with server-stamped visit timing, structured reports with QR verification, PKR billing, referrer and consultant commissions, and critical-result alerts. It installs on your own WordPress server, so patient data never leaves it.
- Self-hosted
- PKR · CNIC · PMC
- Thermal + A4 print
- Works offline
- Role-based
Ships as Sehat Lab — installed, licensed and supported by Debug Nodes.
- 23
- Screens, one system
- 6
- Staff roles, API-enforced
- 145+
- Report templates
- 3
- Alert channels
What actually changes on day one
Not a feature list — the four arguments a diagnostic centre has with its own paperwork, and what the system does about each one.
A register book tells you a patient came in — never how long they waited.
The server stamps arrival, exam start and end, report-ready, hand-over and check-out. Waiting time and turnaround are measured, per modality, not guessed.
Reports leave on WhatsApp with no way for anyone to prove they are genuine.
Every finalised report prints with the consultant’s signature and a QR code that resolves to an unguessable public verification page.
Referral commissions live in a notebook and get argued about at month end.
Commission accrues the moment an invoice is paid, reverses on refund or void, and settles into the day book as an expense with a printable statement.
Nobody can say what today actually earned until the cash is counted twice.
Cash sessions close with X and Z reports, the day book shows money in against money out, and every discount above your threshold needed an approval.
One visit, six moves, nothing retyped
Each step hands the next one everything it needs — and the server, not the browser, decides what time it happened.
-
Register
One desk step, not four
Pick or quick-register the patient, search the catalog by code or name so the price fills itself, choose referrer, consultant and priority — the order and the invoice are created together, and an 80mm token slip prints.
-
Check in
The clock starts on the server
Arrival is stamped server-side, so a stale browser cannot backdate a visit. The wait timer on the worklist card is the real one.
-
Perform
Technician moves the board
Checked-in → In progress → Performed, filtered by modality. Exam start and end are stamped on transition, and the study records who performed it.
-
Report
Write from a template, not a blank page
A searchable library of pre-written imaging narratives pre-fills findings, impression and advice. Flag a critical, attach films, finalise — a radiologist’s own phrasing saves back as a reusable template.
-
Verify
Sign-off is the moment of record
Verification assigns the QR token, prints on your letterhead with the consultant’s signature, and — if the report is critical — fans out alerts to the referring doctor and your escalation list.
-
Settle
Money reconciles itself
Payment closes the invoice, commission rows accrue for the referrer and consultant, cash lands in the drawer session, and the day book balances against the expense register.
Every screen the lab runs on
Grouped the way the sidebar groups them. Roles decide who sees which group — and the API enforces it, not the menu.
Front desk
05- Dashboard Today by modality, pending reports, revenue, live average wait, plus unacknowledged criticals.
- Register & Check-in Patient, studies, referrer, priority → order + invoice + token slip in one pass.
- Worklist The day’s board by stage with live per-card timing, check-out and cancel-with-reason.
- Schedule Visit Day and week calendar for booked studies, carrying prep and fasting instructions. Optional module.
- Patients Validated PK registration, auto MRN, and a record whose timeline is the test history.
Clinical
02- Reporting The structured writer: a ~145-narrative template library, observation sections, criticals, media, finalise → verify.
- Reports library Every study report ever written, searchable — today’s and every previous day’s.
Money
08- Billing Order-driven invoices, part payments, void and refund with reason, thermal receipts in PKR.
- Cash Drawer Per-cashier sessions with open/close X and Z reconciliation reports.
- Day Book The daily cash position — money in against money out — and the expense register.
- Commissions Referrer and consultant payouts: auto-accrued, reversible, settled to a day-book expense.
- Accounts Every statement over a date range: day summary, revenue, expenses, cash flow, payroll, per-entity.
- Analytics Revenue by modality, referrer and consultant; receivables aging; wait, exam and TAT metrics; the day’s visit register.
- Purchases & Assets Procurement register: capital assets kept off the P&L, consumables tracked to on-hand stock and expiry.
- Outsourcing Studies sent to an outside lab: billed against cost, real net margin, and vendor payables.
Catalog & people
03- Services The imaging and test catalog — modality, category, code, charges, with CSV import of a legacy price list.
- Referrers & panels Referring doctors and panels with commission setup and contracted panel price lists.
- Consultants Reporting doctors, pay model, and the signature that prints on their reports.
Management
05- Staff The login accounts behind the roles, per-area write rights, and account blocking.
- Payroll Salaried staff, advances, and payslips that reconcile into the day book.
- Notifications The dispatch log — sent, failed, skipped — with the provider’s own response, retry, and channel setup.
- Audit Log The server-side mutation trail: who changed what, when, from where.
- Settings Lab identity and letterhead, modules on/off, catalogs, print designs, licence and backup.
A report a patient can verify, and a lab can defend
Reporting is the product’s centre of gravity. The writer is structured per study line — a template picker per modality, observation sections, impression and advice, a critical toggle with a note, and film or ECG attachments — and it ends in a two-stage finalise then verify sign-off, so nothing leaves the lab unsigned.
- A ~145-narrative template library, searchable, with the correct study title carried in.
- Radiologists save their own phrasing back as a reusable template.
- A4 print on your letterhead with the verifying consultant’s signature — pick the print design in Settings.
- Every print carries a QR to an unguessable /lab-report/ page; unknown tokens 404, so nothing can be enumerated.
The medico-legal question, answered before it is asked
When a consultant verifies a report flagged critical, the notifier fans out to the referring doctor and a configured escalation list across every channel at once, records the dispatch, and lights up a panel on the dashboard that stays lit until somebody acknowledges it. Who was informed, and when, is a record rather than a memory.
- Email is live out of the box; SMS and WhatsApp are built in and wait only for credentials.
- A generic SMS HTTP gateway (SendPK and Twilio presets) plus the Meta WhatsApp Cloud API.
- Failed and queued messages retry on a five-minute sweep; the log keeps the provider’s own response.
- Report-ready notices and an end-of-day owner digest run on the same machinery.
Numbers the owner can act on, not just add up
Analytics is pointed at how a diagnostic centre actually makes and loses money: revenue split by modality, referrer and consultant; panel receivables aging; and the operational triad of waiting time, exam time and report turnaround per modality. The Visit Log takes any day and lays it out one row per patient, click-through to the full timeline of that visit.
- Every statement exports to CSV and prints, so month-end is a filter, not a rebuild.
- Outsourced studies deduct their real cost, so margin is net rather than flattering.
- Assets are capitalised instead of crushing the month they were bought in.
- Step back through previous days with the arrows; filter to open, critical, unpaid or overdue-wait visits.
The parts you only notice when they’re missing
A lab system holds medical records and cash. These are the structural decisions that keep both defensible.
Roles enforced at the API
The sidebar mirrors what a role can do; the REST layer decides it. A narrow role cannot exceed its area even by calling the API directly.
The server owns clock and money
Visit timestamps, invoice maths, commission accrual and report tokens are all assigned server-side, never writable by the client.
Every mutation audited
A server-side trail records who changed what and when — including voids, refunds and discounts.
Discounts need authority
Anything above your configured threshold requires an admin or accountant, and every discount is recorded either way.
Writes survive an outage
A per-user offline outbox queues changes when the connection drops and replays them when it returns.
Your database, your server
Everything lives in tables inside your own WordPress database. There is no vendor cloud in the path.
Backup without cPanel
An admin can download a full restorable SQL dump from Settings; the file is unguessable, single-use and deleted on download.
A clean install starts empty
No demo patients, no sample invoices. Your first record is the first record.
Specifications
- Platform
- WordPress 5.8+ · PHP 7.2+ · MySQL
- Runs as
- Full-screen app in wp-admin, plus a standalone signed-in /lab/ page
- Hosting
- Your own server or shared cPanel — no cloud dependency
- Data
- Custom tables in your WordPress database
- Printing
- 80mm thermal for tokens and receipts, A4 for reports and statements
- Localisation
- PKR amounts, CNIC and Pakistani mobile validation, PMC numbers
- Notifications
- SMTP email live; SMS HTTP gateway and WhatsApp Cloud API built in
- Licensing
- Online or fully offline activation, with grace windows
- Support
- Direct from the team that wrote it — no ticket queue
What lab owners ask first
Straight answers, including the one about what the system doesn’t do yet.
It is self-hosted. The system installs as a WordPress plugin on your own hosting — shared cPanel is fine — and stores every record in your own database. There is no vendor cloud in the path, no per-record upload, and no third party holding your patient data.
The app and its runtime are served from your own server rather than a CDN, so a lab on a local network keeps working when the outside link is down. Changes made during an outage queue in a per-user outbox and replay automatically once the connection returns.
Verifying a report assigns it an unguessable token. The printed A4 carries a QR code that resolves to a public /lab-report/ page showing the verification header — patient, study, date, verifying consultant, and whether the result was critical. Full findings appear only if you switch online reports on and the report is verified. An unknown token returns 404, so the pages cannot be enumerated.
Not by default. Each of the six roles — receptionist, technician, consultant, nurse, cashier, admin — gets a focused set of screens, and commissions and analytics are admin-only until you grant them to a named account. The rules are enforced in the REST layer, so they hold even against direct API calls.
Yes, as a ledger rather than a spreadsheet. A commission row accrues the moment an invoice is paid, reverses automatically on refund or void, and can be settled per beneficiary — which posts the payout into the day book as an expense and prints a statement for the doctor.
Yes. The services catalog takes a CSV import of a legacy price list, including modality, category, code and charges, so you are not retyping hundreds of studies to get started. Panel referrers can then carry their own contracted prices on top.
Registration token slips and payment receipts are laid out for an 80mm POS thermal printer, while reports, statements and the visit register print A4. Report print designs are selectable in Settings so the output matches your letterhead.
Not yet, and we would rather say so. Today the system manages imaging and test workflows with narrative structured reporting — it is built for X-ray, ultrasound, CT, MRI, mammography, OPG, echo and ECG work. Analyte grids with units, age and sex reference ranges, and automatic high/low flagging are the next major phase on the roadmap.
Pricing depends on your lab size, the modules you want on, and whether you need data migration and staff training. Request a demo and we will walk the system against your actual workflow, then quote in writing — usually within a business day.
See it run against your lab’s own day.
Bring your price list.
A live walkthrough on your workflow — your modalities, your referrers, your rates — then a written quote, usually within one business day.