Patient data & healthcare

The Kafka platform for healthcare organizations

Real-time patient and clinical data exchange, with every access controlled and logged, on infrastructure you control. On-premises, hybrid, or in your own cloud.

Book a demo
Contact us
17,000
Healthcare organisations reached, Norsk Helsenett
99.999%
Platform availability, Public healthcare organisation
Sub-100ms
Clinical event latency, Norsk Helsenett
100%
On your infrastructure,
if you want it
Rated with a 4.5 from more than
13 G2 reviews
Healthcare on batch

Care happens in real time. Patient data doesn’t.

Admissions, lab results, referrals, and medication changes happen every minute, but move between hospitals, labs, GPs, and pharmacies in batches or point-to-point interfaces. Clinicians decide on incomplete information, and staff re-enter data by hand. Axual shares each update with the systems and organisations that need it as it happens, through one governed platform where every access is controlled and logged.

Why healthcare organisations choose Axual

The right data, at the point of care

Real-time clinical events

Monitoring, capacity, medication, and device events reach the right systems as they happen. If a system goes down, it catches up from the stream afterwards, without losing data.

Interoperability across systems

Connect EHR, PACS, laboratory, and pharmacy systems through one exchange layer instead of separate interfaces. Legacy systems use existing connectors, while modern services consume events directly.

Analytics and research

Feed analytics and research platforms with live, validated data, without extra load on clinical systems. Stream clinical and operational events to S3, Azure Data Lake Storage, Snowflake, Elasticsearch, and OpenSearch.

Secure data sharing

Share selected data with other institutions, regional networks, or research programmes, and nothing more. Each application needs approved access, and every grant is recorded.

Controls your auditors can see

Real time, with every control in place

Patient data is among the most sensitive data there is. Axual controls who can produce, consume, and manage every stream, and records every action automatically. Governance is enforced by the platform, not by policy documents.

Only the right people get in. mTLS, SASL, and OAuth authentication, with role-based access control and secrets managed in HashiCorp Vault.
Access only with approval. Every request to use a stream is approved by its owner, so you can show which applications use which patient data.
Patient data stays hidden. Field-level masking in Topic Browse, set by the schema owner, with a strict mode that prevents unmasking.
A complete audit trail. Every create, change, deletion, access request, and approval, filterable by resource, person, action, and time.
See who uses what. An overview graph of every producer and consumer per stream.
Test safely before going live. Separate development, testing, and production environments, so test teams never need production patient data.
NIS2
ready
NEN 7510
ready
ISO 27001

‍certified
GDPR
ready
View our ISO 27001 certification
Sovereignty & compliance

Patient data that stays
‍under your control

Patient data stays inside

The full platform runs in your own data centre or cloud account. No data is routed through Axual, and the supplier is EU-owned, based in the Netherlands.

Care keeps running

Multi-AZ and multi-cluster deployment keep data flowing when part of your infrastructure fails, with certificate expiry flagged before it can cause an outage.

Evidence for your auditors

Access approvals and a complete audit history support your GDPR, NIS2, and NEN 7510 obligations.

Continuity beyond any contract

Built on Apache Kafka and Strimzi, so your services keep running on standard Kafka, whatever the outcome of the next tender.

Built for the infrastructure you already have

Real-time patient data without replacing your EHR

Axual connects the clinical and administrative systems you already run and streams their data in real time, on-premises, in your own cloud, or both.

Diagram showing a three-layer stack with Axual at the top including connectors like Databases, APIs, SaaS, Data lakes, and Message Queues; Kafka in the middle with components such as Kafka Connect, Kafka Streams, and Brokers; and Infra at the bottom with Deployment, Kubernetes, Cloud, Operators, and Monitoring components.
Connects to what you have, including legacy. Ready-made connectors, plus a REST Proxy for systems that can’t run a Kafka client.
Runs where patient data must stay. On Kubernetes or OpenShift, in your own data centre or cloud account.
Moves data between on-prem and cloud. Axual Distributor syncs messages, schemas, and offsets between clusters.
Migrates without a cutover. Built on standard Apache Kafka, so existing applications keep working while you move.
Topics, applications, and connectors managed in one interface, or through Terraform
In production in critical public infrastructure

