In order for your DiGA data to end up in the electronic patient file (ePA), you need access to the telematics infrastructure (TI) – and that’s exactly what we provide you with the right solution for. We provide you with all the technical components you need for a compliant connection. This includes certified connectors, preconfigured software and a ready-to-use TI interface via our MedicalOne Connect platform. Integration into your existing architecture is straightforward and suitable for both new and existing applications.

The connection to the ePA is standardized and traceable with us – so that you are not only on the safe side technically, but also from a regulatory perspective. We provide you with a complete, documented interface to the ePA with which your DiGA can communicate securely and in a structured manner. You then use the official FDV app to test write access from the perspective of the insured person and receive proof for your BfArM procedure.

We pay particular attention to the KVNR (health insurance number). We ensure that a valid KVNR is checked every time you log in – flexibly and in compliance with data protection regulations. Authentication takes place entirely via our TI interface, without you having to permanently store sensitive data yourself.

We know how important data protection is when integrating ePA with DiGA—especially for a sensitive application like the electronic health record. That is why our service does not permanently store any personal data. IP addresses in log files are truncated or pseudonymized, and all data processing is carried out in accordance with CNST and DMN guidelines.

You don’t have to set up your own data protection infrastructure – our solution takes care of it. So you remain compliant without any additional effort. And if you have any queries during audits or inspections, we can provide you with the appropriate documentation on request.