152-FZ in Telemedicine, Without the Pain: The MedConnect Case
At MedConnect, we brought medical data processing in line with 152-FZ: set up E2E-encrypted messaging, electronic prescriptions with a qualified electronic signature (QES), integration with the Unified State Health Information System (EGISZ), and data classification by confidentiality level.
At MedConnect, we took privacy all the way: we brought medical data processing into compliance with 152-FZ — and this was not just about checking a box in a checklist. When an app has doctor-patient messaging, electronic prescriptions, and treatment progress tracking, the cost of a mistake is too high.
What we did:
- E2E encryption for messaging — so data doesn’t end up where it shouldn’t
- electronic prescriptions with a qualified electronic signature (QES) — legally binding, with no gray areas
- integration with EGISZ — fully aligned with healthcare infrastructure requirements
- classification of each data element by confidentiality level, with the appropriate protection
The most interesting part was detailed treatment tracking: useful for doctors, but from a privacy standpoint it’s firmly in the “handle with care” category. So instead of protecting the “table as a whole,” we protected each data type separately.
Bottom line: compliance is no longer bureaucracy — it’s a standard must-have for healthtech.