Dental practice management modelled on how you actually chart
Treatments, charts, appointments and recalls — built around your speciality instead of a generic clinical template.
What changes on day one
- Chart treatments the way your practice records them
- Keep multi-visit treatment plans in one thread
- Bring patients back with recall workflows
- Take dental bookings from CareSewa One
Everything below is a starting point, not a specification. Every model, field and form on this page is yours to change in Studio — without a developer, a release or a migration.
Inside Dental ERP
The surfaces this ERP ships with. Read them as a well-informed first draft — the shape is right for most, and where it is wrong for you, you change it rather than file a ticket.
Treatment records
Define per-tooth or per-quadrant records with the fields your practice charts.
Treatment plans
Multi-visit plans tracked as a relation between the plan and each visit.
Appointments & recalls
Schedule visits and the six-month recall in the same model.
Materials & lab work
Track crowns, aligners and external lab jobs with your own status flow.
Patient documents
X-rays, consent forms and scans attached to the record.
Bookings inbox
Dental service requests from patients land in a confirmable queue.
It arrives completely empty. That is the feature.
Dental ERP ships with no default models at all — and we are going to defend that rather than apologise for it.
Blank by design
Dental charting is the most opinionated thing in this suite. An orthodontist tracking eighteen-month plans and a practice doing exams and cleanings do not want the same record, and neither of them wants ours. So Dental ERP starts empty and you chart the way you already chart.
Want a head start instead? Copy the default model set from Hospital ERP and cut it down to what you use. Both routes take minutes. Both end somewhere you chose.
Your first hour, roughly
- 01
Name your models
The three or four things you actually track. Not ours.
- 02
Add your fields
Eighteen types — text, select, date, relation, file and the rest.
- 03
Order the form
Drag it into the sequence your staff actually work in.
- 04
Open
The API, the table and the form exist the moment you save. There is no step five.
Change any of this yourself
Every field on every dental form is a record in a ModelDefinition, not a line in a codebase. That is not an implementation detail — it is the reason you can add the field you need on a Tuesday afternoon and have your staff using it before the shift ends.
No release. No migration window. No change request, no six-week quote, no field living in a spreadsheet because the vendor said no. You open Studio, you add it, and the form re-renders for everyone on their next request.
18 field types
Text, number, currency, date, select, relation, file, JSON and more.
Relations, not exports
Link a model to a model and the join is real, not a nightly CSV.
Auto-CRUD REST
Every model you define gets an API with the same envelope and auth.
Instant everywhere
The table, the form and the API all change on save. No deploy.
What Dental ERP plugs into
This is not a standalone product with an integrations page. The other portals are on the same engine, the same account and the same patient — so “integration” is mostly a word for something that already happened.
All ten sit on one patient, one staff directory and one audit trail.
Connect another and there is nothing to migrate, nothing to sync, and nobody retyping a name from one screen into another.
Recalls that reach someone
The hardest part of dental is not the treatment; it is the six-month return. When the patient already holds a CareSewa account, the recall is a notification in an app they open — not a card in a drawer.
They connect to your practice
Patients find you and share their profile. Nothing about them is visible to you before that.
They book dental services
Exams, cleaning and treatment appointments are offerings you publish and they book from the app.
Their plan travels with them
Treatment plans, X-rays and consent forms sit in the record the patient carries — so a move across town is not a restart.
And the part that is genuinely uncomfortable to say out loud
The patient can revoke you. Their account is platform-level and they own it, so the moment they revoke, your view of them is empty — not archived, not pending a support ticket, empty. We think that is the right trade: providers who are chosen get people who arrive with their whole history, instead of a clipboard and a memory test.
How CareSewa One worksPeople get exactly what you grant. Nothing more.
Staff are created once on your account, then granted specific portals and specific create, read, update and delete rights per model. A dental receptionist and a dental manager are the same directory entry with different grants — not two systems with two passwords.
Entitlements ride in the JWT and are enforced server-side. A portal you do not hold returns 403 no matter what the browser renders, and a revoked grant stops working on the next request rather than the next login.
- Grants are per portal and per model, not per role-shaped guess
- Create, read, update and delete are separate rights
- Enforced on the server on every request — hiding a menu is not security
- Revocation takes effect immediately, not at the end of a session
Priya Menon
Staff · created once, granted per portal
Portal grants
Dental ERP
dental.caresewa.com
Laboratory ERP
lab.caresewa.com
Pharmacy ERP
pharmacy.caresewa.com
These grants are claims in the token and are re-checked server-side on every request. The UI reflects them; it does not enforce them.
The rules are in the engine, not in a policy document
Dental ERP does not implement its own idea of security. It inherits the platform's — which means these constraints hold on every request, in every portal, without anyone remembering to apply them.
Tenant isolation is structural
Every model definition and every record carries your tenant id, and every query filters by it. There is no code path that reads across tenants without an explicit super-admin assertion.
Every mutation is audit-logged
Who did what, when, and from where — appended on write, readable by your admins, and editable by nobody. Including us.
Clinical records are soft-deleted
Removing a field stops collection and display; it does not destroy what was already recorded. Medical data is not hard-deleted by default, and that default is deliberate.
Consent gates the patient, not a setting
A patient is visible to a provider because they connected and shared. No admin toggle, no bulk import and no support request produces access that the patient did not grant.
What people ask about Dental ERP
If yours is not here, ask us directly — a real person answers.
You can model per-tooth records today using a record per tooth with a relation to the visit. A dedicated chart widget is on the roadmap.
Connect Dental ERP on its own, or alongside the other nine
Each portal is entitled and billed separately, so you pay for what you connect and nothing else. CareSewa is priced per market rather than from one figure in one currency.
Nine more, on the same account
Add any of these later without touching what you already run. One login, one patient, one audit trail.
See Dental ERP shaped around your workflows
Not a generic demo tenant — dental practices, orthodontists, dental chains have their own protocols, and the point of this platform is that it takes them.
Multi-country by design · tenant-isolated · every change audit-logged