-
Notifications
You must be signed in to change notification settings - Fork 134
Patient Registration Source
Every patient record in HMIS carries a Registration Source label that permanently records how the patient was first entered into the system. This is set once when the patient record is created and is never changed afterwards.
The Registration Source serves as an identity-trust indicator: a patient registered at a cashier counter by staff (Walk-in) had their identity verified in person, whereas a patient registered online or via a kiosk was self-declared and not yet verified by staff.
| Value | Label shown | Meaning |
|---|---|---|
WALK_IN |
Walk-in | Registered by counter or cashier staff during an OPD visit, pharmacy sale, or EMR entry |
INWARD_ADMISSION |
Inward Admission | New patient registered at the time of an inpatient admission |
NEWBORN |
Newborn | Baby registered via the Baby Admission workflow from the mother's admission profile |
CALL_CENTRE |
Call Centre | Registered by staff over the phone via a channel (OnCall) booking |
KIOSK |
Kiosk | Patient self-registered at a physical kiosk terminal in the facility |
ONLINE_SELF |
Online / Self | Patient portal or mobile app self-registration; also set for online channel bookings where the patient creates their own record |
THIRD_PARTY_AGENT |
3rd-Party Agent | Registration submitted by an external referral agent or online booking partner |
ON_ADMISSION_DEATH |
On Admission Death | Patient found dead and registered posthumously at the time of admission |
Patients registered before this feature was introduced will show no Registration Source badge (blank / unrecorded).
The Registration Source badge appears on:
- Patient Profile — as a labelled badge next to the patient's name and status
- Patient Edit page — read-only field in the patient details section
- Admission Profile — visible in the patient summary panel at the top of the admission profile page
The badge is read-only — it cannot be changed by any user after the patient record is saved.
The Registration Source is set automatically by the system at the point of patient creation. No staff action is required beyond choosing the correct registration workflow.
| Registration workflow | Source set automatically |
|---|---|
| New patient during OPD billing | Walk-in |
| New patient during Pharmacy cashier sale | Walk-in |
| New patient via EMR Patient Registration | Walk-in |
| New patient entered during standard Inpatient Admission | Inward Admission |
| Baby registered via Baby Admission on mother's profile | Newborn |
| New patient registered via "On Admission Death" button on the admission form | On Admission Death |
| New patient registered via Kiosk self-registration terminal | Kiosk |
| New patient registered via the Patient Portal (online self-registration) | Online / Self |
| New patient created during an OnCall channel booking (phone / call-centre) | Call Centre |
| New patient created during an Agent or Online Booking Agent channel booking | 3rd-Party Agent |
| New patient created during an OnlineSettlement channel booking (online portal booking) | Online / Self |
- The Registration Source is stored in the
registrationSourcecolumn of thepatienttable as a string enum value - The enum class is
com.divudi.core.data.PatientRegistrationSource - The legacy
selfRegisteredboolean column has been migrated: any patient withselfRegistered = truenow hasregistrationSource = ONLINE_SELF - The
selfRegisteredcolumn has been removed after migration - No configuration key is required — Registration Source is always recorded for all new patients
- VIP, VVIP and Staff Patient Status
- Add New Patient
- Kiosk Patient Self-Registration
- Admit a Patient
- On Admission Death
- Rapid Temporary A&E Admission
- Preventing Duplicate Patient Records
- Patient Chip Card (NFC/RFID) — how Registration Source is exposed to external chip-card readers