Medical middleware for OEMs
DicomPulse is a modular C++20 SDK that gives any medical imaging device or system, from C-arms and mobile X-ray to ultrasound, acquisition workstations and gateways, secure DICOM networking, object creation, anonymization and a hash-chained audit trail — developed under an IEC 62304 lifecycle.
Association handling and the full SCU surface, with TLS 1.3 hardening.
Build DICOM objects from what your device already produces: images, PDFs, video, reports.
Encrypted configuration and a hash-chained audit log you can verify.
DicomPulse sits between your acquisition software and the hospital's PACS. Call the C++ API, or let the Watcher do it from a folder.
With the C++ API
Or with the Watcher, no code
Use only what your product needs. Each module is verified and documented on its own.
C-ECHO, C-STORE, C-FIND, C-MOVE and C-GET over TLS 1.3, with Storage Commitment: wait for the PACS to confirm that an object is archived. SCP listener to receive C-ECHO and C-STORE. Asynchronous operations returning std::future.
Build native DX, CR, CT, MR and US images, Secondary Capture, Encapsulated PDF, Grayscale Softcopy Presentation State and Comprehensive Structured Report. H.264 MP4 video stored as Video Photographic, Endoscopic or Microscopic objects, without re-encoding. JPEG Lossless, JPEG 2000 and JPEG-LS; lossy is never the default.
PS3.15 Basic Profile de-identification with consistent pseudonyms, UID remapping, optional date shifting and burned-in text warnings.
Asynchronous, hash-chained logger designed for IEC 62304-traceable operation records.
Centralized encrypted JSON profiles for deployment and setup.
Modality Worklist / MPPS synchronization and RDSR dose reporting are planned modules.
dicompulse-service, a gRPC-oriented daemon for headless orchestration of the SDK.
The API is plain C++20 and asynchronous: operations return a std::future.
DicomPulse::Network::NetworkConfig cfg;
cfg.enableTLS = true;
cfg.caCertificatePath = "certs/ca.pem";
cfg.verifyPeerCertificate = true;
cfg.storeMaxRetries = 2; // auto-retry
DicomPulse::Network::NetworkManager nm(&logger);
nm.SetNetworkConfig(cfg);
std::vector<std::string> files = { "img001.dcm" };
auto store = nm.SendStorageRequest(
"CALLING_AET", "PACS_AET", "192.168.1.10", 11112, files);
DicomPulse::Status status = store.get();DicomPulse::Anonymization::Anonymizer anonymizer(&logger);
DicomPulse::Anonymization::AnonymizationOptions options;
// secret: at least 16 characters
options.pseudonymSecret = secretFromSecureStore;
options.shiftDates = true; // keep intervals
anonymizer.SetOptions(options);
DicomPulse::Anonymization::AnonymizationResult result;
DicomPulse::Status status =
anonymizer.AnonymizeFile("in.dcm", "out.dcm", &result);
if (status == DicomPulse::Status::BurnedInTextWarning) {
// pixels may contain patient text: review it
}Excerpts. The full API is described in the SDK documentation.
Reference application
A hot-folder service, built on the SDK, that turns files dropped in an inbox into DICOM objects and forwards them to one or more PACS. No code to write: configure it, drop files in, and it delivers.
A de-identified copy follows the DICOM PS3.15 Basic Profile. Example with fictitious data.
| Attribute | Original | De-identified copy |
|---|---|---|
| Patient's Name | ROSSI^MARIO | DP3F9A1C07B2E45D81 |
| Patient ID | PAT-9910 | DP3F9A1C07B2E45D81 |
| Patient's Birth Date | 19750312 | removed |
| Study Date | 20261014 | 20260916 (shifted, optional) |
| Study Instance UID | 1.2.840.113619.2.55.3… | 2.25.1840273… |
| Institution Name | Ospedale San Marco | removed |
| Referring Physician | BIANCHI^LUCA | removed |
| Private attributes | (0009,1001) vendor data | removed |
| Body Part Examined | CHEST | CHEST (kept) |
| KVP | 70 | 70 (kept) |
| Pixel Data | unchanged | unchanged |
| Patient Identity Removed | — | YES |
DicomPulse is developed as a Class B software item. The lifecycle documentation set is part of the product.
Intended use, safety classification, development plan, requirements, architecture, risk management, FMEA, verification and validation reports, and a traceability matrix.
Vulnerability analysis and a maintained SBOM, TLS 1.3 transport and encrypted configuration.
Intended use. DicomPulse is middleware for data exchange and DICOM object creation. It does not perform diagnosis or image interpretation and does not alter the clinical content of images.
C-arms and mobile units: send acquisitions and reports to the hospital PACS.
Create DX, CR, CT, MR and US images and deliver them reliably, with retry and failover.
Embed DICOM transport and object creation in your own software.
Convert files from other sources (PDF, images, video) into DICOM with the Watcher.
Tell us about your product and we will walk you through the SDK and its documentation set.