Running where downtime
is not an option

Modern building complex under sunset sky near a body of water, surrounded by snowy landscape and parked cars, with a yellow bus on a road in front.

Norsk Helsenett

Norway's national health network

Secure event streaming for the organisations connected to the national health network, with audit coverage across platform changes and availability targets set for clinical use. Today Axual provides secure event streaming for 17,000 healthcare organisations, with full audit coverage across clinical data flows.

Read the Norsk Helsenett story
Evening cityscape featuring historic buildings with warm lights reflecting on calm water in the foreground and modern skyscrapers in the background.

Logius

Dutch government service provider A governed on-premises Kafka platform delivering real-time messaging, data sovereignty, and auditability for national government communications.

Read the Logius story
Ready when you are

See how Axual fits your clinical estate, your compliance requirements, and your integration roadmap.

Book a demo
Contact us

Frequently asked questions

Can Axual run in our healthcare organisation’s own data centre?

Yes. Axual can run on premises or in your own cloud, including OpenShift environments. It also supports firewalled environments where healthcare data must remain under your control.

Does Axual support HL7 and FHIR data?

Axual can carry HL7v2 messages and FHIR resources alongside other event data. Avro, JSON, and Protobuf schemas can be validated through the schema registry. Mapping between your healthcare integration engine and Kafka requires a separate connector or service.

How does Axual protect patient data?

Role-based access control limits each application to approved topics and environments. Access requests, approvals, and governance changes are recorded automatically for auditing. Axual runs in your own data centre or cloud account, and no data is routed through Axual.

Can we track who accessed a patient data stream?

Axual records access requests, approvals, and governance changes, including the actor, action, resource, and timestamp. Per-record consumption must be logged by the consuming application or broker.

Is Axual an alternative to Confluent?

Yes. Axual is an enterprise Kafka platform for organisations that handle patient data, built on open Apache Kafka and Strimzi and running on infrastructure you control. Every access request is approved by the data owner and recorded in the audit history, supporting your NEN 7510 and GDPR obligations, and data masking lets operators inspect message flows without seeing patient data. Norsk Helsenett uses Axual for secure event streaming across 17,000 healthcare organisations.

How do you handle patient data in streams?

Schema owners mark fields as masked, and stream owners can mask additional fields per environment. Masked fields are hidden in Topic Browse, and strict masking prevents unmasking. This controls what users see in the platform, not what is written to the stream, so encryption or pseudonymisation at the source remains your responsibility.

How does Axual support healthcare GDPR compliance?

Axual helps healthcare organisations control where patient data flows, who can access it, and how long it is retained. Retention policies, keyed compaction, and careful payload design can support erasure requirements for event streams.

Can we securely share healthcare data with other institutions?

Yes. Hospitals, regional networks, and research programmes can receive access to selected topics without connecting to your source systems. Access can be withdrawn centrally at any time.

Can Axual work with our existing Kafka or Strimzi environment?

Yes. Axual Governance can run with an existing Strimzi environment, or Axual can manage the platform under an enterprise SLA. Migration services are available when required.

How much does Axual cost for healthcare organisations?

Pricing depends on the deployment model, support level, and platform scale. Contact us for a tailored plan.

How do healthcare organisations use Apache Kafka?

To share clinical and administrative data continuously instead of in scheduled batches. Typical uses are data exchange between care organisations, real-time clinical events such as lab results and admissions, connecting EHRs with departmental systems, and feeding analytics and research. Axual adds the governance layer on top of open Kafka: stream ownership, schema validation, access approvals, and an audit history of every change.

How do healthcare organisations use Apache Kafka?

To share clinical and administrative data continuously instead of in scheduled batches. Typical uses are data exchange between care organisations, real-time clinical events such as lab results and admissions, connecting EHRs with departmental systems, and feeding analytics and research. Axual adds the governance layer on top of open Kafka: stream ownership, schema validation, access approvals, and an audit history of every change.