Module group 01

Patient Registration (ABHA / UHID)

The problem

Front desks re-key the same patient across OPD, lab, pharmacy and billing. Duplicates pile up, ABHA stays unlinked, and consent is on paper or nowhere.

How OneCity handles it

One patient master with a hospital UHID, optional ABHA linkage, and consent captured at the counter. Every downstream module reads the same record.

Patient Registration (ABHA / UHID) workflow in OneCity ERP

What's inside

Patient Master & UHID Single demographic record with a hospital-wide unique ID. → ABHA Linkage & Verification Link and verify the patient's ABHA number with consent. → MLC & Survivor Flagging Medico-legal and Section 357C survivor handling at registration. →

Kiosk & Self-Registration Patient-side pre-registration to cut counter time.

Family & Dependant Linking Link dependants under one contact for paediatrics and maternity.

India compliance

ABDM (ABHA / PHR) — Health Data Management Policy
DPDP Act 2023 — consent & purpose limitation
Section 357C CrPC — free care flag for survivors
POCSO Act 2012 — minor handling

Integrations

ABHA / ABDM
FHIR R4 Patient
DigiLocker

Vendor integrations run in stub mode — payloads generated to spec, live posting enabled per site after onboarding.

Questions

Does registration require ABHA?+

No. ABHA is optional and linked when the patient consents. A local UHID is always generated so the patient can be served immediately.

How is duplicate registration prevented?+

The master de-duplicates on phone, name and date of birth at entry and flags likely matches before a new record is created.

Where is consent stored?+

Consent is captured against the patient record with timestamp and purpose, per DPDP Act 2023.

See Patient Registration (ABHA / UHID) on real data.

Book a 30-minute walkthrough or start free up to 5 doctors.

Start free Book a demo