Skip to content

Workflow Request Message change request #127

@mocsharp

Description

@mocsharp

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"
    }
  ]
}

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions