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

Workflow Request Message change request #127

Closed
mocsharp opened this issue Mar 21, 2023 · 2 comments · Fixed by Project-MONAI/monai-deploy-messaging#215
Closed

Workflow Request Message change request #127

mocsharp opened this issue Mar 21, 2023 · 2 comments · Fixed by Project-MONAI/monai-deploy-messaging#215
Assignees
Labels
enhancement New feature or request

Comments

@mocsharp
Copy link
Collaborator

mocsharp commented Mar 21, 2023

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 and called_aetitle properties and replaces them with trigger and data_origins:

Example: an incoming FHIR message that fetches additional DICOM study:

{
  "trigger": {
    "type": "fhir",
    "source": "server-xyz",
    "destination": "1.2.3.4"
  },
  "data_origins": [
    {
      "type": "dimse",
      "source": "calling-aet",
      "destination": "called-aet"
    }
  ]
}

Example: an incoming DICOM study via DIMSE:

{
  "trigger": {
    "type": "dimse",
    "source": "calling-aet",
    "destination": "called-aet"
  }
}

Example: an incoming DICOM study via DICOMWeb STOW:

{
  "trigger": {
    "type": "dimse",
    "source": "source ip",
    "destination": "named-endpoint"
  }
}

Example: an incoming HL7 message that triggers retrieval of data from FHIR server and PACS:

{
  "trigger": {
    "type": "hl7",
    "source": "server-xyz",
    "destination": "1.2.3.4"
  },
  "data_origins": [
    {
      "type": "fhir",
      "source": "server-xyz",
      "destination": "1.2.3.4"
    },
    {
      "type": "dicom",
      "source": "calling-aet",
      "destination": "called-aet"
    }
  ]
}
@JoeBatt1989
Copy link
Contributor

@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?

@mocsharp
Copy link
Collaborator Author

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants