Blog
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.
6 min read
A UHID — a Unique Patient Identification Number — is the single number a hospital issues a patient the first time they walk in, and never issues again. Every visit, admission, test, prescription and bill afterwards attaches to that number rather than to a name, a phone number or a file kept in a particular department.
It sounds administrative. It is actually the difference between a hospital that has one version of a patient and a hospital that has several.
What happens without one
A hospital without a shared patient number does not notice the problem on day one. It notices it in specific, recurring ways:
- The same patient exists three times — once as entered at reception, once as spelled by the laboratory, once as abbreviated in the pharmacy.
- A returning patient's history cannot be found, so tests are repeated because it is faster than searching.
- A discharge summary has to be assembled by asking each department for its part.
- Nobody can answer what a patient has actually cost, because the bill lives in one system and the treatment in another.
None of those is a software fault in the ordinary sense. Each department's system works. They simply have no agreed way to say that this patient and that patient are the same person.
What the number actually does
In TechMediz, registration issues the UHID once and everything downstream attaches to it. The out-patient visit, the admission and ward transfer, the theatre booking, the laboratory sample and its result, the scan and its report, the pharmacy issue and the bill are all facts about the same number.
That has a practical consequence worth stating plainly: there is no synchronising step between departments, because there is nothing to synchronise. A requisition raised on the ward is already about the patient the laboratory will run the test for. This is what people mean — or should mean — when they say the departments share one record.
Finding the patient again
A number is only useful if the front desk can get back to it under pressure. Search by UHID, by mobile number or by name covers how a patient actually identifies themselves at a counter: some quote the number, most quote a phone, and a few have neither.
That is why the search matters as much as the number. A unique identifier nobody can look up quickly gets bypassed, and a bypassed identifier produces exactly the duplicate records it was introduced to prevent.
What to ask a vendor
- Is the patient number issued at registration and used by every module, or does each module keep its own key?
- What does the system do when a patient turns up without their number?
- Can two records be merged when a duplicate is created anyway — because one will be?
- Does the discharge summary assemble from the record, or does someone type it?
The answers tell you whether you are looking at one system or several with a shared login. If you want to see how this works across departments, the hospital management software page sets out the full set.
See it on a live system
Tell us which departments you need first and we will show you the modules that cover them — Mescope Solutions, Salem.
The modules behind this
Keep reading
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.
Moving a hospital off paper: which department to do first
Most failed implementations are not failures of software. They are failures of sequence.
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.



