Hospital type & scale
A general, maternity, or psychiatric hospital, or a clinic; the number of beds and service volume. The needs of a clinic or small (type D) hospital differ greatly from those of a large hospital.
We choose transparency over posting a single figure stripped of context. Here we break down the real cost components — so you know what drives the number, and the proposal is built around your actual needs.
Why this page has no numbers
An honest price cannot be set without knowing your hospital.
A "starting from" figure is neat, but hard to turn into an honest promise: the real cost depends on the hospital type, the modules used, the integrations enabled, the deployment model, and your migration and support needs. We choose to explain the factors first, then build a proposal after an assessment — so the number is right for what you actually need.
6 cost factors
A general, maternity, or psychiatric hospital, or a clinic; the number of beds and service volume. The needs of a clinic or small (type D) hospital differ greatly from those of a large hospital.
How many of the 49 modules you actually use — clinical, financial, and administrative. You do not pay for what you do not use.
BPJS, SATUSEHAT, E-Klaim, SISRUTE, PACS/LIS, BSrE — some involve third-party subscriptions or credentials on the hospital side.
Your own server (on-premise) or the hospital's choice of cloud (GCP/AWS/Azure). This choice affects infrastructure cost and who manages it.
Moving data from the old system and training staff in batches — a one-time effort up front, depending on complexity.
Ongoing support, updates that keep pace with regulation, and the level of hands-on support required.
Founding-partner model
Special terms for the first 1-2 hospitals.
Adievia is pre-revenue and looking for founding partners. For the first hospital willing to run it in full production — built together, with hands-on support straight from the developers — there are special terms well below the eventual list price. This is not manufactured urgency; it is an honest consequence of the stage we are at.
FAQ
We deliberately do not post a price figure on this page — because an honest price depends on your hospital's type and scale, the active modules, the integrations, the deployment model, and your migration and support needs. A "starting from" figure without context is hard to stand behind. We prefer to assess your needs first, then put together a proposal that is genuinely right.
Because hospitals are not a uniform product. A rigid package can leave a hospital paying for things it does not use, or hide costs that only surface later (integrations, migration, training). Being transparent about the cost components is more helpful than a single figure that may not reflect your actual needs.
Typically, the system license/usage is separate from one-time costs such as data migration and training, and from third-party subscriptions (e.g. a BSrE certificate, cloud infrastructure) that belong to the hospital. We spell out what is included and what is extra from the start — not after the contract is signed.
Adievia is pre-revenue and looking for 1-2 founding-partner hospitals. For a founding partner, there are special terms well below the eventual list price, in exchange for close involvement and the willingness to be the first hospital to run it in full production. We state this plainly — it is not a sales tactic.