Messaging on the phone they have
Confirmations, tokens, reports, and reminders arrive in the thread a patient already reads, rather than an inbox they do not check or an app they will not install.
It meets patients where they already are.
A patient should not have to install software to hold their own health record. These are the channels patDule uses, what the patient controls at each one, and how the clinic behind them stays connected.
No new app, because the app is the one they already have
The competitive reality is that a portal is a window into one provider. The point of a personal health record is that it outlives the clinic that created it.
Booking that writes to the diary
A booking is not a request that someone re-types. It lands in the clinic diary, takes a slot, and the token that follows is the same record the desk is working from.
ABHA and ABDM consent
Records built around the ABHA identity with consent-first sharing, on the ABDM sandbox track. Consent is something the patient grants, sees, and can withdraw.
One record across visits
Visit, lab, prescription: four views of the same encounter held as one thread, so a history survives changing clinic rather than starting again.
Consent is a switch, not a checkbox at signup
Granting, and withdrawing
Sharing is per recipient and per purpose, and withdrawing it stops the sharing. A consent you cannot take back was never consent.
Caring for someone else
A parent, a child, or an elder can be managed from your own account, with their consent recorded rather than assumed.
Telugu, Hindi, English
Language is a setting on the account rather than a separate version of the product, so nobody has to translate their own health for the system.
Taking it with you
The record exports in open formats. It is the patient's copy, which is the whole idea, and that stays true if they never see this clinic again.
It works with whatever is behind your desk
patDule can run as a patient communication layer for a clinic regardless of its backend, so partnering does not mean replacing anything.
No system required
A clinic on paper registers can still give patients booking, live tokens, and report delivery. The layer does not require a platform underneath it.
Or the full platform
With hospiDule and medDule behind it, tokens, bills, and results flow automatically instead of being posted by a person who has to remember to.
HL7 and FHIR R4
Standard interfaces where a clinic already has a system worth connecting to, so the patient surface is not a second data entry job.
Payment before arrival
A payment link in the same conversation settles onto the clinic ledger, so paying ahead and paying at the counter are one number at day close.
What we do with what a patient trusts us with
Where the data lives
Encrypted in transit and at rest, held in the region the organisation operates in, and handled to meet DPDP obligations rather than described as certified.
Who can see it
Access is role-scoped and organisation-scoped, enforced at the edge and inside every service, and every read of a record is logged.
What AI is allowed to do
Nothing enters a clinical record without a clinician signing it off, and every generated line carries where it came from. That gate is not a setting.
What it is never used for
Patient data is not used to train any external AI model. That is a policy commitment rather than a preference you have to find and switch off.
Early Access
Partner your clinic with patDule
We handle the integration side. Your clinic gets fewer no-shows and a calmer waiting room, without new software to learn behind the desk.
Encrypted, stored in the region you operate in, and governed by consent the patient can withdraw.
Explore
More from patDule
The full picture, one page at a time.
Features
Everything patDule does, all of it inside the WhatsApp thread patients already use.
Use cases
The patient journeys patDule was built around, and what clinics get from each one.
Pricing
The patient side of care, on WhatsApp. Free for patients, permanently, and included with your clinic plan.