Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continue the Clinical Workflow after receiving the results back from a Remote Application #859

Open
JoeBatt1989 opened this issue Aug 4, 2023 · 4 comments
Milestone

Comments

@JoeBatt1989
Copy link
Contributor

JoeBatt1989 commented Aug 4, 2023

Describe the solution you'd like
The MIG will publish a Workflow Request event to inform the MWM that the results have been received and to continue. The MWM workflow initiation logic will need to be updated, if the message contains a valid workflowInstanceId then match with an existing workflow instance to carry on

New Workflow Request Schema

@JoeBatt1989 JoeBatt1989 added this to the 0.4.0 milestone Aug 4, 2023
@JoeBatt1989
Copy link
Contributor Author

@mocsharp @DanielNuttall-AD @neildsouth we need to agree on a schema for the update that differentiates normal export udpate messages from export message message (export)

@mocsharp
Copy link
Collaborator

mocsharp commented Aug 4, 2023

Hi @JoeBatt1989, MIG will publish a Workflow Request message md.workflow.request with the existing workflowInstanceId instead of publishing an update message. Therefore, when WM sees a Workflow Request message with workflowInstanceId, it can resume that workflow instance. Please let me know if you find any issues with this design.

Thanks!

@JoeBatt1989
Copy link
Contributor Author

JoeBatt1989 commented Aug 7, 2023

Thanks @mocsharp is MIG also including taskId as well, in case of multiple remote task exports?

@mocsharp
Copy link
Collaborator

mocsharp commented Aug 7, 2023

Yes, added taskId. Please review Project-MONAI/monai-deploy-messaging#210

This was referenced Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants