It never sees your raw schema
The model is shown a curated set of business views with clean names and written definitions — not your hospital tables, and not patient identity columns for users who are not cleared.
Security & governance
Built to survive an audit, not just a demo
Two questions decide whether a hospital IT head says yes: can this slow down or corrupt our clinical system, and who can see patient data. Both are answered below without hedging.
In short
Prism connects to a hospital system using a read-only login and never writes to it. Analysis runs against a separate reporting database, so clinical systems are unaffected. Access is role-based by unit and department, patient identity is masked unless a user is cleared, and every login, report and question is logged.
1
Read-only by design
The login Prism uses on your hospital system has read rights and nothing more. It is not technically capable of writing to a clinical system. Your DBA creates it and can verify the grant.
2
A separate reporting database
Analysis never runs against the database your wards and billing counters depend on. Month-end reporting cannot slow down a discharge.
3
Role-based access, enforced not trusted
A department head sees their department, a unit head their unit. The restriction is applied by the platform to every query, including queries produced by the Ask box.
4
Patient identity masked by default
Names and contact numbers are hidden unless a user is specifically cleared, and each time they are viewed it is recorded. Most management dashboards work on aggregates and never need identity at all.
5
Credentials encrypted at rest
Hospital database passwords are encrypted with a key held outside the database and are never displayed again after entry. A database dump alone does not yield access to your system.
Everything is logged
Every login, every report run, every question asked and the exact query it produced — recorded with the user, the time and the result count. When an auditor asks who saw what, there is an answer rather than an assurance.
- Access and authentication log
- Report and dashboard run log
- Ask box query log with the generated query
- AI token and cost log per user and per dashboard
- Import and connection history
- Support access log — if we open your console, it is recorded with a reason
Caresoft's own certifications
CMMI Level 5ISO 27001PCI DSS
Twenty years, bootstrapped, still owned by the people who built it. 1,000+ hospitals across India and 12+ countries.
The AI question
What the model can and cannot reach
Worth being precise about, because most vendors are vague here.
It cannot be talked out of your access rules
Unit and department restrictions are applied by the platform after the query is generated. The model is never asked to add a filter, because anything that can be asked can also be persuaded.
It cannot write anything
The Ask box connects through a database account with read permission only. Even if every other safeguard failed, that permission holds.
Evidence, not assurance
Every change is on the record
The audit trail is a dashboard, not a table nobody opens.
Illustrative data shown.
Questions your IT head will ask
Do we have to be a Caresoft HIS customer to use Prism?
No. Prism is a separate product and works with any hospital information system. Where a direct database link is possible we read from it; where it is not, your team uploads spreadsheets and Prism builds the same dashboards from those. Hospitals running Caresoft HIS get a faster start because the schema is already understood, but that is a head start, not a requirement.
We cannot open our database to an outside system. Can we still use it?
Yes. The spreadsheet route exists for exactly this. You export the data you are willing to share, upload it, and Prism runs the same transformations it would have run over a live link. The numbers come out identical. Many hospitals begin this way and connect the database later once they trust the output.
Will connecting Prism slow down our hospital system?
No. Prism copies data into its own reporting database and every dashboard runs against that copy. The login it uses on your system has read rights only and cannot write to it. Your billing counters and wards are unaffected.
What happens to patient names and phone numbers?
Patient identity is masked by default. Only users you specifically clear can see names and contact numbers, and every time they do it is recorded. Most management dashboards never need identity at all, since they work on aggregates.
How long does it take to go live?
Typically four weeks: connect and run the readiness checks in week one, financial dashboards in week two, operational dashboards in week three, and handover in week four. That assumes reasonably clean data, which the week-one readiness report tells you honestly rather than discovering in week three.
What does the Ask box actually do?
Someone in management types a question in plain English and gets back a table or a chart built from your own data. If the answer is useful they pin it and it becomes a permanent dashboard tile. It means new requirements do not need a change request, and it is why the product does not go stale six months after it is installed.
Can we see what the AI costs us?
Yes, in detail. Every question is metered: which user asked it, which dashboard or report it belongs to, how many tokens it consumed and what that cost. The token log is visible to your administrators, not just to us, and each plan carries a monthly allowance you can watch against.
Do we have to replace our existing reports?
No. Prism reads the same source data your existing reports read, and where a report is worth keeping it can be registered and run on schedule, with its output landing in Prism alongside everything else. Existing reports keep working throughout.
What if our data is incomplete?
That is normal, and Prism tells you rather than producing a confident wrong number. A readiness console checks fill rates on the fields each dashboard depends on and marks which modules your data can genuinely support today. Where a field is not being captured, that is a process fix, and it is better to know in week one.
See it on your own numbers
One hospital, one month of your data, and the exception list from your own billing.