Skip to content

Latest commit

 

History

History
120 lines (84 loc) · 5.22 KB

services.md

File metadata and controls

120 lines (84 loc) · 5.22 KB

MONAI Deploy Informatics Gateway Services

MONAI Deploy Informatics Gateway supports the following standard protocols for communicating with medical devices:

Note

The ACR DSI API uses the DICOMweb client and FHIR client.

DICOM SCP

The DICOM SCP Service accepts standard DICOM C-ECHO and C-STORE commands, which receive DICOM instances for processing. In addition, the Informatics Gateway groups received DICOM instances by the study or series based on the configuration. Once DICOM instances are grouped, they are assembled into a payload for the MONAI Deploy Workflow Manager to consume.

Workflow Request

With a DICOM SCP triggered workflow request, the data trigger contains the following:

  • DataService: DataService.DIMSE
  • Source: <calling AE Title>
  • Destination: <called AE Title>

DICOM SCU

The DICOM SCU Service allows users to export application-generated DICOM results to external DICOM devices. It subscribes to the md.export.request.monaiscu events generated by the MONAI Deploy Workflow Manager, then exports the data to user-configured DICOM destination(s).

Note

DICOM instances are sent as-is; no codec conversion is done as part of the SCU process. See the DICOM Interface SCU section for more information.

DICOMWeb STOW-RS

The DICOMWeb STOW-RS Service allows users to trigger a new workflow request by uploading a DICOM dataset. The entire DICOM dataset is assembled into a payload for the MONAI Deploy Workflow Manager to consume. It provides options to trigger a workflow with or without specifying a workflow ID/name. See the DICOMWeb STOW-RS section for more information.

Workflow Request

With a DICOMWeb STOW-RS triggered workflow request, the data trigger contains the following:

  • DataService: DataService.DicomWeb
  • Source: <caller's IP address>
  • Destination: default or <name of Virtual AE Title>

HL7 MLLP Server

The HL7 MLLP Server accepts Health Level 7 messages via the MLLP (Minimal Lower Layer Protocol). The received messages are validated and assembled into a payload for the MONAI Deploy Workflow Manager to consume.

Workflow Request

If a workflow request is triggered by an HL7 MLLP Server, the data trigger contains the following:

  • DataService: DataService.HL7
  • Source: <caller's IP address>
  • Destination: <MIG's IP address>

ACR DSI API

The ACR DSI API allows users to trigger inference requests via RESTful calls, utilizing DICOMweb and FHIR to retrieve data specified in the request. Upon data retrieval, the Informatics Gateway uploads the data to the shared storage and generates an md.workflow.request event, which notifies the MONAI Deploy Workflow Manager for processing. See the Inference API for more information.

Workflow Request

If a workflow request is triggered by the ACR DSI API, the data trigger contains the following:

  • DataService: DataService.ACR
  • Source: <transaction ID from the ACR request>
  • Destination: <MIG's IP address>

DICOMweb Export

A DICOMweb export agent can export any user-generated DICOM content to configured DICOM destinations. The agent subscribes to the md.export.request.monaidicomweb events generated by the MONAI Deploy Workflow Manager, then exports the data to user-configured DICOMweb destination(s).

FHIR Server

The FHIR Server accepts FHIR resources as described in the FHIR API section. When data arrives at the service, each resource is packaged into a payload and a workflow request is sent to the MONAI Deploy Workflow Manager.

Workflow Request

With an FHIR Server triggered workflow request, the data trigger contains the following:

  • DataService: DataService.FHIR
  • Source: <caller's IP address>
  • Destination: <MIG's IP address>