EXA9
— Run private operations —
Encrypted Medical Records
Encrypt every patient record once. Doctors see only what they need — enforced by the keys each role holds, not by policy alone.
The problem to solve
Hospital access controls are policy-based: IT decides who can see which fields, role-based access lists govern who reaches which records. Policy can be overridden, misconfigured, or socially engineered. Once a clinician has access, today's systems hand them the whole record — including the fields they don't need. The privacy of every patient depends on the strength of the weakest IT policy.
The solution it enables
Polymonial encrypts every record field-by-field. A cardiologist sees only the cardiology fields. Billing sees only the cost fields. A patient's psychiatric history, HIV status, and genetic markers stay encrypted unless a key for those fields has been issued. Access follows the keys each role holds, not only IT policy.
What it looks like
A hospital encrypts every patient record with Polymonial. When a cardiologist needs to see a patient's heart data, they receive access to only the cardiology fields. The patient's psychiatric history, their HIV status, their genetic markers — all remain encrypted. Access is enforced by the keys each person holds, not only by IT policy.
“A policy can be misconfigured. A key has to be issued. Your HIV status stays encrypted unless someone has been given the key to it.”
Who’s this for you?
We have this problem.
Your organisation needs this for its own data, product or programme of work.
We deliver this for clients.
A consultancy, integrator, service provider, industry programme or technology vendor.