Use case · Healthcare
Protecting patient data without getting in the way of care
Patient records move between portals, integration engines, labs and clinical systems. CCL keeps them sealed in transit and at rest, and readable only where care happens.
- Patient records
- Referrals and results
- Insurance and identity details
- Clinical notes
The challenge
Where the data goes today.
Healthcare data is among the most sensitive data there is, and it has to move. Referrals, results and records flow between patient portals, integration engines, laboratories, clinical systems and third-party suppliers every day.
Strict end-to-end encryption is rarely practical, because clinical systems genuinely need to read the data. The result is that many intermediate systems can read it too.
Where it’s readable
- Patient portals and online forms
- Integration engines and message brokers that route records between systems
- Third-party apps and suppliers connected to core systems
- Analytics and reporting copies
- Backups and test environments built from real records
How CCL applies
The same journey, sealed where it doesn’t need to be read.
- Patient portalBrowser SDK
Information a patient enters is sealed in their browser.
- Integration layerGateway
Where the integration layer only routes records, it does so without being able to read them. Where it must transform them, it becomes an authorised endpoint.
- Clinical systemBroker
Only the authorised clinical application opens the record, so care workflows carry on as normal.
- Records storeProtected Storage
Records are sealed again before they are stored or backed up.
What changes
The outcome.
Care workflows keep working
Clinicians use the same applications. CCL protects the data around them, not instead of them.
Less exposure through suppliers
Systems that only move records no longer need to be trusted with their contents.
Supports GDPR and NIS2 objectives
Health data is special-category data under GDPR, and healthcare is in scope for NIS2. CCL helps demonstrate technical protection.
CCL is in development. This use case describes how the v1.0 design is intended to apply.
Related insights
The breach that starts somewhere boring
Serious incidents rarely begin with a movie-style hack. They begin with a debug log, a forgotten test database or an over-privileged service account.
- Breaches
- Containment
Where your customers' data is exposed today
Encrypted in transit, encrypted at rest. Follow one piece of customer data through your stack and count how often it is neither.
- Data exposure
- Architecture
Trust less, prove more
Every system you run asks to be trusted. The strongest security removes that need wherever it can, and makes the rest visible.
- Principles
- Trust
Contact
Get in touch.
Whether you’re exploring how to protect your clients’ data, interested in CCL, or want to work with us, we’d like to hear from you.