Hi, I am Gerard Verheij, Together with my wife (gynaecologist) we are the directors/owners of a prive clinic “Karmenta” for gynaecology and urology in Schijndel and Heesch, the Netherlands. 4 gynaecologists and 2 urologists work for Karmenta.

Also I have a background in ICT, worked for Lotus, IBM as infrastructure-specialist and ICT-project manager. I like open source a lot. I have a lot of knowledge of Joomla!CMS (webdesign). As a businessman I do not like vendor lock-in… I have my own ICT-company www.applicura.nl for ICT-services for doctors in hospitals and clinics. I am pretty familiar with programming, but I am not experienced in C, C++ or PHP.
I do not have a lot of knowledge about hospital-orgaisations, radiology or DICOM.

I have experimented with Orthanc since 2020, first installed it on WIndows, then a Raspberry Pi, but now in Docker on a Synology NAS, with the MariaDB of Synology. I am enthusiastic about the possibilies of Orthanc, but I have still a lot to discover. We use Orthanc mostly for Ultrasound DICOM-pictures. We have HTTPS activated for Orthanc, with SSL-certificate and reverse proxy and (only when your IP-address is on the allow-list) can access it from the internet. I created a conversion-spreadsheet in Excel to create worklists for the ultrasounce-modalities, now I am trying to do the same in Python. We store the link to the studies from Orthanc Explorer in our electronic patientdossier (EMR).

We have several wishes:

• Make a flexible, robust, scalable and secure Orthanc-server
• API-connections to our Medicore EMR, we are busy with that
• Better, easier organisation of our worklists
• Add hysteroscopy-, colposcopy and cystoscopie-images to Orthanc
• Communicate with other clinics to exchange DICOM-studies (MRI, CT, Röntgen etc) for example via the Dutch initiative Twiin (a national system of agreements so that various healthcare providers can safely and reliably exchange patient data across existing healthcare networks, platforms and facilities.)

I am glad to participate in the Orthanc-community. Regards, Gerard Verheij