Closed mocsharp closed 1 year ago
@mocsharp the only thing we would need to think of in the Workflow Manager is to add additonal functionality into evaluators (https://github.com/Project-MONAI/monai-deploy-workflow-manager/blob/develop/guidelines/mwm-workflow-spec.md#evaluators). Currently they support DICOM metadata (https://github.com/Project-MONAI/monai-deploy-workflow-manager/blob/develop/guidelines/mwm-workflow-spec.md#dicom-tags) but I imagine we would want to think about FHIR and HL7 support as well...what do you think?
@JoeBatt1989 Besides the evaluators, I think you will also need something to prepare the data before passing it to the evaluators.
@mocsharp the only thing we would need to think of in the Workflow Manager is to add additonal functionality into evaluators (https://github.com/Project-MONAI/monai-deploy-workflow-manager/blob/develop/guidelines/mwm-workflow-spec.md#evaluators). Currently they support DICOM metadata (https://github.com/Project-MONAI/monai-deploy-workflow-manager/blob/develop/guidelines/mwm-workflow-spec.md#dicom-tags) but I imagine we would want to think about FHIR and HL7 support as well...what do you think?
This issue proposes a change to the Workflow Request message to support multiple data sources/modalities: DIMSE, STOW, FHIR, HL7, and more. This change provides additional information for the Workflow Manager to handle, filter and process incoming requests.
The change removes the existing
calling_aetitle
andcalled_aetitle
properties and replaces them withtrigger
anddata_origins
:Example: an incoming FHIR message that fetches additional DICOM study:
Example: an incoming DICOM study via DIMSE:
Example: an incoming DICOM study via DICOMWeb STOW:
Example: an incoming HL7 message that triggers retrieval of data from FHIR server and PACS: