Security & compliance
How meda handles patient data.
For practice owners, data protection officers and IT service providers: the path the data takes, who can see it, and what you get in writing.
What is said in the consultation room belongs to your patients.
Compliance
Classified. Contracted. On the record.
meda processes patient data on your practice’s behalf. The AVV is signed before any data flows.
Not a medical device. meda makes no diagnosis and gives no treatment advice. The classification is available on request.
Not a high-risk AI system. meda suggests, the doctor always decides. AI literacy material for your team on request.
The data path
One consultation, step by step.
- 01Audio
Held only until the transcript exists, then deleted.
- 02Note
meda writes the note from the transcript. You correct it by keyboard or by voice.
- 03Billing codes
meda suggests the billing codes (Ziffern), each with the line of the note that supports it.
- 04Your approval
Nothing enters your PVS unless you approve it. Every approved code keeps its link to the note.
Protection
How the data is protected.
Medical notes with AES-256, every transfer over TLS.
Your practice’s data is never used to train AI models.
Named personal accounts, role-based. Each practice’s data is kept separate.
When the contract ends, as you choose. A data breach is reported to you without delay.
Documents
For your data protection officer.
- Data Processing Agreement (AVV)Read
- Technical and organisational measuresRead
- AI TermsRead
- Privacy policyRead
- List of sub-processorsOn request
- Template for your data protection impact assessmentOn request
- AI literacy material for your teamOn request
Requests: support@mymeda.ai
Security questions? Ask them directly.
We answer data protection and compliance questions before anything else. AVV and technical documentation on request.
