Hip Pre-Op Worklists
-
Orthanc backend API that allows for building and consuming a worklist -
Database Models -
Group -> Work List Table Model: -
List of WorkListItems that Group has access (group: [WorkListItem, WorkListItem...]
-
-
WorkListItem Table Model: -
Resource needs to have: UID, CTIME, MTIME, Status (Rejected, Reviewed, Approved, Unread), Resource reference
-
-
-
API View -
ManagementView, GET, POST -
RestView, PUT, DELETE (can handle multiple items, ask Steve)
-
-
Implement interface for streamlining viewing, annotation, and approval of studies (worklists) -
Export worklist creation and completion status to Kafka -
Create an integration that will generate key object selection documents based on the status and comments of a worklist item -
Create an integration which reads case assignment status from VCM and updates the worklist API with any status changes
Questions for @stevenm
- How to handle multiple resource status' changing; frontend or api for it?
- Can you provide more detail?
- The task requests for a user to select multiple work list items and modify their status. Should the frontend handle making multiple request for each work list? Or should the API handle a single request that carries all of the work lists to be modifed.
- Can you provide more detail?
- How are resources added to a work list? Does the frontend give the resource id to the api? What info will we get from frontend?
- As it was explained to me there were back end processes that would add resources to the worklist. We'll need to talk to @roakes for more detail.