-
Notifications
You must be signed in to change notification settings - Fork 22
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
Workflow Request Message change request #127
Workflow Request Message change request #127
Comments
@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.
|
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:
The text was updated successfully, but these errors were encountered: