Your organisation runs several systems. It should need one account.
CareSewa is one no-code platform behind 10 healthcare ERPs — hospital, clinic, dental, lab, diagnostics, pharmacy, ambulance, blood bank, and the portals your doctors and patients use. Register your organisation, choose what you run, and reshape any of it without writing a line of code.
Free to register. Accounts are reviewed by a person before ERP access opens.
What you are registering for
- connected ERPs
- 10connected ERPsone account, one login
- field types
- 18field typesbuild any model
- ship ready-made models
- 7ship ready-made modelslive on day one
- lines of code
- 0lines of codeto add a workflow
Care is connected. The software never was.
Across Asia, care is delivered by thousands of small, independent participants. The systems they run were never designed to speak to each other — so the people in the middle pay for it.
The lab does not know the hospital
A result is printed, carried across town and typed in again. Every handover between two organisations is a re-entry, and every re-entry is a chance to lose something that matters.
The software cannot bend
You need one more field on an intake form. Your vendor quotes six weeks and a change fee. So the field goes in a notebook instead, and the data never reaches the system at all.
One organisation, five logins
The group runs a hospital, a lab and a pharmacy. That is three vendors, three contracts, three user lists and three versions of the same patient — none of which agree.
“None of this is a technology problem. It is an architecture problem.”
10 systems. One account. Zero re-entry.
Subscribe to the ones you run. Each opens on its own address, shares one user list, and reads from the same engine — so a referral between two of them is not an integration project.
Facilities
3 systemsHospital ERP
hospital.caresewa.com
Full hospital administration — patients, doctors, appointments, billing.
Clinic ERP
clinic.caresewa.com
Lightweight clinic management for single or multi-doctor practices.
Dental ERP
dental.caresewa.com
Dental practice management — treatments, charts, appointments.
Services
5 systemsLaboratory ERP
lab.caresewa.com
Lab test catalog, orders, samples and reports.
Diagnostics / Imaging ERP
diagnostics.caresewa.com
Radiology & diagnostics — scans, modalities, reporting.
Pharmacy ERP
pharmacy.caresewa.com
Medicine inventory, dispensing and expiry management.
Ambulance ERP
ambulance.caresewa.com
Fleet management, dispatch and trip logs.
Blood Bank ERP
bloodbank.caresewa.com
Blood inventory, donors and requests.
Practitioners
1 systemDoctor Portal
doctor.caresewa.com
Practitioner workspace — schedule, consultations, prescriptions.
People
1 systemPatient Portal
patient.caresewa.com
Patient-facing app — records, appointments, reports.
What makes it one ecosystem, not ten products
The ERPs are not ten codebases with a shared logo. They are ten configurations of one engine — which is why they behave the same, upgrade together, and bend to your organisation instead of the other way round.
One account, every system
Register once. Subscribe to as many of the 10 ERPs as you run. One user list, one tenant, one bill — not 10 vendors.
Models defined at runtime
Entities are definitions, not code. Add a field, change a form, invent an entity we have never heard of — the engine renders it. No release, no ticket.
Tenant-isolated by default
Every definition and every record carries your tenant. Every query filters by it. Isolation is a constraint in the engine, not a policy in a document.
Audit-logged, always
Every change to a record or a definition is written to an append-only log — who, what, before, after, when. It cannot be edited, including by us.
Permissions down to the model
Staff get explicit grants per model — create, read, update, delete. A receptionist and a pharmacist open the same platform and see two different products.
Medical data is soft-deleted
Patient records are never hard-deleted by default. Deletion marks a date; the record survives. Losing a medical history to a stray click is not a feature.
Add a field. Watch every screen change.
In most healthcare software an entity is a table someone compiled two years ago. Here it is a definition you can edit today. Change it and the forms, the tables, the validation and the permissions follow — because they were always reading it.
- 18 field types — text, currency, dates, files, relations, and more
- Relations that can only point at records inside your own tenant
- Validation on every write, against your definition — no unvalidated data
- Default models are suggestions: edit them, extend them, delete them
Who sees what
- Owner / adminEvery owned ERP, every model, full access
- DoctorTheir schedule, consultations and prescriptions
- PharmacistInventory, dispensing and expiry
- ReceptionistOnly the models they are granted, action by action
One platform, one login — and a different product depending on who signs in.
Live in days, not quarters
No implementation project. No consultant on site for six months.
- 01
Register your organisation
Your name, your details, and the ERPs you run. It takes a minute and you do not need to talk to anyone first.
- 02
We review the account
A person at CareSewa checks the organisation and approves it. Healthcare is not a market where anyone should be able to self-serve their way to a patient database.
- 03
Open your ERPs
Once approved, each ERP opens on its own address. 7 of the 10 arrive with working models already in place — the rest start empty, for you to shape.
- 04
Reshape it as you go
Add a field on a Tuesday because a doctor asked on Monday. Studio changes the model; every form and table follows. Nothing is rebuilt.
The things people ask first
If yours is not here, ask us directly — a real person answers.
What happens after I register?
Your account is created immediately and you can sign in straight away. Access to the ERPs themselves is granted by CareSewa once the organisation has been reviewed — until then you will see your account status and the ERPs you asked for.
Can one account run more than one ERP?
Yes — that is the point. A group running a hospital, a lab and a pharmacy subscribes to all three under one account, with one user list. You can add or drop an ERP later without starting again.
What is a tenant code?
An 8-character public code for your organisation, issued at registration. Your email address only has to be unique within your organisation, not across the whole platform — so if the same address is registered under two organisations, the tenant code tells us which one you mean when you sign in.
Do the ERPs come with anything in them?
7 of the 10 ship default models — suggestions, not fixtures. They are yours to edit, extend or delete. The others start empty on purpose, because a diagnostics centre and a clinic do not want the same starting point.
Is my data separate from other organisations?
Yes. Every record and every definition is stamped with your tenant, and every query filters on it. Cross-tenant access exists only for platform administrators and is explicit, never implicit.
What does it cost?
Pricing depends on which ERPs you run and how many people use them. Register your organisation and we will confirm it with you during review — registering does not commit you to anything.
Register your organisation
Create the account, choose the ERPs you run, and we will take it from there. It costs nothing and commits you to nothing.