Worklists: Engineering notes describing worklists, how they fit within review and workflow, and examples

Engineering notes describing worklists, how they fit within the review and workflow process as images arrive, and examples showing how the tools can be programmatically accessed (to be added to Sonador examples repository technical reference).

Worklists

Purpose

To facilitate processes prior to / post reviewing medical imaging worklist feature should be added to the system. Worklists should cover missing labeling functionality in the workflow for imaging technicians, add data communication visibility.

Example

Company receives imaging data, stores it in the medical DB, assigns it for review to imaging technician. Imaging tech reviews the data, assess data quality, and labels it for the further processing.

Requirements

Worklist

A worklist with the assigned to the users’ group Studies shell be developed. There is at least 1 worklist per group available for S+N to populate. Worklist consists of worklist items.

Worklist Item

Worklist item is a record in the Sonador’s DB, and it consists of

  1.      ts,
  2.      group ID
  3.      study ID
  4.      status
  5.      user ID

Open question: is it possible to include user ID in worklist item to filter out Studies each user needs to review on the worklist page?

Worklist item contains only one Study from the medical DB. It should have ability to open Study in the viewer from the worklist. Each worklist item is determined on the S+N side and created by API call to Sonador. The Study, that should be looked at, identified, and paired with the user via a group that user is in.

Worklist item has a status and shows a comment section. To show the summary of the work done on the Study status and comments are added by the user.  A status values for the Study are

  1.      Default is ‘unread’,
  2.      ‘reviewed’,
  3.      ‘rejected’,
  4.      ‘accepted’,
  5.      Additional options: ‘partially accepted’, ‘incomplete’.

Statuses are stored in the Sonador’s DB.

For worklist item creation worklist API endpoint should be added. Another API endpoint or method for the previous endpoint should be added for querying existing worklist items.

Worklist items should be accessible from the worklist. Each worklist item shell show Study preview, patient data, Study status, Study comments. Clicking on Series should open Series preview with the Series data, comments, labels if any. Would be great to be able to open imaging Series from the preview in the viewer for review.

Study Comments

A Study should have a comment section where comments with findings are posted. Study comment is a plain text that should be indexed. Study comments shell be stored in the Study in Orthanc DB and available upon request. Comments should be available via Orthanc API.

Series Labels

The user sell be able to label/tag any Imaging Series in the Study. Labels/tags should be defined on the global level. Labels API is needed to configure or extend the set of labels/tags. Data [labels, tags] shell be propagated into Orthanc API, Orthanc shell parses the data to finds the labels/tags.

Series Comments

A Series should have a comment section where comments are posted. Comment is a plain text that should be indexed. Comments shell be stored in the Series in Orthanc DB and available via Orthanc API.

Kafka Messages

To track and propagate needed information for the further processes kafka shell be used.

Open question: how Series comments and labels/tags work? Is it possible to add them separately? If not, meta field for label/tag should be added to Series comments.

When the Imaging Series is labeled/tagged a message should be sent to kafka at the same time. When the Series comment is created kafka message shell be sent at the same time. The message should include Study ID, Series ID, label/tag if available, comment if available.

Similarly, a Study status shell be sent to kafka. For the Study a kafka message should include Study ID, status, all Series with Series ID, label/tag, [comment if available].

Sorting and Filtering

Open question: should Studies be removed from the worklist?

If not, then pagination, sorting, filtering, and search should be available.

Sorting of the list shell be available for columns: asc./desc. Filtering data by patient ID, DoB, accession number, potentially other DICOM tags shell be available. Filtering by assigned user shell be available. Search for patient information shell be added.

Project Tracking

OP#45 OP#83 OP#65 OP#47 OP#48 OP#145

Edited by Sonador Claude