Governance infrastructure

Patient identity
never leaves.

The centralised data privacy & governance platform for Australian healthcare. Anonymise, govern and audit every modality before it reaches an AI service.

DICOM PS3.15HL7 / FHIROAIC AlignedAU Data Residency
Built around the standards Australian healthcare actually uses
DICOM PS3.15-alignedHL7 FHIR R4OAIC De-identification GuidancePrivacy Act 1988 (Cth)My Health Records Act 2012ISO 27001:2022 alignmentHREC submission readyEssential Eight (ACSC)AU sovereign cloud infrastructureDICOM PS3.15-alignedHL7 FHIR R4OAIC De-identification GuidancePrivacy Act 1988 (Cth)My Health Records Act 2012ISO 27001:2022 alignmentHREC submission readyEssential Eight (ACSC)AU sovereign cloud infrastructure
100%
Australian data residency
Sovereign AU infrastructure
Comprehensive
DICOM PS3.15 attribute coverage
Anonymised by default
Zero
Raw PHI in transit
Removed on-prem
Inline
Low-latency pipeline
Runs at the edge
The problem

Healthcare AI is moving fast.
Patient identity is moving with it.

SECUVA lets healthcare teams accelerate AI without sacrificing compliance - by removing patient identity from every clinical surface before it leaves your network.

Identity leaks at the edges

Header fields, burnt-in pixel overlays, free-text clinical notes - every modality hides identity in surfaces standard pipelines miss.

Manual de-id doesn't scale

One-off scripts and PACS export settings don't survive multi-modal AI workflows or a regulator's audit.

Proof is missing

Boards, HRECs and regulators want defensible evidence. Most teams can't produce it from email chains and spreadsheets.

Healthcare Organisation network · on-prem
PACS / DICOM
EMR / FHIR
Research DB
↓ raw clinical data ↓
SECUVA Layer
anonymise · validate · route · govern
PixelIQSlideIQGenomeIQCardioIQClinicalIQSignalIQ
governed output only · patient identity never leaves your firewall
SECUVA control plane · AU sovereign cloud
Policy engine
Audit trail
Routing rules
↓ approved recipients only ↓
AI vendor
de-id data only
Researcher
HREC approved
Internal model
within perimeter
The platform

One privacy layer between
your data and every AI service.

SECUVA runs entirely within your environment, under your control, paired with an Australian cloud-hosted control plane. PHI is removed where it lives. Only governed, auditable outputs ever cross your firewall.

Raw PHI never crosses your firewall
Australian data residency, sovereign control plane
Connects to PACS, EMR, FHIR, research systems and AI vendors
Every action recorded in a tamper-evident ledger - independently verifiable
How it works

Four steps. Zero raw PHI in transit.

01

Connect

SECUVA agent registers as a DICOM node, HL7 listener, and FHIR proxy inside your network - minimal network configuration required.

02

Anonymise

PHI removed from headers, pixel overlays, free-text fields and structured reports using modality-specific PS3.15-aligned profiles.

03

Govern

Policy engine determines what leaves your perimeter, where it goes, and which AI service is permitted to receive it.

04

Audit

Every transformation recorded in a tamper-evident ledger. Exportable for OAIC, TGA, HREC, and internal governance review.

The difference

The day you switch SECUVA on.

Scenario
AI vendor requests DICOM data
Without SECUVA
Manual export, zip, email - with full patient headers attached
With SECUVA
Automated pipeline: de-identified within your environment, then securely routed through approved pathways.
Scenario
Researcher needs a study cohort
Without SECUVA
IT project, 3–6 months, manual spreadsheet de-id, no audit trail
With SECUVA
Automated cohort build, HREC-exportable audit trail, days not months
Scenario
OAIC asks what left your network
Without SECUVA
"We believe it was de-identified" - no records to show
With SECUVA
Cryptographic log: what, when, who, which profile - exportable in minutes
Scenario
New AI vendor onboarding
Without SECUVA
Legal review cycle, custom de-id pipeline per vendor, inconsistent output
With SECUVA
Vendor added to allowlist, same pipeline, same audit standard
Scenario
Multi-site clinical trial
Without SECUVA
Each site uses different scripts, inconsistent PHI removal, no central log
With SECUVA
Same profile deployed everywhere, consistent pseudonymous IDs, central audit

Patient identity
never leaves.

Show us your data flows - PACS, EMR, research, AI vendors. We will show you exactly where SECUVA fits and what changes the day you switch it on.