Your images leave.
The patient stays.
Third-party radiology AI keeps coming up in strategy meetings. Legal keeps saying no because the images have to leave the network with patient identifiers still attached. PixelIQ™removes that blocker - inline, on-prem, before any study reaches any AI vendor.
Before and after PixelIQ™.
Everything currently standing between your practice and a third-party AI partnership.
Manual de-identification is not a DICOM strategy.It is a liability waiting to surface.
Most radiology practices rely on PACS export settings and hope. Private creator tags are invisible to header-only tools - and invisible to the practice until a breach notification arrives.
The PixelIQ™ pipeline.
Runs inside your network. Nothing raw ever leaves.
- 01
PACS / Modality
Study arrives via standard DICOM transport
- 02
Modality check
Studies from modalities that need extra identity handling are held back rather than released.
- 03
Header Scrub
PS3.15-aligned attribute coverage applied per configured profile
- 04
Policy Check
Release rules validated, recipient allowlist enforced
- 05
Governed Output
Clean study delivered. Tamper-evident ledger entry written.
Three things that change immediately.
PixelIQ deployed as DICOM proxy
Our team installs PixelIQ inside your network. Radiologists notice nothing. IT does not reconfigure modalities. Half-day on-site engagement.
No workflow changes for clinical staff
AI vendor connected
Your existing AI vendor relationship connects to the governed pipeline. They receive exactly what the data-use agreement permits. The legal blocker is architecturally removed.
Multiple vendors, single policy
First audit log ready
Every study that moves generates a tamper-evident audit entry - timestamped, exportable. From day one you have a record of every data movement, ready for review.
Exportable for HREC audit
What PixelIQ™ covers.
Modality-aware identity controls
Release rules account for the modality of every study. Studies that need extra identity handling are held back rather than released, so a study is never released on an assumption.
PS3.15 header scrub
All E.1 and E.2 profile attributes processed, configurable retain/remove/pseudonymise per tag.
SR & KO handling
Structured Reports, Key Objects, and Presentation States processed natively - not skipped.
Policy-gated release
Each destination receives only what its data-use agreement permits, and an unregistered destination receives nothing.
Tamper-evident audit ledger
Every anonymisation decision recorded in an independently verifiable ledger - exportable for HREC.
Built for PACS integration, not alongside it.
PixelIQ runs as a transparent DICOM proxy. Your PACS does not know it is there. No workflow changes for radiologists. No integration project for IT.
What radiology teams usually ask us.
Our board keeps asking about third-party radiology AI. Why can't we just share studies directly?
You can - with PixelIQ in place. Radiology AI vendors receive a governed, PS3.15-aligned dataset. Patient identity never leaves your network. You retain the audit trail. The contract review cycle shortens because the identity question is answered by the architecture.
Our PACS already has de-identification settings. Isn't that enough?
For most deployments, no. PACS de-identification tools process header fields, but private creator tags can carry patient identifiers that don't appear in standard DICOM headers - and are invisible to the practice until a breach notification arrives.
How does PixelIQ interact with our existing PACS and radiology workflow?
PixelIQ operates as a transparent DICOM proxy. Your PACS sends studies the same way it always has. Radiologists see no change. IT does not need to reconfigure modalities. PixelIQ sits inline and processes studies before they reach any downstream destination - on-prem, per study.
What is our liability position under the Australian Privacy Act if something goes wrong?
Under APP 11, you are required to take reasonable steps to protect the personal information you hold. Sending identifiable DICOM to an AI vendor without architectural controls is difficult to defend as 'reasonable'. With PixelIQ, PHI never reaches the external recipient - a far stronger basis for showing reasonable steps were taken.
How long does a trial deployment take?
A typical sandbox deployment - where we connect PixelIQ to your PACS, configure the anonymisation profile, and run a live demo against your study formats - is a half-day on-site engagement. There is no disruption to production workflows during the trial.