SemanticMD Cloud

The SemanticMD Cloud Developer Hub

Welcome to the SemanticMD Cloud developer hub. You'll find comprehensive guides and documentation to help you start working with SemanticMD Cloud as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Integration Overview


This guide provides an overview of SemanticMD's DICOM and HL7 connectivity. HL7 is one of the standard ways of passing medical information between medical systems. SemanticMD's API supports receiving (incoming) DICOM and sending (outgoing) HL7 messages. The outgoing HL7 message formats supported are orders (OMR^O01) and reports (ORU^R01).

This guide will discuss the following topics:

  • Incoming DICOM messages and workflow
  • Outgoing HL7 messages and workflow
  • Sample messages
  • HL7 message segments and fields

Incoming DICOM Messages and Workflow

PACS is a system for digital storage, transmission, and retrieval of radiology images. Any DICOM data in a PACS server can be automatically routed securely to SemanticMD for analysis in the cloud or on-premises.

The DICOM images are received at SemanticMD's secure DICOM server. Then, the images are processed using our deep learning algorithms, and the prediction probabilities are sent back to a PACS or EHR, securely and in under a second.

We also provide a REST API endpoint connected to distributed object storage server, which we recommend when uploading large volumes of data.

Outgoing HL7 Messages and Workflow

Upon completion of the analysis, our web server sends HL7 messages to your EHR or DICOM enabled device, as designated in the configuration settings. The message generator is highly configurable. The messages described below are the most common messages generated; however other types of HL7 messages can be generated as required. When complete, the report can be sent via ORU^R01 to a target EHR.

An ORU^R01 message is an unsolicited transmission of an observation. Colloquially, we refer to ORU^R01s as reports. It is highly useful to store the report with the imaging. The client receives the ORU^R01 and ties the report to the study.

As soon as the ORU^R01 is received, the report appears attached to the study. Those with the appropriate permissions can search for, find, and review the study report at any time. Below is an example ORU^R01 message:

|168715|P|2.5 PID|||1||SARFATI^MICHAEL OBR||||10000 OBX|1|ED|PDF||normal: 0.874313
abnormal: 0.125686824322||||||F

Below is an overview of the message fields and headers contained in the HL7 message:

DICOM SR Support

For simplified integration with PACS, we also provide an encapsulation of algorithm responses (JSON) as DICOM Structured Report (SR). The example below can be downloaded here.

Integration Overview

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.