The web home for people your facility already treats
Records, appointments and reports on the web — the same patient identity that powers the CareSewa One mobile app.
What changes on day one
- Reach your records from any browser
- Book with facilities you have connected to
- Read reports the moment they are verified
- Control who sees your profile, always
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 Patient Portal
The surfaces this portal 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.
Health records
Records from every provider you connected to, in one place.
Appointments
Book, reschedule and cancel with connected facilities.
Reports
Lab and imaging reports released to you on verification.
Billing
What you owe and what you paid, per facility.
Consent control
Connect, share and revoke — revoke hides everything, immediately.
One identity
The same Health ID and account as the CareSewa One app.
It arrives with these models. All of them are editable.
Subscribing provisions Patient Portal and seeds 4 default models against your account. Not one of them is fixed: rename them, add fields, remove fields, or delete the model outright. They exist to save you an afternoon, not to define your organisation.
Record
ModelDefinition · seeded
Appointment
ModelDefinition · seeded
Report
ModelDefinition · seeded
Bill
ModelDefinition · seeded
And whatever else your organisation tracks
Records for every one of these live in a generic store, tagged with your tenant. That is why adding a field is instant and why removing one never destroys what was already recorded — the schema is data, and clinical data is soft-deleted by default.
Change any of this yourself
Every field on every patient 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 Patient Portal 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.
Connect. Share. Revoke. Nothing else grants access.
This is the part that is worth being precise about, because most health software gets it backwards. Your account is not issued by a hospital and cannot be taken by one. Every provider who sees you is a provider you chose.
The account is yours first
You create your own Health ID. No hospital enrols you, and no hospital can delete you. You exist on the platform, not inside a facility.
A provider sees nothing until you connect
Search a provider, connect, share. Before that, your name is not in their system — not hidden in it, not in it.
Revoke hides everything, immediately
Not at the end of the month. Not after a support ticket. The next request that provider makes returns nothing.
Nobody administers you
There is no staff model here, because there is no organisation above you. Patient Portal and CareSewa One are two surfaces on one account that belongs to you — the same Health ID, the same records, the same consents.
On the provider side of a connection, staff at that facility hold per-portal and per-model grants that their admin sets. What none of those grants can do is reach a patient who has not connected and shared. Consent sits above the permission model, not inside it.
- One account across the browser and the mobile app
- Every connected provider is one you chose
- Sharing is per provider, and revocable per provider
- Your record is not deleted when you leave a hospital — it was never theirs
Aarav Sharma
Health ID · CS-4KX92QM7
Providers you have connected to
City General Hospital
Connected · sharing
Sunrise Diagnostics
Connected · sharing
Metro Pharmacy
Revoked by you
Revoked providers see nothing on their next request. Not a cached copy, not an archived view — nothing.
The rules are in the engine, not in a policy document
Patient Portal 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 Patient Portal
If yours is not here, ask us directly — a real person answers.
Same account, different surface. Patient Portal is the browser view; CareSewa One is the mobile app with services, bookings and community.
Connect Patient Portal 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 Patient Portal shaped around your workflows
Not a generic demo tenant — patients of connected facilities 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