Trust & security
Who can reach it, who can change it, and who did
“Role-based access — every action attributed and audited” is the line the application itself carries on its sign-in screen. This page is what sits behind it, described in terms of what it means for your hospital.
01 · Who can reach it
Who can reach it
People sign in to a hospital, not to a shared login, and what they can open follows from who they are and where they work.
- Each person signs in as themselves, with their own credentials.
- What a role can open is decided per hospital, so a person working across units sees the right thing in each.
- An area a role is not given simply is not there for them — it is not merely hidden.
- Where a hospital already manages identity centrally, sign-in can follow it.
02 · What they can do once inside
What they can do once inside
Reaching a screen and being allowed to act on it are two different questions, and SanoBrix answers them separately.
- Individual actions — changing a price, switching a payer, applying a discount, closing a bill — are granted in their own right.
- The platform enforces those grants itself rather than relying on the interface to hide a button.
- Approval authority is separate again: the person who raises a purchase, refund or price change is not the person who approves it.
- Limits, such as how much a role may discount, are set by your own team.
03 · What happened, and who did it
What happened, and who did it
The platform is built so that “who changed this, and when?” has an answer that was recorded at the time rather than reconstructed afterwards.
- Who created a record and who last changed it is kept throughout the system.
- Changes to prices, cover, discounts and the closing of a bill leave their own record, visible where the change was made.
- Approvals are part of the record, with the approver and the moment.
- Reviewing activity is something your own staff can do in the application.
04 · How records are kept
How records are kept
Records are corrected and retired rather than erased, and the platform keeps the history of how something came to be what it is.
- Entries are withdrawn rather than deleted where history matters.
- Price lists, clinical summaries and documents are kept in version, so an earlier state can be shown.
- A reprint reflects the document as it stood when it was issued.
- Clinical and financial states are explicit — a bill line is draft, checked, closed, cancelled or refunded, not merely a flag.
05 · Where your data lives
Where your data lives
SanoBrix is deployed for your hospital. The decisions that matter most about your data stay with you.
- It runs in your own environment, under your own IT team’s control.
- Who can reach the system on your network, and how it is backed up, remain your decisions.
- One platform serves every unit you run, so there is a single system to keep current.
- External exchange, such as national digital health programmes, is switched on hospital by hospital rather than assumed.
Plain statement
On compliance claims
SanoBrix is designed with configurable access control, per-hospital roles and a record of who did what, which a hospital can use in meeting its own regulatory and accreditation obligations. PureBrix does not claim certification against any particular standard on this page.
Two things this page deliberately does not do: claim a certification the product has not been assessed against, and describe a control as stronger than it is. If an evaluation checklist needs a specific answer, ask us and we will answer it properly.
Send us your security questionnaire
We would rather answer a specific question about access, authority or accountability than publish a page of reassuring adjectives.