Features
Everything, in one list.
Grouped the way a laboratory is organised — 49 lines across 11 areas. Each one is something the product does today; WhatsApp goes out once Kliniqo's number is live with Meta.
01The counter
Registration, ordering and billing in the time it takes to say the name.
- Patient files
- Find by name, mobile number or code. Titles, -bhai and -ben understood. Age snapshot kept on every order so old reports stay right.
- Duplicate detection
- A likely match is shown before a second file is made; two files can be merged later, and a wrong merge undone exactly.
- Orders and profiles
- A profile expands into its tests; a test is found by name, code, alias or the words people use for it.
- Receipts and invoices
- A receipt with a barcode, an invoice series, GST when you charge it, a discount that needs a reason above your threshold.
- Payments and dues
- A ledger with a receipt number for every rupee, refunds, balance reminders on WhatsApp, and a day book by mode and by who took it.
- Home collection
- Bookings from the patient's phone, pincodes you serve, capacity per window, holidays, a collector's round with map directions.
02Samples
Every tube accounted for, from the needle to the bench.
- Barcode labels
- Code-128 labels per container; a scan collects or receives the tube.
- Accessioning and routing
- A received tube is routed to its department and given a shelf; a tube spanning departments is split into aliquots with their own barcodes.
- Rejection and recollection
- A rejected sample keeps its reason; a recollection follows the same order.
- Department worklists
- A printable list per bench of what is received and still to enter, urgent first.
03Results and verification
Where being wrong prints a wrong number — so the rules are strict.
- Reference ranges as rows
- By age band, sex and specimen; an age band outranks a sex match, so a newborn gets the paediatric range.
- Formulas as data
- LDL, A/G ratio, indices — evaluated by a hand-written parser, never executed code; derived values recomputed on read.
- Flags, critical values and delta checks
- L/H and panic flags, a callback log of who was telephoned and read the value back, a warning when a value moves too far from the last visit.
- Reflex rules
- When an analyte comes back abnormal or beyond a value, the follow-up test is added to the same order, once.
- Quality control
- Control materials with targets, Levey-Jennings charts, Westgard rules, review notes, and an optional hold on release while a control fails.
- Microbiology
- Culture reports with organisms and an antibiogram, not a paragraph.
04Reports
A signed report is a record. It is treated like one.
- Frozen versions
- Release freezes the whole document; portals, doctors and links render that snapshot, never live rows.
- Amendments with a reason
- A correction issues the next version marked amended; the earlier one stays, marked superseded.
- Interim and final
- A report may go out with a culture to follow; the final completes it as the next version, without an amendment.
- QR verification
- Every printed page carries a code that shows the printout is genuine without exposing anything on it.
- Your letterhead, your layout
- Signatories with signatures, a footer, pre-printed stationery or an image; a draft layout you preview and publish as a numbered template.
- The day's print run
- Every report released today, once, at its latest version, one sheet per page break.
05Analysers
An extra, quoted for your laboratory. Your own machines are connected and tested with you when you move in.
- An agent in the lab, outbound only
- Runs on a PC on your LAN, holds the serial port or the socket, and talks to us over HTTPS. Nothing is opened on your network.
- ASTM, HL7 and CSV
- Parsers written from the Sysmex, Roche and Mindray manuals and tested against their own example messages; a folder-drop mode for instruments that only export a file.
- Never loses a result
- Results are written to disk before the instrument is acknowledged, so a day-long internet outage costs nothing.
- Orphans, controls, unknown codes
- A value for a barcode we have not seen becomes an orphan you attach later; control material is quarantined; an unmapped code is shown and fixed once.
- Every raw frame kept
- Re-parse last month's traffic without a second visit to the lab; a per-device monitor shows connection, counts and the last error.
06WhatsApp
From Kliniqo's WhatsApp number, opening with your laboratory's name, once that number's connection to Meta is live. Your own number instead, for extra.
- Report-ready messages
- Utility templates with a link that opens the report; no clinical content in any message.
- Your wording, per event
- Each kind of message can be switched off or reworded, with a live preview.
- Delivered, read, or failed
- Delivery status from Meta on every message; a failed one becomes a task to telephone the patient.
- A daily cap
- A bug that messages every patient twice should cost one day, not one month.
07The patient's portal and your website
Where the patient meets the laboratory before anyone has met them.
- Sign in with mobile and date of birth
- No codes, no app. Every report the family has had here, with trends across visits and a plain-language summary.
- Booking and tracking
- Health checks and tests booked at home or in the lab; the sample's progress from collection to report.
- Sharing
- An expiring link to forward to a doctor; every open is counted and it can be revoked.
- A website of your own
- Colour, logo, hero, blocks, FAQ, reviews, gallery, your own policy pages — draft, preview and publish with versions. On your own domain when you have one.
08The doctor's portal
Every patient they referred, and only those.
- Referrals and results
- Released reports, previous values and turnaround for their own patients, across the branches they refer to.
- Recommendations
- A doctor suggests tests; the patient accepts them into a booking. Nothing is ordered or billed without the patient.
- Statements
- A monthly statement per doctor of the orders, what was billed and what is owed.
09Money and the view of the business
The owner's questions, answered without a spreadsheet.
- Revenue by day, mode and doctor
- Discounts by whom, dues, the day book, referral statements.
- Turnaround and workload
- TAT per test, work by staff member, no-shows, patient growth, health checks sold.
- Stock
- Reagents by lot with expiry, consumption, low-stock warnings and a printable stock-take that corrects each lot that differs.
- Exports
- Six CSV exports — orders and billing, payments and refunds, turnaround, bookings and home visits, the patient register and the activity log — each behind its permission and on the activity log. Anything else on request.
10Branches
A chain of laboratories and collection centres: one login, one view of the group.
- A branch opens with the parent's rate card
- A laboratory or a collection centre, with its own bill series, its own staff or shared ones, and prices pushed across the group in one click.
- The group console
- Every branch's day side by side; analytics with a branch filter.
11Security and your data
Boring on purpose.
- The database in Mumbai
- Every laboratory's rows are isolated at the database level, not only in the application.
- Permissions, not just roles
- Six roles as bundles over a catalogue of permissions, adjusted per person; a receptionist cannot see the cost column; only an owner can make an owner.
- Two-step sign-in
- An authenticator app for staff who want it, lockouts on repeated failures, sessions that end when a password or a role changes.
- An audit trail
- Every clinical write, every portal read, every export, every time the platform looked inside your laboratory — on record and visible to you.
- Data-principal rights
- A patient's data exported in one click; an erasure request an owner decides, redacting contact details while the clinical record stands.
See it with your own rate card.
Every line above is on the demo laboratory too — but the walk-through worth having is the one on your own price list and your own report.