Patient data & healthcare

The Kafka platform for healthcare organizations

Connect clinical systems, monitoring devices, and analytics with governed, auditable Kafka on infrastructure you control.

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

Clinical data moves between systems that were not designed to talk to each other

EHRs, PACS, lab, pharmacy, and monitoring systems each hold part of the patient picture. Batch processes and point-to-point connections make every new integration harder to maintain and audit.

Four problems, one streaming layer

Real-time event processing

Process patient monitoring, capacity, medication, and device events as they happen. Replayable streams let systems catch up after downtime without losing data.

Interoperability across systems

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

Allocation and reconciliation

Stream validated clinical and operational events continuously to S3, Azure Data Lake Storage, Snowflake, Elasticsearch, and OpenSearch.

Secure data sharing

Share selected event streams with institutions, regional networks, or research programmes. Each application receives approved topic access, and every grant is recorded.

Governance across every patient data flow

Control access to patient data, schemas, and clinical event streams centrally. Every change is recorded automatically, giving auditors clear evidence without relying on spreadsheets.

Controls

Authentication: mTLS, SASL, and OAuth
Authorisation: role-based access control, ownership groups, and approval workflows on every access request
Encryption in transit between clients, brokers, and clusters
Apicurio schema registry with OAuth, validation enforced on every event
Audit history (2026.1): every create, modify, delete, access request, and approval across topics, applications, schemas, groups, environments, clusters, tenants, and users, filterable by resource, actor, action, and time range
Authentication: Environment separation between development, acceptance, and productionmTLS, SASL, and OAuth
Topic graph showing every producer and consumer per topic
NIS2
compliant
NEN 7510
compliant
ISO 27001
compliant
GDPR
compliant
View our ISO 27001 certification

Add event streaming without replacing clinical systems

Axual sits on Kafka, and Kafka sits on your infrastructure. Existing systems reach it through connectors. Nothing has to move to a vendor cloud for the platform to work.

Connectors for IBM MQ, AMQP 1.0, JDBC, Debezium change data capture on PostgreSQL, MySQL, SQL Server and MongoDB, MQTT for device telemetry, and sinks to S3, Azure Data Lake Storage, Snowflake, Elasticsearch, OpenSearch, and Splunk
Any Kafka Connect plugin is supported, the platform adds no restrictions beyond Kafka Connect's own
The Distributor synchronises messages, offsets, and schemas between Kafka clusters, so a consumer failing over to a second cluster resumes at the right position
Multi-cluster deployment across data centres, and between on-premises and cloud
Consumer offset reset by timestamp for controlled replay and recovery
Kubernetes-native: OpenShift, on-premises, or private cloud
Topics, applications, and connectors managed in one interface, or through Terraform

Running where downtime
is not an option

Logius

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

Read more

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.

Read more

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

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.

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.

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.