How We Built End-to-End Encryption in a Telemedicine Messenger
At MedConnect, we implemented end-to-end encryption for doctor-patient chats: the server never sees message text, and for EGISZ and electronic prescriptions we moved legal verification into a separate channel.
In MedConnect, we implemented end-to-end encryption for doctor-patient chats. The idea is simple, but critical: the server never sees the message text at all — only encrypted blobs. In healthcare, this is not a “future feature”; it is the baseline. Medical confidentiality should not end up moving through the backend like a meme in a work chat.
The most interesting part started with the integration with EGISZ and electronic prescriptions. That requires legal verification, so we moved it into a separate channel with the doctor’s qualified electronic signature (UKEP), where the signature works correctly and encryption does not interfere with it.
The result: message privacy is preserved, and regulatory requirements do not break the UX. In an era when privacy is back at the top of the IT agenda, this kind of balance is no longer a nice-to-have; it is a must-have.