FAQ
Frequently asked questions
Trials and plan limits, hosting or your own server, getting your data out, and what the software does — and does not yet do.
Yes. Every plan on our pricing page starts with a free trial of 14 days. You can start a trial or compare the plans first.
Limits are set on the plan and published up front — there is no per-user licence on top:
- Starter: up to 10 users, up to 2,000 patient records, one site, selected modules.
- Professional: up to 40 users, up to 20,000 patient records, one site, every module.
Prices and the modules in each plan are on the pricing page.
A single-site hospital that needs more users or patient records than its plan allows does not have to move plan. We raise the limits on the plan you are already on, and agree what that costs with you case by case.
Running several sites is a different question — see multi-branch below.
Either.
- Hosted by us: your hospital gets its own workspace at its own web address, carrying your hospital’s name.
- Self-hosted: you run it on your own server, and your data never leaves it.
If you are not sure which suits you, ask for a quote and tell us about your setup.
Yes. On the hosted edition each hospital’s records live in their own database — not a shared table with a hospital column. Sensitive fields (medical history, allergies and lab results) are also encrypted at rest with AES-256-GCM, using a key kept outside the database.
Yes, on the self-hosted edition: your group runs the system on its own server and owns the data outright. The hosted plans are single-site. Ask for a quote for a multi-site setup.
The self-hosted edition does. It has no external dependencies — even the styles and icons it uses are bundled — so it can run on your hospital’s own network with no internet connection at all. The hosted edition is used over the internet.
- PHP 8.1 or newer, with the pdo_mysql, openssl, mbstring, json and fileinfo extensions.
- MySQL 5.7 or newer, or MariaDB 10.3 or newer.
- Apache or nginx.
- No Composer and no third-party packages: the software has no outside dependencies.
We do not publish server sizing, because it has not been load-tested yet and we would rather not guess. Tell us about your hospital and we will talk it through.
- Self-hosted: you already have everything. A built-in backup command writes a plain MySQL dump and a zip of uploaded documents. It is your server; nothing is withheld and nothing needs asking for.
- Hosted: we can provide a copy of the same dump on request.
- One patient at a time: for hospitals in India, on plans that include the Health ID and consent module, a patient’s record can be exported as a FHIR R4 document bundle — patient details, encounters, conditions, prescriptions, observations, lab reports and allergies.
The dump is ordinary MySQL, so it can be restored on your own hardware. Because sensitive fields are encrypted, the encryption key has to travel with it — without the key those fields cannot be read.
For hospitals in India, it is ABHA-ready: you can record patients’ ABHA numbers and manage their consent, ready for ABDM integration. ABHA and ABDM are India’s national health ID and digital health mission, so a hospital in any other country does not see this part of the system. It is not yet connected to the ABDM gateway — that integration is on our roadmap — and we do not claim ABDM certification.
It has built-in prescribing safety checks for common interactions and drug allergies, and it understands drug classes: a recorded penicillin allergy warns when amoxicillin is prescribed, and cephalosporins warn as a possible cross-reaction.
The built-in rules are a starter set — 40 common interactions and 66 drug-class mappings — not a complete drug database, and they can be extended with a licensed one. Warnings do not block: the prescriber records a reason for going ahead, and it is kept with the prescription.
- AES-256-GCM encryption at rest on medical history, allergies and lab results.
- Two-factor authentication, with single-use recovery codes.
- Role-based access across seven roles, enforced on every page and action.
- A tamper-evident activity log: every entry is signed, so editing, forging or deleting entries can be detected.
- Sign-in throttling, and protection against cross-site request forgery on every change.
We hold no security certification and do not claim one. If your hospital needs an independent security assessment, ask us - we will support one on your installation.
Yes, on every plan. Patients can see their appointments, prescriptions and invoices, see lab results once they have been checked and released, and book appointments online.
At your hospital’s own address — for example yourhospital.healthcare.dvsoft.in, or your own domain if you use one. They can also use the sign-in page on this site, choose their hospital, and be sent on to its own sign-in page. Patients reach the patient portal the same way.
Still unsure? Ask us directly and we will reply by email.
See it working on your own questions
Tell us what your hospital or clinic runs, and we will show you those parts of the software.