Support for ingest of imaging data - DICOM

[jjgriff93]

As well as typical relational data, following the implementation of #160 we can ingest any type of file. We should implement a Data Pot template that can ingest DICOM images and store / process them through stages of the datalake.

[stefpiatek]

Suggested requirements for allowing ingress of medical imaging data

• Role based access control - users should only be able to access studies and images that they have been given access to
• Encrypted transfer of pseudonymised imaging data (DICOM or a compatible API which can transfer linked images and metadata)
• Reduce load on hospital imaging systems (Picture Archiving and Communication System [PACS] and Vendor-Neutral Archive [VNA]) by extracting studies and images once and storing in a central location
• Users should be able to access the image server in the TRE while data is being uploaded (AFAIK, azure dicom server does not allow public and private endpoints both being enabled, so the TRE lost access to server while data was being uploaded)
• Imaging module should be an optional part of flowEHR
• Solution should define which DICOM SOP Classes will initially be supported (and consider whether a full DICOM conformance statement is required)

[stefpiatek]

• improvements on PACS and VNA so this hopefully would have caught up, so could pull more data
• would need to be driven by a project
• @RichardClarke-dm to go through (existing?) list, or create one and then review the priority for this.