Protocol Complexity
DICOM is a 30-year-old binary protocol with complex association negotiation, transfer syntaxes, and service classes.
Medical Imaging Protocol
DICOM Connector
Native DICOM protocol support for medical imaging integration. Connect PACS, modalities, and AI platforms without writing custom DICOM code.
Available Now
The Challenge
DICOM integration is complex
Custom Code Required
Building DICOM integrations typically requires specialised libraries, deep protocol knowledge, and months of development.
Security Gaps
Legacy DICOM implementations often lack encryption, proper authentication, and audit trails required for compliance.
The Solution
DICOM as configuration
Harmony's DICOM connector handles protocol complexity so you can focus on your integration logic. Define pipelines in configuration, not code.
Protocol Translation
Convert DICOM to JSON, DICOMweb, or custom formats using declarative JOLT transforms.
Metadata Extraction
Extract DICOM tags into structured JSON for downstream processing and routing decisions.
TLS Encryption
Secure DICOM connections with TLS 1.2/1.3 for data in transit protection.
Audit Logging (coming soon)
Comprehensive logging of all DICOM operations for compliance and troubleshooting.
# DICOM to AI pipeline
[pipelines.dicom_to_ai]
description = "Receive DICOM and transform to JSON for AI"
networks = ["dicom_net"]
endpoints = ["dicom_listener"]
middleware = ["dicom_flatten", "transform_to_json"]
backends = ["ai_cloud_api"]
# DICOM endpoint
[endpoints.dicom_listener]
service = "dicom_scp"
[endpoints.dicom_listener.options]
local_aet = "AI_GATEWAY"
enable_store = true
# Backend
[backends.ai_cloud_api]
service = "http"
target_ref = "ai_service"
DIMSE Operations
Full DICOM service class support
Act as Service Class Provider (SCP) or Service Class User (SCU) for all standard DICOM operations.
C-STORE
Receive and forward DICOM images from modalities, PACS, and other sources.
Example: Accept imaging studies from CT scanners, MRI machines, or workstations.
C-FIND
Query DICOM servers for studies, series, and instances matching specific criteria.
Example: Search for patient studies by date, modality, or accession number.
C-GET
Retrieve DICOM objects from a remote server over the same connection.
Example: Pull specific imaging studies for processing or analysis.
C-MOVE
Instruct a remote server to send DICOM objects to a specified destination.
Example: Route studies from PACS to workstations or AI processing pipelines.
Capabilities
Enterprise-grade DICOM handling
Protocol Translation
Convert DICOM to JSON, DICOMweb, or custom formats using declarative JOLT transforms.
Metadata Extraction
Extract DICOM tags into structured JSON for downstream processing and routing decisions.
TLS Encryption
Secure DICOM connections with TLS 1.2/1.3 for data in transit protection.
Audit Logging (coming soon)
Comprehensive logging of all DICOM operations for compliance and troubleshooting.
Workload Templates
DICOM Workload Templates
Pre-configured templates for medical imaging integration
DICOM to AI Gateway
Transform DICOM to JSON for cloud AI processing
Medical Image Analysis
AI Pipeline Integration
HealthcareDICOM
Learn more →
DICOM Backend
HTTP to DICOM medical imaging proxy
REST to DICOM
Medical Imaging Integration
HealthcareDICOM
Learn more →
DICOM C-STORE to Filesystem
Store DICOM images to local filesystem
Image Archival
Local PACS
HealthcareDICOM
Learn more →
DICOM C-STORE to JMIX
Receive DICOM images and package into JMIX envelopes
DICOM to JMIX Gateway
Modality Integration
HealthcareDICOM
Learn more →
DICOM Receiver (SCP)
DICOM Service Class Provider endpoint
Image Reception
Study Routing
HealthcareDICOM
Learn more →
DICOM to DICOMweb
Convert DICOM requests to the DICOMweb protocol
Legacy DICOM Integration
Protocol Translation
HealthcareDICOM
Learn more →
Get Started
Connect your imaging systems
Deploy DICOM integrations in hours, not months. No custom code required.