Hospital visitor management system: policy first, software second

A hospital visitor management system is unusual among visitor systems because three separate duties meet at the ward door: infection prevention, safeguarding of vulnerable patients, and physical security. A corporate lobby system optimises for speed; a hospital one has to decide who may enter at all, how many at once, and what must be known about each visit afterwards. The software choice follows from the policy, and most failures trace back to a policy that was never written down.

What a hospital visitor management system must support

• Ward-level rules: visiting hours, maximum visitors per patient, and restrictions during outbreaks.
• Named or nominated visitors for patients where the policy limits who may attend.
• Protected areas — maternity, neonatal, paediatric, mental health — with stricter identification and escort rules.
• A record of each visit: visitor, patient or area visited, time in and time out.
• Rapid lookup of who visited a ward during a given window, for infection contact tracing.
• Alerts or flags for visitors who are not permitted, managed under a documented safeguarding process.

Write the visitor policy before choosing anything

1. Define visiting hours and exceptions — end of life, parents of children, carers — in writing, per ward type.
2. Decide which areas require identification and who checks it.
3. Set the outbreak procedure: who can restrict visiting, how quickly, and how visitors are told.
4. Agree retention for visit records with the information governance lead, balancing contact tracing against data minimisation.
5. Name the owner of the policy and the review date.
6. Only then list what a system must do, and test products against that list.

The strictest rules belong where the risk is: an infant abduction protocol on a maternity unit is not a reason to impose ID scanning at the café entrance.

Where general tools fit, and where they do not

For the record-keeping part — a sign-in form per ward, a searchable log of visits, a quick filter for contact tracing — a general form and records tool is workable: Ettex Forms collects the sign-in on a ward tablet or via QR code, and Ettex Records holds the visit log with times and areas. Be clear about the limits. There is no identity document scanning, no badge printing, no integration with door access control or patient administration systems, and no watchlist screening. Large hospitals with protected units need a dedicated hospital visitor management system for those functions, and the procurement should say so explicitly.

Contact tracing from the visit log

• Record the area visited, not only the building — ward-level location is what tracing needs.
• Capture departure times, or tracing windows become guesses.
• Keep a phone number or email per visitor where the policy justifies it, and nothing more.
• Test the lookup before an outbreak: pick a ward and a date and time the query.
• Delete records on the agreed schedule once the tracing window has passed.

Staff, contractors and volunteers

Visitors are only one group moving through clinical areas. Contractors working on wards need their own sign-in linked to a permit to work and, often, an infection control briefing; volunteers need training evidence on record. The same log structure serves all of them, which is the argument for one register rather than three paper books kept by three departments.