Clinics & Allied Health

Patient privacy.
Without a privacy team.

Small practices are expected to meet the same Privacy Act obligations as large health networks - without the IT department or compliance team to back them up. SECUVA fixes that.

See our threat model →
What changes

What SECUVA replaces.

Everything you are currently doing manually - and hoping is enough.

✗
The old way
Export DICOM from PACS and hope header settings are right
With SECUVA
Automatic, PS3.15-compliant anonymisation on every export
✗
The old way
Manually redact patient details from imaging reports
With SECUVA
NLP-based free-text de-identification, zero manual steps
✗
The old way
Email a spreadsheet of patient IDs to researchers
With SECUVA
Policy-gated data release - PHI never leaves your network
✗
The old way
No record of what data was shared or with whom
With SECUVA
Immutable audit log with every movement. Exportable on demand.
✗
The old way
Uncertainty about whether you're Privacy Act compliant
With SECUVA
OAIC APP 11 alignment built in. Report it any time.
Day one

Three things that change immediately.

Same-day deployment

Our team installs SECUVA Agent on-prem and connects to your PACS or EMR. Half-day engagement. No disruption to clinic operations.

Typically 4 hours end-to-end

Automatic anonymisation

Every study, note, and report that leaves your network is processed before it moves. No manual steps. No staff training required.

Inline, <50ms overhead

A paper trail you can show

Every data movement is logged, timestamped, and cryptographically signed. If a regulator or HREC asks, you have the answer ready.

Exportable audit report
Questions

Things practices usually ask us.

01

Do we need an IT team to set this up?

No. SECUVA is deployed by our team, typically in a half-day. You connect to your existing PACS or EMR via a standard protocol. Your staff don't notice it's there - and that's the point.

02

We already export DICOM files manually. Isn't that enough?

For most practices, no. Manual exports miss burnt-in pixel text, private creator tags, and secondary capture objects. These carry patient identifiers that don't appear in standard header fields and are invisible to export settings.

03

What happens if an AI vendor asks us to share data directly?

With SECUVA in place, you can say yes - safely. The vendor receives a governed, anonymised dataset. The raw data never leaves your network. You keep the audit trail. They get what they need.

04

How does SECUVA handle our compliance obligations under the Privacy Act?

SECUVA removes PHI before it leaves your perimeter, maintains an immutable audit log of every data movement, and aligns with OAIC APP 11 and DICOM PS3.15 - the two frameworks most relevant to clinical data sharing.

05

Is patient data stored in the cloud?

Raw patient data is never stored in the cloud. The SECUVA Agent runs on-prem inside your network. Only anonymised, governed outputs - and policy metadata - interact with the Australian cloud control plane.

06

What does pricing look like for a small practice?

SECUVA is priced per-modality and scales down for smaller practices. Book a demo and we will put together a quote based on your study volume and the modalities you need covered.

No IT team? No problem.

We have set up SECUVA for practices of every size. Tell us about your setup and we will tell you exactly what deployment looks like for you.

No sales pressure. Just a 30-minute call with a solutions engineer.