Walk-ins and appointments in one token stream per department, the way an OPD actually runs
Reception Module
BetaThe Eruntar Reception Module is front-desk software for clinics and hospitals: patient registration with duplicate detection, multi-doctor appointment calendars, walk-ins and appointments in one OPD token queue, admissions coordination, visitor passes and desk payments.
A duplicate is caught before the record exists, a clash is caught before the patient arrives, and every action at the desk is audited.
3
ways to register: quick, complete, emergency
1
queue for walk-ins and appointments alike
30 min
of waiting before the desk is alerted
62
permissions, eight of them off by default
Reception Module
Solutions
Who it is for
The front desk of a clinic or hospital
Works with
Our Doctor, Nurse and Billing Modules, or on its own
Registration
Quick, complete or emergency
A duplicate
Caught before the record is created
The queue
Walk-ins and appointments, one token stream
Admissions
Five visible steps. The ward is told automatically
The money
Cash, card or UPI, with a receipt
The record
Append-only, written in the same transaction
Connects to
HL7 v2 ADT and SIU, FHIR R4
Availability
Beta, in any browser
Today's appointments, the walk-ins, the no-shows and the waitlist on one screen, with the alerts that need a hand first.
Quick for a moving queue, complete for full demographics, emergency for a patient with no name yet. Duplicates are caught before the record exists.
Every doctor on one calendar. Click an empty slot to book, drag a card to move it, and a double booking is refused.
Check-in creates the encounter and issues the token. Call the next patient, recall one, or move a position, and the board keeps up.
An admission moves through five visible steps with the ward told automatically. At the end of the day, the totals and the reports are already there.
The record
That sentence is from the module's own compliance documentation. These are the places where the desk will not let a busy morning turn into a bad record.
Name, date of birth, phone and identifiers are checked before the record is created. A likely duplicate is blocked unless it is deliberately forced, and the forced flag goes into the audit.
A merge is a request that someone else approves before it runs, never a silent overwrite. A merge already decided cannot be decided again.
Admissions move in order: requested, verifying, bed requested, nurse notified, admitted. A step cannot be skipped, and a finished admission cannot be edited.
When Billing is installed the desk refuses the payment and shows status only, so there is never a second source of financial truth.
A suggestion is not a write. Someone at the desk accepts it or does not, and if the AI platform is unavailable the desk keeps working manually.
This one is advisory. The desk can override a conflict when it is the right call, and the override is recorded with who made it.
The public queue page shows a code, a position and a time, never a name, a department or a reason. A bad link and an expired link look the same.
And once the patient is checked in
Checking a patient in creates the encounter and validates arrival, outstanding tasks and duplicates in one motion. Nobody re-keys anything.
The board refreshes itself with live wait times. Anyone waiting more than thirty minutes becomes an alert that links straight to the fix.
Every write lands in an append-only audit, in the same transaction as the change: who, what, before and after. The database enforces it.
Nothing changes patient data on its own. A suggestion is reviewed before it is accepted, every AI interaction is audited and metered, and if the AI platform is ever unavailable the desk simply keeps working manually.
Identity documents read into the registration form for review, with suggested completions and inconsistency checks as the record is built. Premium.
Similarity scoring on top of the deterministic duplicate engine, and translation of patient-entered and administrative text at the desk. Premium.
Congestion and wait-time forecasts with suggestions for balancing the departments, and workflow recommendations for the desk. Enterprise.
Questions
It is front-desk software for clinics and hospitals: the administrative entry point of the building. It covers patient registration, appointment scheduling, walk-in and queue management, check-in, admissions coordination, visitor management, desk payments and printing, with every action audited.
Yes, and in the same queue. Walk-ins get a token alongside appointment arrivals in one stream per department, which is how an outpatient department actually runs. A walk-in can be converted into a proper appointment in one step without re-entering the patient.
Each department runs a live token queue. A token is waiting, called or arrived, and ends completed, missed or cancelled. Staff call the next patient, recall one, move positions and change priority from the board, and the patient's own view goes from issued to approaching to called. On Standard the queue is first come, first served. Premium adds priorities with estimated waits, and a queue that has anyone waiting more than thirty minutes raises an alert.
Yes, before they exist. A deterministic engine checks name, date of birth, phone, national ID, passport, insurance and the health ID as a record is being created, and refuses a likely duplicate unless the receptionist deliberately forces it, in which case the forced flag is written to the audit. Merging two records is a request that someone else approves before it runs.
Yes. The calendar spans every doctor with day, week and month views and drag-and-drop rescheduling. A double booking is refused unless it is explicitly overridden, and the override is audited. Availability reads live from the Doctor Module, and if that link is ever down scheduling degrades gracefully instead of stopping.
Yes, on Premium. Patients check in for an appointment, confirm it or take a queue token on a kiosk with large touch targets and no administrative functions exposed. It ships in English, Finnish and Arabic with right-to-left support, resets itself after inactivity and has a privacy screen, so it is safe to leave in a lobby.
Yes: consultation, registration and deposit fees in cash, card or UPI, with receipts, refunds and a running daily total. When the Eruntar Billing Module is installed, the desk hands off to it and shows payment status only, so there is never a second source of financial truth.
Through five visible steps: requested, verifying, bed requested, nurse notified, admitted. A bed cannot be requested until the registration is complete, the ward is told automatically, and the clinical decision to admit stays with the doctor. Reception coordinates, it does not decide.
The module produces HL7 v2 ADT messages for registration, check-in, admission and transfer, SIU messages for appointments, and FHIR R4 Patient and Appointment resources for the systems around it.
Yes. Doctor availability reads live from the Doctor Module, admissions notify the Nurse Module and the money hands off to the Billing Module, so the record that starts at the desk is the same one the ward, the laboratory and the ICU work from.
It reads identity documents into the registration form, suggests completions and flags inconsistencies, scores possible duplicates, translates text at the desk and recommends next steps, on Premium. Enterprise adds queue prediction. None of it changes patient data on its own: a suggestion has to be reviewed by a person before it is accepted, every AI interaction is audited, and if the AI platform is unavailable the desk keeps working manually.
Access is by capability rather than by job title: 62 of them, in seven ready-made roles from receptionist to read-only auditor. Eight sensitive actions, among them merging records, refunding money, overriding a queue position and forcing a check-in, are denied by default even for the right role until the facility switches them on.
The Reception Module is in beta, and pricing is announced at general availability. Desks join the beta with onboarding and close support from the team, and help shape the product before it is priced. It will be sold on three editions: Standard for registration, calendars, the queue, admissions, visitors and payments; Premium for priorities and estimated waits, the kiosk, offline mode and the AI; and Enterprise for several branches. Beta access is arranged through the form on this page.
Pricing
The Reception Module is in beta. It will be sold on three editions, and what changes between them is the kiosk, the AI and the number of branches. The guardrails do not: duplicate detection, approval-gated merge, the admissions steps and the append-only audit are in every edition. Beta partners run the module with the team's support, and are the first to know the price.
One branch
The whole desk: registration, calendars, the queue, admissions, visitors and the money. Deliberately without AI.
One branch, with AI
Everything in Standard, plus priorities and waits, the kiosk, offline mode and the AI at the desk.
Branches per agreement
Hospitals and groups running several front desks, with the queue predicted and the branches compared.
Prices are published on the pricing page at general availability. Beta partners are told first.
Beta partners get onboarding support, a direct line to the team building it, and a say in what it becomes. Tell us how many desks and doctors you run and we will take it from there.
Rather see the consulting room first? Explore the Doctor Module.