Move from EkaCare. ABHA links come with the records, so nobody re-links a patient.
If your patients already have ABHA numbers attached, they stay attached. Prescriptions, visits, reports and billing follow in about two days, and your WhatsApp number does not change.
- ABHA links preserved
- Same WhatsApp number
- About two days
The records, the prescriptions, and the ABHA links you spent months collecting.
Clinics on EkaCare tend to have done the ABDM groundwork: a good share of patients carry an ABHA number, and consultations have been linked as care contexts. That work is worth protecting. When the export carries the ABHA number against each patient, Saaro imports it as part of the patient record, and the clinic does not have to ask anyone to verify an OTP again.
The rest of the export is familiar: patient list with phone numbers, visit history, prescriptions as structured drug lines or as documents, uploaded reports, and billing. Each maps to its place in Saaro, and you get the mapping sheet before we import anything.
One honest boundary. Consent artefacts that were granted through the ABDM consent manager are tied to the health information provider that received them. Records already linked to a patient's ABHA remain visible in their ABHA app; new consent requests after the switch are raised by Saaro as your clinic's HIP. Nothing in the patient's own health locker is touched by the migration.
Six data types, and who is responsible for each.
Product means Saaro does it. Clinic means you provide or confirm it. Both means we do it together on the verification call.
- Saaro handles it
Patients
Name, phone, date of birth, sex, allergies and ABHA number or ABHA address where present. Phone number is the de-duplication key; the ABHA number is validated on import and flagged if it does not parse.
- Saaro handles it
Visits
Consultation date, doctor, complaint, vitals, diagnosis and notes, placed in the patient timeline in order. Visits that were linked as care contexts are marked so you can see which ones the patient can already view in their ABHA app.
- Shared
Prescriptions
Structured drug lines become rows with drug, dose, frequency and duration so refill reminders and interaction checks work on them. Document-only prescriptions are attached to the visit and re-structured for active chronic patients first.
- Shared
Reports
Lab and imaging files are attached to the matching visit. Documents the patient shared from their own locker are kept as patient-provided and labelled as such.
- Your clinic
Billing history
Invoices, receipts and dues are imported so ledgers are complete. GST registration, invoice series and letterhead are configured fresh in Saaro by you.
- Your clinic
Appointments
Future appointments go into the Saaro calendar. You confirm doctor names, slot lengths and any location mapping if you run more than one branch.
Export, map, import, verify. Two days.
- 01Day 1
Export
You take the export available in your EkaCare account, or ask their support to prepare one. Upload it through the secure link we send; never over email or WhatsApp.
- 02Day 1
Map
We read the files and return a mapping sheet, with ABHA fields and care-context flags called out. You approve it or mark changes.
- 03Day 2
Import
We load the data into your Saaro workspace, validate ABHA numbers, de-duplicate on phone, structure drug lines and attach documents to visits. You get a per-type count.
- 04Day 2
Verify
On a call, you open ten to twenty real patients, including several with ABHA links, and confirm demographics, ABHA, last visit, last prescription and balance match.
Run both, then switch. The patient sees the same number throughout.
After verification, new visits go into Saaro and EkaCare stays open read-only as a reference for as long as you want. The migration deletes nothing from EkaCare; closing that account is your decision on your timing.
Your clinic's WhatsApp number is onboarded onto SaroConnect, Lumotis's own WhatsApp Business Solution Provider infrastructure, during setup. Prescriptions, reports, reminders and refill nudges go out from the same number patients already have, with no third-party BSP in the chain and no external template-approval queue.
For ABDM, Saaro takes over as your clinic's health information provider from the first visit you record in it. New consultations are linked to the patient's ABHA as care contexts, and consent requests are handled from inside the record. Nothing already in a patient's locker is altered.
Your questions answered.
The things clinics ask first.
No. Data is copied into Saaro and nothing is deleted from EkaCare. You verify real patients, including ABHA-linked ones, in both systems before cut-over.
No. Where the export carries the ABHA number, it is imported with the patient record. New visits recorded in Saaro are linked to that ABHA as care contexts with the patient's consent; existing records in their ABHA app are untouched.
About two days for a typical clinic: export and mapping on day one, import and verification on day two. We confirm timing after seeing a sample export.
Yes. Your existing number is onboarded onto SaroConnect during setup, so patients see the same number and clinic name they already have saved.
Yes, keep EkaCare open read-only as long as you like. Published plans are Solo ₹1,499 and Clinic ₹3,999 per clinic per month, billed annually, excluding GST, with messaging included. Migration is scoped on the demo call once we have seen a sample export.
Keep reading.
- FeaturesPatient recordsA record built from every visit, not a spreadsheet row. Prescriptions, reports, notes and follow-ups sit in one timeline, linked to the patient's ABHA if they have one.
- FeaturesWhatsApp automationSaaro runs on SaroConnect, Lumotis's own WhatsApp Business infrastructure. Reminders, prescriptions, reports and refills go out from your number, patient replies come back to the desk, and messaging is included in every plan.
- FeaturesVoice prescriptionSpeak it in English, Hindi, or your mix of both. Saaro structures the drug, dose and duration, flags interactions, files it to the record and sends it from your clinic's number.
- AI flowsRefill remindersBecause Saaro's prescriptions are structured rows, not photos of a slip, the refill flow knows exactly when each medicine runs out. The patient gets a nudge, replies R, and the pharmacy or the doctor picks it up from the record.
- Comparevs EkaCareEkaCare is ABDM-native and plays on both sides: a consumer health app for patients and an EMR for doctors. Saaro Health is clinic-only and puts the patient side in the WhatsApp thread they already have with you. The differences are real, and this page lays them out.
- TrustABDM complianceABHA creation, care-context linking, consent requests and FHIR record push happen inside the patient record. Here is what the Ayushman Bharat Digital Mission asks of a clinic, and which parts Saaro handles.
Bring a sample export to the demo.
Fifty anonymised rows, a few with ABHA numbers, and we will show you the mapping live.