One governed radiology backbone for every branch.
Unify study flow, reporting, DICOM agents, billing and analytics across all your hospitals and branches under one central, role-governed platform with strict per-site data isolation.
Frequently asked questions
Can one branch see another branch's patients?
No. Isolation is enforced in the database itself with row-level security in FORCE mode, so a query for one branch cannot return another branch's rows. It is not application-side filtering that a bug or a direct query could step around.
Can reporting capacity be shared across branches?
Yes. A radiologist can be scoped across several branches and work one shared worklist, so a busy site can be covered by readers attached to another — without giving anyone a second login or blanket access to everything.
Do we get turnaround and billing per branch, or one lump?
Per branch. Turnaround is tracked per study and sliced by centre, and invoices are raised and reconciled per centre rather than hand-totalled across the chain.
Who signs the report?
A registered radiologist, always — AI drafts only, and signing is restricted to radiologist accounts. Every finalised report carries the signing radiologist's name and registration number.
Where does our data live?
In India, on AWS Mumbai (ap-south-1), and the platform is built DPDP-ready by design.