Learn
Practical, evergreen guides on DICOM connectivity, DICOMweb, and receiving medical imaging data over standard HTTPS.
DICOM C-ECHO: Verification and connectivity testing
DICOM C-ECHO tests application readiness, AE titles, and TLS handshakes without sending patient data. Learn how it works and how to troubleshoot it.
DICOM C-STORE vs DICOMweb STOW-RS
C-STORE and STOW-RS both deliver DICOM instances — here's how the classic and web-based transfer protocols differ, and when to use each.
DICOM Instances, Series, and Studies explained
Understand the four-level Patient-Study-Series-Instance hierarchy in DICOM, how unique identifiers work, and why imaging arrives as many separate files.
DICOM SOP Classes and Transfer Syntaxes explained
Understand how SOP classes define clinical operations and transfer syntaxes control byte encoding, and why association negotiation depends on both.
Implicit vs Explicit VR in DICOM
Compare Implicit and Explicit Value Representation in DICOM. Learn why modern systems mandate Explicit VR and how Implicit VR creates parsing bugs.
Mutual TLS for DICOM connections
Why mutual TLS (mTLS) is the right way to authenticate and encrypt DICOM connections over the internet, and how it differs from a regular HTTPS client.
Receiving DICOM from a hospital over the internet
How to accept live DICOM studies from a hospital's scanners over the public internet, and what changes when the sender isn't on your LAN.
Site-to-site VPN vs internet-facing endpoints for DICOM
Compare site-to-site IPsec VPNs and internet-facing mTLS endpoints for hospital DICOM ingestion, including operational complexity, latency, and costs.
What is a DICOM Application Entity (AE) title?
An AE title names a DICOM service in up to 16 characters. Learn how AE titles work, why they fail, and why they provide identity without security.
What is DICOM Modality Worklist (MWL)?
DICOM Modality Worklist connects hospital scheduling with imaging scanners to eliminate manual data entry, prevent patient mismatch, and secure image intake.