How We Brought E2E Encryption and Telemedicine Together in MedConnect
In MedConnect, we implemented end-to-end encryption for the doctor-patient chat: the server only sees encrypted blobs. For EGISZ and electronic prescriptions, we set up a separate signed channel.
In MedConnect, we implemented end-to-end encryption for the doctor-patient chat. This was not done just for show: medical confidentiality requires that even the server sees not the conversation itself, but only encrypted blobs. In other words: the data is there, but it can’t be read. Zero trust is no longer hype, but the baseline.
But then the real quest began. Integration with EGISZ and electronic prescriptions required a separate channel where the doctor signs the data using UKEP. And here it was important not to break legal validity: encryption protects the conversation, while the signature provides document verification.
In the end, we separated these flows: the private E2E chat lives its own life, while legally significant data goes through a separate signed channel. Like coffee and prod — better not mix them 😅