Home › Your data
The questions a careful owner — or their chartered accountant, or their partner — should ask before signing anything, answered plainly and without hiding behind acronyms.
Not a shared table with a column for your clinic's name. Each clinic on Solace has a separate database, and the boundary between two clinics is the database itself rather than a filter somebody has to remember to write correctly.
This is the single most important thing on this page. Most multi-tenant systems keep everybody's patients in one table and rely on the code being right every single time.
Your patients' records live on infrastructure in India, and the AI that reads them is scoped to an Indian region. Where a capability genuinely is not available in India, we say so and do without it rather than quietly sending your data somewhere else.
Built to the Digital Personal Data Protection Act, 2023 — consent recorded, purpose limited, and deletable on request.
Records export as a standard FHIR bundle — a format other health systems can read. Patients can link their ABHA number themselves, and it is written through to every clinic they are registered at.
You can export all of your data at any time, not only when you are leaving.
Doctors, front desk, nurses and the owner each see only their own screens, and every change to a record is logged against the person who made it — including anything an AI desk did on a member of staff's behalf.
Databases are backed up, and a restore is something we have actually practised rather than something we assume works.
The clinical AI question
This is the part a regulator, an insurer and a careful doctor all care about, so it is worth being exact rather than reassuring.
The co-pilot offers red flags and a differential to consider. It is a prompt for the doctor's own thinking, and the record never shows an AI as the author of a diagnosis.
A prescription is drafted for review. A registered doctor changes what they want to change and signs it. Nothing reaches a patient unsigned.
Solace is not registered as a medical device with CDSCO and does not make claims that would require it to be. We will not tell you otherwise to win a deal.
And where it cannot check something, it says so. If there is no recent creatinine on file, the safety check reports that it could not verify renal dosing — rather than staying silent, which a busy doctor reads as “nothing to worry about”. Silence is the failure mode that actually reaches a patient.
Messages and calls
SMS and WhatsApp to Indian numbers are regulated, and a system that ignores that gets your clinic's messages blocked rather than delivered.
Ask for the data-processing terms before you sign. If a vendor will not give you those in writing, that is your answer.
Straight answers
No, and we will not imply that we are. We are a young company building to the Indian law that actually applies to you — the DPDP Act — and we are happy to walk you or your auditor through exactly how the system is built. Certification is on the roadmap; claiming it before it exists is not.
Access is restricted to the engineers who operate the platform, and only for support and incident work. It is logged. We will name the arrangement in the data-processing terms rather than leaving it vague.
No. Your clinic's records are used to serve your clinic. They are not pooled into training data for anybody else's benefit.
You export it — all of it, as a FHIR bundle — and we delete it on your written instruction. There is no exit fee and no hostage-taking of your patient list.
A fair question to ask any young vendor. The answer is the export: because your data leaves as a standard format at any time, your clinic is never one company's survival away from losing its records. Take an export periodically — we will help you set that up.
We would rather answer this properly once than be asked to explain it after something has gone wrong.
