You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
MONAI Deploy was designed to support multiple/custom data ingestion and export services. In order to do so, the workflow schema must be updated to support it.
Describe the solution you'd like
The team should meet to discuss how to support custom data input and output services.
E.g. the export request event includes the name of the service (such as, md.export.request.monaiscu) which should be defined in the workflow definition so no code changes are required.
I've encountered a similar issue with MONAI Deploy. I'm particularly interested in initiating a workflow using the ISMRMRD format as input, and aiming to produce a DICOM as an output.
Can I somehow bypass this limitation by integrating directly into the message broker? Additionally, is the schema of the Workflow Request Event somewhere documented?
Thank you for highlighting this issue. Looking forward to a solution!
Hi @chdinh! atm, Workflow Manager does not support anything other than DICOM coming into the Informatics Gateway via DIMSE and that's why I have opened this issue. However, support for multisource and multimodality are in the works.
Is your feature request related to a problem? Please describe.
MONAI Deploy was designed to support multiple/custom data ingestion and export services. In order to do so, the workflow schema must be updated to support it.
Describe the solution you'd like
The team should meet to discuss how to support custom data input and output services.
E.g. the export request event includes the name of the service (such as,
md.export.request.monaiscu
) which should be defined in the workflow definition so no code changes are required.The text was updated successfully, but these errors were encountered: