I need to set up a secure forum for doctors to discuss various apsects of neurosurgery. This is a specialty with many rare types of tumour and a platform to share learning and ask advice would be very helpful. This is mainly community support for surgeons in different stages of training.
There is good advice from the UK General Medical Council (https://www.gmc-uk.org/ethical-guidance/ethical-guidance-for-doctors/doctors-use-of-social-media/doctors-use-of-social-media)<p>The main minimum requirements are<p>Moderated - no patient id's<p>Secure 2FA<p>Heavy image upload (mainly screenshots of radiology Images - MR scans) Annotation would be good but a big ask<p>Inexpensive<p>Archiveable<p>Legal disclaimer etc<p>There is already a decent forum at doctors.net.uk but we could not use this as it does not allow image upload and we could not easily set up subforums.<p>The image load could become expensive and cost is a concern.
Thanks for any tips.
Discourse software may work for you in your area of concern and customers. [A] Integrating on the fly annotations to image store for large important data set isn't a new problem that hasn't already been solved. Networking and storage is cheap. Look for expert cloud infrastructure provider specialising in the medical field? Expect a little bit of premium on pricing above services from namecheap.com? [B]<p>A. <a href="https://en.wikipedia.org/wiki/Discourse_(software)" rel="nofollow">https://en.wikipedia.org/wiki/Discourse_(software)</a>
B. <a href="https://namecheap.com" rel="nofollow">https://namecheap.com</a>
What is your budget?<p>Overall, per user, per patient.<p>What regulatory jurisdiction are you under? US, EU, UK, etc., all have sharply differing concerns.<p>You'll need a legal advisor to determine what information can and cannot be exchanged. Note that "no patient IDs" doesn't mean that cases aren't identifiable. Diagnosis and timing information are themselves sufficient in many instances, any additional information (the classic ASL --- age, sex, and location --- would also strongly reduce search space). You're working against 33 bits:<p><a href="https://33bits.wordpress.com/about/" rel="nofollow">https://33bits.wordpress.com/about/</a>