Platform and APIs

Use it as a service. Build on it as a platform.

Hospitals run Sevara as a ready service. Groups, integrators and partners also build on it: open standards for data, configuration instead of custom code, and one multi-tenant core you can run in our cloud or yours.

Talk to our platform team Book a demo

FHIR R4 · synthetic example

GET /api/fhir/Patient?identifier=DH-000081
Authorization: Bearer ••••••••

{
  "resourceType": "Bundle",
  "type": "searchset",
  "total": 1,
  "entry": [{ "resource": {
    "resourceType": "Patient",
    "identifier": [{ "value": "DH-000081" }],
    "gender": "male"
  } }]
}

Two ways in

One core, two ways to use it.

As a service (SaaS)

For a hospital or a group that wants every module working on day one.

Every module, one record, one login
Updates without downtime projects
Onboarding, training and support from people who know hospitals
Your data separated from every other hospital at the database

As a platform (PaaS)

For groups, integrators and partners who connect, configure and extend.

FHIR and HL7 interfaces with per-system tokens
Roles, approvals and feature switches by configuration
Provision and operate many hospitals from one console
Run it in our cloud or on your own servers

Connect

Standards-based interfaces, so your analysers, PACS, insurers and other systems talk to the same record.

FHIR R4 API
Live
Read and search Patient and Encounter with a token the hospital issues per system. More resources follow.
HL7 v2 in and out
Live
Orders to modalities and analysers, results and ADT feeds back, through a per-endpoint token.
Reliable delivery
Live
Every outbound message goes through an outbox with retries and a delivery log, so nothing is silently lost.
Accounting exports
Live
Journals to Tally XML and Zoho Books CSV; GST registers and the trial balance on demand.
Event webhooks
On the roadmap
Subscribe your own systems to admissions, results and bills as they happen.

Configure

Shape the platform to each hospital without code: who does what, which modules are on, how work is approved.

Roles and permissions
Live
Forty-five ready-made roles, custom roles, permissions per module and branch, delegations with an end date.
Feature switches
Live
Turn modules on per plan or per hospital, so a clinic and a group run the same platform.
Masters
Live
Departments, wards and beds, services, tariffs, packages and order sets, managed by the hospital.
Approval rules
Live
Maker-checker on refunds, cancellations, stock adjustments, and purchase orders by amount.
Single sign-on
On the roadmap
SAML and OpenID Connect for groups with their own identity provider.

Operate

Run many hospitals on one platform, or run it yourself, with the controls a regulated service needs.

Multi-tenant by design
Live
Every hospital sealed off by row-level security in the database, checked on every build.
Tenant provisioning
Live
Create a hospital, its first administrator, plan and branches from one console.
Audit everywhere
Live
Append-only audit of every change and every record opened, exportable for inspectors.
Your cloud or ours
Live
Run it as a managed service or on your own servers with Docker; the same build either way.
AI with guardrails
Live
Assistants that act as the signed-in person, propose rather than change, and refuse clinical questions in code.

Running it yourself? The self-hosting guide covers servers, settings, the first hospital, backups and updates.

Ask for the self-hosting guide

Building on it? Talk to our platform team.

Tell us what you want to connect or extend. We walk through the interfaces, the configuration and where it runs.

Book a demo Talk to sales