One patient record, one audit trail
Replacing paper files and spreadsheets with a record model that can answer who saw what.
Demonstration content. This write-up is an illustrative example used while the site is being populated. The client is fictional and no figure here describes a real engagement.
Context
A private hospital keeping patient information across paper files, departmental spreadsheets and a legacy billing package.
The challenge
Nobody could answer access questions with confidence. Records were duplicated between departments, and billing frequently disagreed with what had actually been provided.
Our approach
We treated access control as part of the data model rather than a UI concern, so a permission cannot be bypassed by reaching the data another way.
What we built
One patient record with department-scoped permissions enforced at the query layer, an append-only audit log for every read and write, and billing derived from recorded activity instead of separate entry.
The outcome
Access questions are answered from the audit log, and billing reflects what the record says happened.
What we were aiming for
- A single patient record used by every department
- Access control that is provable, not assumed
- Billing generated from the record rather than re-entered
Tell us what you need
Four fields. A real person reads it and replies within one working day.
info@devnainc.com