The NRIC ward logbook is on its way out
Collecting full NRIC numbers by default has been restricted since 2019, and from 31 December 2026 the NRIC can no longer be used to authenticate people. A ward logbook of full NRICs no longer meets the rules.
Replace the ward reception logbook with Singpass-verified check-in. Match every next-of-kin to the right patient, hold visiting hours and per-bed caps, keep entry contactless for infection control, and give security an audit trail it can trust. Ready for the 2027 NRIC rules.
Registered Singpass provider · Free plan to pilot one ward · Setup in minutes
A hospital visitor management system records who enters your wards and which patient they are visiting. A Singpass-powered one verifies each person against Singapore's national digital identity at the point of entry, matches them to a specific patient, and holds your visiting-hour and visitor-cap policies. The result is a contactless, government-verified record of everyone on the ward, instead of a paper logbook of self-written names and exposed NRICs.
Next-of-kin write whatever name they like. Full NRICs sit on the page for the next visitor to read. Handwriting is illegible, caps go uncounted, and when security needs to know who was on the ward last night, the answer is five smudged lines. The shared pen and clipboard are an infection-control problem on their own.
Collecting full NRIC numbers by default has been restricted since 2019, and from 31 December 2026 the NRIC can no longer be used to authenticate people. A ward logbook of full NRICs no longer meets the rules.
One flow for your team, one for the visiting family. The same Singpass tap millions already use.
Create a location for every ward or entrance. Set its visiting hours and visitor cap per bed.
Ask for the patient being visited and relationship. Validate against your ward list if you connect the API.
Print the QR for each ward reception or entrance. Each location gets its own code and its own log.
See who's on each ward in real time. Search, filter, and export verified records anytime.
The visiting family member scans the code at ward reception with their own phone.
They authenticate with Singpass and confirm which patient they are visiting.
Identity confirmed, matched to the patient, checked against the ward cap. No pen, no logbook.
Not a generic sign-in tool with Singpass bolted on. SingVMS is built around verified identity and the way hospital wards actually run.
At check-in the visitor states who they are visiting and the ward. SingVMS pairs their Singpass-verified identity with that patient, so reception and security see a confirmed person against a specific bed, not a scribbled name.
Each ward carries its own visiting windows and a limit on visitors per patient. Check-ins outside the window, or beyond the cap for that bed, are flagged for staff instead of slipping through unnoticed.
Visitors scan and authenticate on their own phone. No shared pen, logbook, or reception touchscreen. During an outbreak you can tighten caps, close a ward to visitors, or add a screening question from the dashboard in seconds.
Every entry is a verified identity with a timestamp, ward, and patient reference. Search it, filter it, export it. When an incident needs review, you have a real record of who was on the ward, not five illegible pages.
The SingVMS API pushes verified check-in events to your patient administration, registration, and security systems through REST endpoints and webhooks. Validate patient references against your live admissions list at check-in.
Consent is built into the Singpass flow and only a masked NRIC is stored. From 31 December 2026, organisations must stop using full NRIC numbers to authenticate people. Verified Singpass check-in meets that rule out of the box.
SingVMS handles the Singpass FAPI and MyInfo integration. Your ward gets verified fields, plus the visit fields you need, with no API keys or engineering on your side.
From evening ward visits to vendor access, the same verified check-in runs wherever identity matters on your site.
Evening visiting hours bring a rush of next-of-kin to reception. Verified check-in matches each one to a patient and holds the visitor cap per bed without a queue at the counter.
A&E moves fast and visitors arrive under stress. A three-second Singpass check-in records who is accompanying a patient without slowing triage or clinical staff.
These wards run the strictest caps and the tightest infection control. Contactless entry and per-ward limits are enforced at check-in, and access can be closed instantly during an outbreak.
Verified identity at the door supports patient registration and cuts duplicate records. The same Singpass flow that checks in a visitor can prefill a registration form from MyInfo.
Biomedical, facilities, and IT vendors need auditable site access. Verify who they are before they reach clinical areas, and keep a record for security and compliance.
One dashboard across every ward and entrance. Search verified check-ins by patient, ward, date, or person, and export the log when an incident or audit calls for it.
It's 7pm on a general ward. Visiting hours run until 8:30pm, and the policy is two visitors per bed. A daughter arrives to see her father in bed 14. She scans the QR code at reception, taps Singpass, and confirms she is visiting that patient. Three seconds later she is checked in: a verified name, a masked NRIC, and her relationship to the patient, all against bed 14.
Her brother is already at the bedside. When a cousin turns up and checks in for the same bed, the system flags that the cap is reached, so the nurse at reception has a clear prompt instead of a guess. Nobody touched a shared pen. Nobody read anyone else's NRIC off a page.
At 9pm a ward manager glances at the dashboard and sees exactly who is still on the ward and which patient each visitor came for. If an incident is raised the next morning, security exports the verified log for that ward and that window in one click. The same night on a paper logbook would be a column of half-legible names, a few of them fake, and no way to prove who was actually there.
The dimensions that matter for a hospital ward, compared directly.
| Dimension | Ward paper logbook | Generic digital VMS | SingVMS (Singpass) |
|---|---|---|---|
| Identity verification | None. Whatever the visitor writes. | None. Self-declared on a form. | Government-verified through Singpass. |
| Next-of-kin to patient match | A name and a ward number, unchecked. | Typed in, no verified person behind it. | Verified visitor paired to a specific patient. |
| Visiting-hour and cap enforcement | Manual, at the counter, easily missed. | Varies by vendor, rarely per-ward. | Per-ward windows and per-bed caps, flagged automatically. |
| Infection control | Shared pen and logbook at reception. | Shared tablet or kiosk touchscreen. | Contactless. Visitor uses their own phone. |
| Audit trail | Paper only. Often illegible. | Digital, but unverified entries. | Verified, timestamped, searchable, exportable. |
| PDPA / 2027 NRIC rules | Full NRICs exposed to later signers. | Depends on the vendor. | Masked NRIC only. Ready for the 2027 rules. |
| Integration with patient systems | None. | Rare. | REST API and webhooks. |
Start free at a single ward, then move to a plan sized for your volume and sites. Enterprise covers unlimited wards, white-label, extended MyInfo fields, and a dedicated SLA.
Test SingVMS at one location. Live in under 5 minutes, no credit card.
For small teams that need verified visitor details and predictable pricing.
For growing businesses that want their own branding and more volume.
Common questions from facilities, operations, and security teams.
A hospital visitor management system records who enters your wards and which patient they are visiting. SingVMS uses Singpass, Singapore's national digital identity, so every next-of-kin and visitor is verified against government records instead of writing a name in a logbook. Reception and security see a real, searchable record of everyone on the premises.
At check-in the visitor selects or enters the patient they are visiting, and the ward. SingVMS pairs their Singpass-verified identity with that patient reference, so the record shows a confirmed person against a specific bed. If your ward system exposes an API, the patient reference can be validated against your live admissions list rather than typed by hand.
Yes. Each ward can carry its own visiting windows and a cap on how many visitors are allowed per patient at once. Check-ins outside the window, or beyond the cap for that bed, are flagged for staff instead of being waved through. Rules are set per location, so a general ward, an isolation ward, and an ICU can each run different policies.
Visitors scan a QR code and authenticate on their own phone. Nobody shares a pen, a logbook, or a reception touchscreen. During a surge or an outbreak you can tighten caps, close a ward to visitors, or add a screening question at check-in from the dashboard, and the change applies to that ward immediately.
SingVMS keeps a manual check-in fallback for anyone without Singpass, including foreign family members and tourists. They enter their details, including passport number, through a digital form. These entries are clearly marked as self-declared on the dashboard, so staff always know which check-ins are Singpass-verified and which are not.
Through Singpass, SingVMS receives the verified name, a masked NRIC (for example S****567A), date of birth, and mobile number, plus any visit fields you configure such as relationship to the patient. The full NRIC is never stored. Only a masked version and a secure hash are kept, and data handling follows PDPA standards.
Yes. SingVMS exposes REST endpoints and webhooks, so verified check-in events can be pushed to your patient administration, registration, or security systems in real time. You can validate patient references against your admissions list at the point of check-in and export visitor records for incident review or reporting.
SingVMS has passed GovTech's security assessment and is a registered Singpass relying party, so the integration is already live and approved. You register an account, create each ward or entrance as a location, set its visiting rules, and print the QR code. Setup takes minutes, not the months a Singpass build from scratch would take.
Pilot one ward free with 50 verified check-ins. For a hospital-wide rollout, talk to us directly.