Blog
Notes on running a hospital on one record
Written for the people who have to make the software work on a Monday morning — not for search engines, though we would not mind.
8 min read
Implementing hospital software without stopping the hospital
The software is rarely why an implementation fails. The sequence, the data and the second week are.
Read the post6 min read
Bed management: knowing which bed is free before the phone rings
A bed occupied by a patient who left at nine is a bed the hospital cannot sell and cannot admit into. Occupancy is a discharge problem before it is a capacity problem.
Read the post8 min read
How a hospital bill is actually assembled
The out-patient bill is a transaction. The in-patient bill is an accumulation — and everything that goes wrong with hospital billing goes wrong in that gap.
Read the post7 min read
HIS, HIMS, HMS and hospital ERP: what the terms actually mean
Four names for products that overlap almost completely. The useful distinction is not the acronym — it is whether the back office is inside the same record.
Read the post6 min read
What a UHID is, and why one patient number changes everything
The Unique Patient Identification Number is the least glamorous thing in hospital software and the one everything else depends on.
Read the post7 min read
NABH and NABL: the records your hospital software has to produce
Accreditation rarely fails on clinical practice. It fails on being unable to produce the record of it.
Read the post7 min read
Moving a hospital off paper: which department to do first
Most failed implementations are not failures of software. They are failures of sequence.
Read the post6 min read
Turnaround time in the hospital laboratory: what TAT actually measures
Every laboratory quotes a turnaround time. Far fewer can say which two events they are measuring between.
Read the post