Add details on "lab booking calendar"

[yarikoptic]

is it the endpoints configured in https://github.com/Donders-Institute/dicom-dataflow/blob/master/docker/cal2wl/config/config.yml

NB Extract from an email correspondence

[marcelzwiers]

This is something that @hurngchunlee may answer best, but in general, I can say that we have developed an in-house portal in which scanner slots can be booked (calendar booking system). The project number, subject number and session number are taken from the portal project database and injected in the the DICOM worklist. You would probably need to implement a translation yourself from your in-house booking system to a worklist (which is then easily taken up by the worklist broker and pushed to any DICOM modality)

[hurngchunlee]

@yarikoptic the file you found out is a configuration template used by a program called cal2wl. The source code of the program is in another repository.

In essence, the program is a tool that, on one hand, queries our lab-booking system (part of the project database, or pdb in short); while, on the other hand, transforms the query results into DICOM worklist. As @marcelzwiers mentioned, you will need to build this tool to adapt the data structure/interface of your local lab-booking system.

This Go source code of cal2wl might be interesting/helpful as it contains the logic how we create the DICOM worklist.

Let me know if you need more information.