The VoxelMD platform
PHI never leaves your network.
De-identified on your hardware, processed in a BAA-covered HIPAA cloud, and waiting when the radiologist opens the study.
Five steps, one trust boundary.
- 01Your PACS forwards the study
- 02De-identified on your hardware
- 03Only de-identified data leaves, outbound
- 04Drafted while it sits on the worklist
- 05Waiting when the radiologist opens it
Three things never leave your site.
It holds because of architecture, not paperwork.
Patient identifiers
Removed on your site, burned-in pixel text included.
The identity crosswalk
Encrypted, and kept only on your network.
Re-identification
Not possible from our side, by design.
The radiologist never waits for AI.
Processing runs while the study is on the worklist. One click pushes the draft into your dictation software.
Typical AI tool
Study opens, then the radiologist waits
VoxelMD
Processed on the worklist, ready at open
Built for the security review.
Outbound only
One HTTPS rule. No VPN, no inbound ports.
Standards-based de-identification
DICOM PS3.15 profiles, HIPAA Safe Harbor.
Cloud run to PHI standards
BAA, customer-managed keys, per-site isolation.
Full audit trail
Immutable, retention-locked logs.
BAA by default
Signed even though data is de-identified.
SOC 2 readiness
Third-party penetration testing before go-live.
Three steps your IT team knows.
One VM
On your premises or your own cloud.
One firewall rule
Outbound HTTPS to a named endpoint.
One PACS routing rule
A standard auto-forward destination.
Put it in front of your security team.
We walk IT and compliance through it, question by question.