DICOM Connector
The Flywheel DICOM Connector moves DICOM data from imaging devices and PACS directly into Flywheel. It is built on Flywheel's modern import pipeline, so Site Admins configure and monitor connections directly in the Flywheel web app.
Limited Release: DICOM Push (Flywheel 22.2)
The first capability of the modern DICOM Connector is DICOM Push — a Flywheel-hosted DICOM receiver that scanners and PACS can send to directly over the public internet, secured with mutual TLS (mTLS). DICOM Push is production-ready in Flywheel 22.2, with additional connector capabilities planned for future releases. It is not enabled by default — contact Flywheel Support to enable it for your site.
Already have a connector, or need PULL or on-premises PUSH?
If Flywheel already operates a DICOM Connector for your site, or you need a PULL or on-premises PUSH connector, see the Legacy DICOM Connector.
What DICOM Push provides
DICOM Push lets an imaging device or PACS send studies to Flywheel without any on-premises connector hardware:
- Flywheel-hosted receiver: Flywheel Core receives DICOM directly, so there is no connector to deploy or maintain at your site.
- Secure transport (mTLS): Each device authenticates to Flywheel, and Flywheel authenticates to the device, using mutual TLS. See Secure Connections (Mutual TLS).
- Per-device authorization: Administrators register each authorized device by certificate, hostname or IP, and Application Entity Title (AET) on the Interfaces → Connector → Manage Connections page.
- De-identification on ingest: DICOM data can be de-identified using your existing de-identification profiles before it is stored.
- Monitoring: DICOM Push activity is monitored alongside other imports in the Flywheel web app.
Get started
- Confirm that your device — or a network appliance in front of it — can make an outbound, mutually-authenticated TLS connection. See DICOM Push Connectivity Requirements.
- Contact Flywheel Support to enable DICOM Push for your site.
- Authorize your devices on the Interfaces → Connector → Manage Connections page (certificate, hostname or IP, and AET). See Manage Connections for step-by-step instructions.
In this section
- DICOM Push Connectivity Requirements — what your devices or appliances must support.
- Manage Connections — authorize devices, share the connector's certificate, and monitor activity.
- Secure Connections (Mutual TLS) — how Flywheel authenticates each device.
Related pages
- Legacy DICOM Connector — the Flywheel-managed connector for PULL, on-premises PUSH, and existing deployments.
- Getting Data In — all methods for importing data into Flywheel.