Product
Lab software built inside a working lab
Our lab software was not designed in a meeting room. It was built in our own lab, one real problem at a time.
Dr. Balaji Krishnan, Founder of PingMeDoc™
· Updated · 3 min read

Most lab software is built by people who have never run a lab. Ours runs every day in our own lab in Kandigai, Chennai, and each feature had to survive a real working day there before we offered it to anyone else.
The first problem: retyping
Analysers print numbers, and someone copies them into a report by hand. Every copy is a chance for a mistake. So we connected the machines. A small program on a computer in the lab listens to the analyser over HL7 or ASTM and passes results up, matched to the sample barcode. Today nine analysers and imaging devices in our own lab are connected, across haematology, biochemistry, HbA1c, X-ray, OPG and ECG.
Nothing is released without a person. The technician sees the machine's values against the right patient and test, checks them and approves. If a connection drops, results are typed into the same screen and the lab never stops. For another lab, we test a real transmission from its own machine before it pays anything.
The second problem: the report
- Reference ranges by age and sex, with out-of-range values flagged on their own and critical values prompting a callback.
- The patient's previous value printed beside today's.
- The report on the lab's own letterhead, sent to the patient on WhatsApp as soon as it is signed.
- A correction goes out as a new version, never a quiet edit, and every report carries a QR code anyone can check.

The third problem: price
Small labs cannot afford enterprise software, and they should not have to. Our lab software runs in the browser on the computer already at the counter, and there is a free plan to start. A lab can add a machine connection later, when its volume justifies it.
That is the only way we know how to build: in the place where the work happens, for the people who do it.


