For MVZs, practices, networks — and their billing partners
The Honorar is already in your notes.
It just never gets billed.
Meda reads the notes your doctors already write and finds the EBM, GOÄ and HzV codes that were never billed.
Patient with a chronic wound, right lower leg. Follow up today. Cleaned the wound, removed damaged tissue, applied a new dressing. Wound healing well, edges calm. Next visit in five days.
The doctor decides. Only approved codes flow into the PVS.
Your PVS knows what was documented.
The KV knows what was billed.
The Kasse knows what was paid.
Nobody knows what your practice is owed.
Meda is the layer that answers it. Read-only, evidence attached, decided by your doctors.
The problem
You already did the work. The payment never arrived.
A chronic wound, cleaned and dressed, all of it in the note. The code that pays for it, EBM 02310, never gets entered.
Your PVS holds the note and the code catalog. It never reads one against the other.
How it works
Meda reads
Every finished note in your PVS, against EBM, GOÄ and HzV. Read-only, nothing changes.
You see the evidence
Each suggested Ziffer shows the line of the note that supports it.
You decide
Bill, reject, unsure. Ten minutes at the end of the day.
AI Billing
Finds the codes your PVS misses.
Finished notes, straight from your PVS.
Unbilled EBM, GOÄ and HzV codes, with evidence.
Die Feierabend-Review. Three buttons, ten minutes a day.
Linked to its note. Ready for the Plausibilitätsprüfung.
Customer quote
First named customer story · publishes with written consent
Why Meda
Four things nobody else can say.
Ambulant by design
EBM, GOÄ and HzV are the product's DNA, not a translated layer on top of a foreign system.
The doctor decides, by law and by design
Not a stage on the way to automation. The final decision is the physician's, and we build around that.
Evidence on every code
Each suggestion carries the note line that supports it, and keeps the link after approval.
Above your PVS, not inside it
One layer across every system you run. No migration, no writing to the patient record.
Trust
Processed in the EU with Meda's own AI. No US providers.
Signed before any practice data flows.
AI Note deletes audio after transcription.
Every approved code keeps its link to the note.
Hosting, data flows and the full picture: Security
Who we serve
Common questions
How accurate are the suggestions?
We do not ask you to trust accuracy. Every suggestion shows the line from the note that supports it, and nothing is billed until the doctor approves it.
Will it work with my PVS?
Live in more than five PVS today, including tomedo, medatixx, T2med and CGM. No switch, no migration.
How do you protect patient data?
Processed in EU data centres, encrypted in transit and at rest. Audio is not stored. An AVV is part of every contract.
How long does it take to get started?
AI Note has a free trial today. For AI Billing, a 20 minute call shows the review on your PVS.
The vision
Complete, evidenced billing as the default state of German ambulant care.
One layer above every PVS. Every note read, every documented service surfaced, every code decided by the doctor.
Built in Munich, with practicing doctors advising from the first line of code.
Read the Meda KodexThe Meda Briefing
✓ You're in.
The numbers, the tools, the moves. No filler.
Want to see your own quarter, read back to you?
A 20 minute call. We show the review on tomedo or medatixx, in a normal day's workflow.
Book a callAI Billing
Finds the codes your PVS misses.
You approve every one.
Reads the finished documentation in your PVS. Surfaces the EBM, GOÄ and HzV codes that are documented but not billed.
Long consultation on a new diagnosis. Discussed findings, treatment options and next steps. Conversation lasted over ten minutes.
The doctor decides. Only approved codes flow into the PVS.
A normal day, with Meda
Ten minutes at the end of the day.
Consultation documented. Wound care performed, dressing changed.
Doctors see patients and document in the PVS. Meda reads the finished notes in the background.
Suggestions arrive as one end of day list. Clear cases sorted first, judgment cases flagged. For the MFA: the quarter-end hunt for missing Ziffern becomes a short daily list.
About ten minutes a day, by design. Where does your gap sit? Take the Gap-Check
Three buttons for every code. Approved codes flow into the PVS. Nothing bills without approval.
Audit ready
Every code carries its evidence.
Every suggestion shows the exact line of the note that supports it. Every approved code keeps that link.
The supporting ICD‑10‑GM diagnosis sits next to the billing code, so diagnosis and Ziffer stay coherent.
When the KV asks during a Plausibilitätsprüfung, the answer is one click. The code, the note, the diagnosis, the approval.
EBM — the statutory catalog. Consultations, chronic care, wound care, home visits.
GOÄ — private billing. Documented services and the correct factors.
HzV — the contract codes easiest to forget.
Security, in one glance
Hosting, data flows and the full picture: Security
Common questions
Does Meda change anything in the patient record?
No. Meda is read-only on the documentation. It never changes or adds to the Patientenakte — suggestions live in the review, and what happens after approval stays in your existing billing process.
Is this billing automation?
Meda automates the reading: finished notes cross-checked against the catalogs, evidence prepared. It never automates the decision. Every code is approved by the doctor. In ambulant billing that final step belongs to the physician by law, and Meda is built around it.
Do we have to change our PVS?
No. Meda works above your existing PVS. It is live in more than five PVS today, with more on the way.
How much time does it take?
The review is designed for about ten minutes per doctor per day, at the end of the day. The MFA can prepare the list first.
What does it cost?
AI Billing runs in practices today. We discuss pricing in a call, based on your setup.
When can we start?
The measurement runs now; results publish at the end of September. Book a call and we will show you the review on your PVS.
AI Note
Clean documentation,
in seconds.
Turns what you dictate or type into structured clinical notes. Inside your existing workflow, in proper German medical language.
S — Patient reports improving wound pain.
O — Wound granulating, edges calm.
A — Chronic ulcer, healing as expected.
P — Continue dressing change, review in five days.
Security, in one glance
Hosting, data flows and the full picture: Security
What it does
Documentation, without the evening backlog.
Dictate or type. AI Note turns it into a clean, structured record.
A short summary of the patient before they walk in.
Diagnoses suggested from the note, for you to confirm.
Built for German documentation, not translated to it.
A clear, patient friendly visit summary to take home.
Clinically accurate terms and structure across specialties.
Why it matters
Good notes are where billing starts.
Every code needs a note that supports it. AI Note writes that documentation. AI Billing reads it. Together they close the gap between the work and the Honorar.
Live today
per doctor, per month
Start with documentation today. Add billing recovery next — most practices do.
Try for freeFor MVZs · Betriebsleitung & Verwaltung
Every location.
The same standard.
Each location misses different codes, in different ways, and no report shows you where. Meda reviews every location the same way, and every approved code stays traceable to its note.
Runs where you already work — more than 5 PVS
One engine · one surface per role
Your billing team stops transcribing and starts reviewing. Same team, more locations — and the billing becomes complete.
What multi location billing actually looks like
Different teams, different habits, different gaps. The codes that slip in Nord are not the ones that slip in Süd.
The PVS reports what was billed. It cannot report what was documented and never billed. That number does not exist today.
More locations means more billing volume under review. Consistency and traceability stop being nice to have.
What Meda changes
One review. One overview. Every site.
Rolled out location by location, above the PVS each site already uses. No big bang migration, no workflow change.
Suggested, approved and open, per location and per week.
Read the notes, suggest the codes, doctors approve. Identical at every site.
Every approved code stays traceable to its note and diagnosis. Billing that withstands review.
Doctors document as before. The review takes about ten minutes a day, by design.
MVZ questions
Our locations run different PVS systems. Does that work?
That is the point of the layer above. Meda is live in more than five PVS today, with more on the way. Each location keeps its system.
How does rollout across locations work?
Location by location, above the PVS each site already uses. No big bang migration, and no location waits for another.
Do our doctors have to change how they document?
No. Meda reads the finished notes they already write. The only new thing is a short end of day review.
What does our ärztliche Leitung need to know?
Three things. Clinical judgment stays where it is: every code is decided by the treating doctor, and nothing changes in how anyone documents. The suggestions are evidence, not instructions — each one shows the note line it rests on. And the rules we build by are public: the Meda Kodex.
What happens at a §106d Plausibilitätsprüfung?
Every approved code stays linked to its note and the supporting ICD‑10‑GM diagnosis, at every location. When the KV asks, the answer is one click. Complete billing that withstands review is the whole point. More on Security.
Want every location billing complete — without new headcount?
A 20 minute call shows the overview on your locations, on the PVS you already run.
Book a callFor Hausärzte und Fachärzte in eigener Praxis
The codes that slip
through a full day.
The long conversation. The chronic care visit. The GOÄ service for a private patient. You did the work and documented it. Then the next patient was already waiting.
Three decisions. Then you go home.
Runs where you already work — more than 5 PVS
Where your Honorar slips
Fifteen minutes walking a patient through a new diagnosis, documented in full. The Gespräch code never entered.
HzV codes are the easiest to forget in a mixed day, and they add up quarter after quarter.
Did everything get billed? Today, there is no way to know. The note holds the answer, and nothing reads it.
What Meda changes
Ten minutes. Your decision. Every time.
Meda reads your finished notes and shows what is documented but not billed, with the line from the note that proves it.
One short review when the day is done. No interruptions during consultations.
Every suggestion carries the exact sentence from your note that supports it.
Bill, reject with a reason, or unsure. About ten minutes, by design.
Nothing bills without you. Your judgment stays the final step, by design.
Doctor questions
Is this upcoding?
No. Meda only suggests codes your documentation supports, and you approve every one. That is correct billing, evidenced. Every approved code stays traceable to the note, ready for the Plausibilitätsprüfung.
How much extra work is it?
The review is designed for about ten minutes a day, at the end of the day. Your MFA can prepare the list first.
Does it work with HzV contracts?
Yes. HzV codes are part of what Meda reads for, alongside EBM and GOÄ.
The Meda Briefing
✓ You're in.
The numbers, the tools, the moves. No filler.
Want your Feierabend back — with the Honorar already in it?
A 20 minute call. We show the review on your PVS. Or start smaller: take the Gap-Check.
Book a callFor Praxisnetze und Verbünde
One standard across
independent practices.
Praxisnetze, Verbünde, Genossenschaften: federations of independent practices. Their systems differ, so Meda sits above the PVS. The same billing review works everywhere, without forcing anyone to switch software.
What the network gets
A member benefit that actually lands.
Complete, evidenced billing for your members — the kind of benefit that strengthens the network itself: members earn what they documented, and the standard travels with your name.
A shared quality floor without mandating software. Each practice decides and contracts for itself. The network offers; it never administers.
What you can tell your members
Three sentences, forwardable as they are.
The network reality
Every member practice chose its own PVS. Any tool that requires switching is dead on arrival.
Billing quality depends on each practice's habits. There is no common floor, and no way to raise one.
Member practices are independent. A network can offer a standard. It cannot mandate software.
What Meda changes
A shared floor, without shared software.
The layer above the PVS is the only place a network standard can live without touching each practice's stack.
The same review works across tomedo, medatixx, T2med, CGM — and counting.
Each practice keeps its system and control of its own data.
Every code is approved by the treating doctor, in every practice.
Complete, evidenced billing that withstands review — as the network's common floor.
Network questions
Do member practices have to switch their PVS?
No. Meda works above the PVS each practice already uses. Live in more than five PVS today, more on the way.
Who controls the data?
Each practice. The network sees no practice data. Each practice sees only its own review; there is no network dashboard, by design. Every code is decided by the treating doctor in that practice.
How does a network offering work?
Network offerings are relationship led, not a form. Talk to the founders and we work out the shape together.
How do member doctors experience it?
A short end of day review with evidence attached to every suggested code. About ten minutes a day, by design.
Want a standard your members actually adopt?
Relationship led, not a form. A call with the founders, then we shape it together.
Book a callIntegrations
Above your PVS.
Not instead of it.
Your PVS stays your system of record. Meda reads finished documentation and writes back only what the doctor approved.
The PVS we run above.
One layer, every system of record. Meda reads the finished documentation in the PVS you already use — no switch, no migration, no new tool for the front desk.
Which PVS do you run?
✓ Noted. We come back to you on your PVS.
How it connects
Standard interfaces. No switch.
Meda connects through the standard interfaces your PVS already speaks, including GDT, LDT and APIs where available.
It reads finished documentation. It never changes a note. It writes back exactly one thing: the codes your doctor approved.
No migration. No new documentation tool. No change for the front desk.
Security & compliance
Built for German healthcare.
From the ground up.
Patient data, medical documentation and billing. No room for shortcuts. This page states how Meda handles it.
Data protection
Why the doctor stays in the loop
German ambulant billing makes the physician responsible for every billed code. That is why Meda is built around the doctor's decision, not around automation.
Every suggestion needs approval. Every approved code stays traceable to the note and the supporting ICD‑10‑GM diagnosis.
When the KV reviews your billing in a Plausibilitätsprüfung under §106d SGB V, the evidence is already attached.
Sovereignty, precisely
German health data stays in Europe.
Practice and documentation data is processed in the EU, on EU infrastructure, with Meda's own AI. No US AI providers touch it.
Meda reads the documentation — read-only, never changing the Patientenakte — and every code is a physician's decision. Sovereignty here isn't a server location. It's the architecture.
An AVV (Auftragsverarbeitungsvertrag) is in place before any practice data flows.
Two kinds of data, told apart
Documentation and billing context. EU-only, Meda's own AI, read-only on the record, AVV-covered.
Forms and CRM run on HubSpot with EU data residency, under the cookie consent you control. Never mixed with product data.
The honest split most vendors blur. We name it.
Security questions? Ask them directly.
We answer data protection and compliance questions before anything else. AVV and technical documentation on request.
About Meda
Doctors should be paid for the work they already do.
Not more medicine. Not different medicine. The same work, finally billed completely and correctly.
Why we built Meda
The gap between the note and the bill.
German ambulant care documents almost everything and still loses Honorar every quarter, because notes and billing live in the same system without ever meeting.
We build the layer that reads one against the other. Above the PVS, with the doctor in charge of every decision.
Meda is built in Munich by a team across product, engineering and healthcare, with practicing doctors advising from day one.
We publish methods and measured results. Claims we cannot back stay off this website.
Doctor in the loop is not a feature stage. It is how ambulant billing must work, and how Meda is built.
EBM, GOÄ, HzV, PVS. We build for this system, in this language, for this market.
Why we're building this
A letter from the founders
We built Meda after watching, up close, how much documented work in German practices never turns into Honorar — and how little the systems holding that work seemed to care.
What we knew from day one: doctors don't need another tool that promises more revenue. They need to be paid completely and correctly for the work they already do — with their own judgment as the final step. That is what we build, in Munich, with practicing doctors advising from the first line of code.
Supported by the EXIST Gründungsstipendium and the AI+Munich initiative. Built with practicing doctors and academic advisors from Munich's medical and AI faculties. A German company, engineered and hosted in Europe.
— Andrei (CEO), Aqid (CTO) & Penny (CPO) · Munich
Read the Kodex we build by
Book a call
See Meda on your PVS.
A 20 minute call. We show the code review on tomedo or medatixx and answer your questions. No slides marathon.
In a hurry? Book a slot directly
Request received.
We get back to you within one working day to find a time.
Pricing
You pay per doctor.
Your team logs in free.
Two features, both counted per Arzt and month. Your MFAs, your billing team and your Praxismanagement use Meda every day too, and cost nothing.
(AI Note + AI Billing)
× your doctors
Everyone else in your practice: 0 €. However many. Each with their own named login.
AI Note is 69 € per Arzt and month. AI Billing comes on top when you want it, and we price that one after we have measured in your practice.
The reason Meda exists
AI Note + AI Billing
For practices that want the documented Ziffern back.
Choose this if you
- suspect Ziffern are slipping and cannot prove it
- run more than one doctor, or more than one Standort
- want every code to hold up at a Plausibilitätsprüfung
- Finished notes read against EBM, GOÄ and HzV
- Evidence attached to every suggestion
- Die Feierabend-Review: bill, reject, unsure
- MFA prepares, the doctor decides
- AI Note included, for every doctor
Live today
AI Note
For practices that want clean notes and nothing else.
No credit card.
Choose this if you
- want the documentation, and no billing help
- would rather start this week than have a conversation
- are curious about the billing side, later
- Structured notes from dictation or typing
- Visit preparation summaries
- ICD‑10‑GM diagnoses suggested, you confirm
- German medical language, built in
- Billing-code suggestions as a preview
All prices net, zzgl. USt. AI Billing is taken for the whole practice, not per single doctor. Practices that only need the documentation are welcome to stay there, and many do.
Roles
Everyone in the practice gets a login. You pay for the doctors.
Documents as always, sees the suggestions, decides every Ziffer. Nothing is billed without that decision.
Per Arzt and month. A doctor who also runs the practice holds both roles on one login, and is counted once.
However many you need. Each with their own named login.
What is included
| AI Note | + AI Billing | Chain & Org | |
|---|---|---|---|
| AI Note | |||
| Ambient documentation of visits | ✓ | ✓ | ✓ |
| Structured notes, dictation or typing | ✓ | ✓ | ✓ |
| ICD‑10‑GM suggested, you confirm | ✓ | ✓ | ✓ |
| Billing-code suggestions | preview | ✓ | ✓ |
| AI Billing | |||
| Finished notes read against EBM, GOÄ and HzV | — | ✓ | ✓ |
| Evidence attached to every suggestion | — | ✓ | ✓ |
| Three button review: bill, reject, unsure | — | ✓ | ✓ |
| Export into your billing process | — | ✓ | ✓ |
| Team & accounts | |||
| Biller, MFA and Manager accounts | 0 € | 0 € | 0 € |
| Named individual logins | ✓ | ✓ | ✓ |
| Unlimited team accounts | ✓ | ✓ | ✓ |
| Chain layer | |||
| Completeness per Standort | — | — | ✓ |
| Organisation wide roles | — | — | ✓ |
| Platform fee per practice | — | — | 99 € / month |
| Contract | |||
| AVV in place before any data flows | ✓ | ✓ | ✓ |
| Term | monthly / annual | monthly / annual | annual |
| Setup | included | included | scoped per deal |
Why it is priced this way
How do you count doctors?
Every doctor whose visits run through Meda in that period. Deactivate a doctor and they stop counting from then on. Anyone practising as a doctor counts, Weiterbildungsassistenten included.
Why per doctor?
Because a doctor is who Meda works for. It reads what a doctor wrote, and every Ziffer is a doctor's decision. Your MFA and your billing team work in Meda every day too. Charging for their logins would put a price on the paperwork instead of the work.
What do Biller, MFA and Manager accounts cost?
Nothing, however many you have. Each person gets their own login rather than sharing one, so it stays clear who did what. That matters at a Prüfung, and it is not something we charge for.
When do you need the multi-site setup?
When you need the layer above the practices: several locations, billing run centrally, and deadlines across more than one KV. It is not about how many doctors you have. Six doctors at one Standort is a practice, and the practice setup fits it.
We work with an external Abrechnungsdienstleister. Can they log in?
Biller accounts are for people employed by the practice or the chain. For external services, Meda hands over finished material in the formats they already take.
Why is there no price on AI Billing?
Because we refuse to guess. It runs in practices today and its price follows the measurement rather than a guess about it. In a call we walk through your setup and what the pricing will look like for it.
See it before you decide.
A 20 minute call on your PVS. No obligation, no slides marathon.
Talk to usInsights
Billing knowledge,
written to be useful.
EBM, GOÄ, HzV, the PVS landscape and the rules around them. No fluff, evidence marked, reviewed by practicing doctors.
How we measure: the method behind our numbers
We publish the method before the numbers — so you can check how they're made. Rejections count against us, publicly.
MarketThe Ziffern practices forget most — and why the pattern repeats
Not a knowledge problem. A timing problem — and the same families slip everywhere.
MarketGOÄ factors: what your documentation has to support
The factor is a claim about the service. Under-factored loses money; over-factored fails review. The note decides.
MarketWhy German health data needs German AI
The shortest processing chain is the safest — and it stays in Europe. Three questions to ask any vendor.
MarketHonorarausschöpfung: billing everything you already documented
What full Honorar capture means, why practices fall short, and what legitimately closes the gap.
GOÄneu: the 24 month window
The PVS systems get rewritten. What the reform projects for GP and psychiatric practices, and what to do about it.
Labs solved this in 2018. Billing didn't.
LDT 3.0 made lab results flow automatically. Why billing capture stayed manual, and what that gap costs.
Why the doctor approves every code
The regulatory architecture of German ambulant billing, and why doctor in the loop is a design requirement, not a feature stage.
How Meda connects: above tomedo and medatixx
GDT, LDT and APIs. What the layer above the PVS reads, what it writes back, and what never leaves.
Ziffern-Finder: every EBM, GOÄ and HzV code, in plain German
Search the way you think — "Wundversorgung", not chapter numbers.
Tool · freeDer Gap-Check: see your own billing gap in 30 minutes
Six questions, a personal audit plan, a printable checklist. No invented numbers — you count your own.
Why three buttons
Designing a billing review a doctor actually finishes: bill, reject, unsure, in about ten minutes a day.
Customer stories publish with the measurement — with consent, never invented.
Market · 7 min read · publishes in German
Honorarausschöpfung: billing everything you already documented
Honorarausschöpfung means one thing: billing completely for the services your practice has already performed and documented. Not billing more. Not billing differently. Closing the gap between what the note proves and what the Abrechnung contains.
In most practices that gap exists quietly. The service is in the documentation, the matching EBM, GOÄ or HzV code never gets entered, and nothing flags it. This page explains where the gap comes from, where it typically sits, and what actually closes it.
Why documented services go unbilled
The daily reality first: the long conversation about a new diagnosis, the chronic care visit, the wound care. Done, documented, and then the next patient was already waiting. The code entry is the step that loses.
Then the system reality: your PVS holds both the note and the code catalog, and never reads one against the other. Documentation tools write notes. Billing modules check what was typed into the billing mask. The space between is invisible to both.
Where the gaps typically sit
In EBM, it is the problem oriented conversations, chronic care codes and wound treatment. In HzV, the contract codes that are easiest to forget in a mixed day. In GOÄ, documented services and the correct factors for private patients. These are qualitative patterns; our measured numbers publish at the end of September.
Honorarausschöpfung messen: how to see your own gap
The honest method: for one quarter, read the notes against the billed codes and count the divergence. Manual, tedious, revealing. It is exactly what we measure right now, in practices on tomedo and medatixx, with every decision logged.
Three ways practices close the gap
Self audits work but rarely survive a busy quarter. Billing training helps, decays, and does not scale across locations. And there is a newer, third way: ambient billing intelligence above the PVS. Software that reads the finished notes and suggests the documented but unbilled codes, for the doctor to approve.
How Meda does it
Meda reads the finished documentation in your PVS and surfaces the codes it supports, each with the exact line of the note as evidence. The review takes about ten minutes at the end of the day: bill, reject with a reason, or unsure. Nothing is billed without the doctor.
What this means for the Plausibilitätsprüfung
Complete billing has to withstand the KV's review. That is why every approved code keeps its link to the note and the supporting ICD‑10‑GM diagnosis. Correct billing, evidenced — not gaming it.
Questions doctors actually ask
What does Honorarausschöpfung mean?
Billing completely for documented, performed services. Nothing more, nothing different.
Isn't this upcoding?
No. Only codes the documentation supports, and the physician approves every one. That is correct billing, and it is built that way deliberately.
How much Honorar do practices typically lose?
We publish measured answers, not estimates — from measurement in real practices. Until then we don't quote a number.
Does it work with my PVS?
Meda is live in five PVS today, including tomedo and medatixx.
Do I have to change how I document?
No. Meda reads the notes you already write.
Der Meda Kodex
The rules we build by.
Published, so you can hold us to them.
Billing AI in German healthcare needs rules, not promises. These are ours. They don't change with the roadmap.
Nothing is ever billed without a physician's explicit decision. Not as a feature stage. As the design.
The industry races toward touchless coding. We build the opposite: machine reading, evidence attached, human decision. We will not "evolve toward autonomy."
Each code shows the line of the note that supports it, and keeps that link after approval. Ready for the Plausibilitätsprüfung, by construction.
No performance numbers appear in our marketing before they appear in a published measurement. Our measured results publish, method first, end of September.
EBM, GOÄ, HzV, the PVS landscape, correct billing under German law. Built for this system, in this language, hosted in Europe. Not adapted to it.
— Andrei, Aqid & Penny · Munich. If we ever break one of these, tell us — publicly.
Der Gap-Check · free
We don't estimate your gap.
We hand you the measuring tape.
Six questions about your quarter. You get a personal audit plan: which code families to count first, and how to see your own gap in about 30 minutes. No invented numbers — the only number that counts is yours.
AI Billing · EBM
Every EBM Ziffer
your notes support.
The Versichertenpauschale bills itself. The Einzelleistungen are where the quarter leaks: the conversations, the wound care, the Chroniker codes. Documented, performed, never entered.
Where EBM slips
The patterns we see, before the numbers.
Problem oriented conversations (03230) done in full and never coded. Wound treatment (02310) documented by the MFA, missing on the Schein. Chronikerzuschläge (03220/03221) forgotten in a mixed day. Vorsorge like the Check-up (01732) performed, unbilled.
These are the qualitative patterns from practice. Our measured numbers publish with the September write up.
Meda reads the finished note, finds the documented service, and shows you the Ziffer with its evidence. You decide.
EBM questions
Which EBM codes does Meda look for?
Documented but unbilled services, with the common hausärztliche patterns first: Gespräche, Wundversorgung, Chroniker, Vorsorge. Every suggestion carries the line of the note that supports it.
What happens at the Plausibilitätsprüfung?
Every approved code stays linked to its note and the supporting ICD‑10‑GM diagnosis. When the KV asks, the answer is one click. Complete billing that withstands review is the whole point.
Is this upcoding?
No. Only codes your documentation supports, and the doctor approves every one. Correct billing, evidenced.
AI Billing · GOÄ
GOÄ: documented services,
correct factors.
Private billing lives on two things: the services you performed and the factors your documentation justifies. Both come from the note. Meda reads it.
Where GOÄ slips
The service happened. The Ziffer didn't.
The Beratung that ran long. The symptombezogene Untersuchung done alongside. Services performed for private patients, fully documented, missing from the Rechnung — or billed below the factor the documentation supports.
Meda surfaces the documented services and factors, each with its evidence from the note. If your GOÄ billing runs through a Verrechnungsstelle, Meda works upstream: more complete input, same trusted process.
Why now
GOÄneu opens a 24 month window.
For GP and psychiatric practices the reform projects around 20 percent more Honorar. Capturing it depends on capturing the codes.
We decode the transition as it happens — our read, the numbers, the tools.
✓ You're in.
GOÄ questions
Does Meda suggest higher factors?
Meda surfaces the services and factors your documentation supports, with the evidence attached. Nothing beyond what the note justifies, and the doctor decides every position.
We bill GOÄ through a Verrechnungsstelle. Does that change anything?
No. Meda sits upstream of the billing office: the doctor approves the documented services, and more complete input flows into the process you already run.
Are you ready for GOÄneu?
The reform rewrites the catalog and the PVS systems with it. Meda is built above the PVS, which is exactly where that transition is easiest to survive. We publish a GOÄneu Rechner in August.
AI Billing · HzV
HzV: the contract codes
easiest to forget.
Hausarztzentrierte Versorgung pays through contract codes that sit outside the EBM routine. In a mixed day of GKV, HzV and private patients, they are the first thing that slips.
Three catalogs, one review.
Why HzV slips
A second billing logic, in the same day.
HzV contracts differ by region and Krankenkasse, each with its own Pauschalen and Zuschläge. The doctor's day doesn't sort patients by contract — the billing has to, and in a full Sprechstunde the contract codes are the ones that get lost.
Meda reads the finished notes and surfaces the documented HzV codes relevant to your contracts, alongside EBM and GOÄ, in the same Feierabend-Review. One list, three catalogs, your decision.
HzV questions
Which HzV contracts are covered?
Contracts differ by KV region and Krankenkasse. In the call we go through the contracts your practice participates in and what Meda reads for in each.
Do HzV and EBM suggestions get mixed up?
No. Each suggestion is tied to the patient's context and shows its catalog. The doctor sees one clean end of day list.
We're an MVZ with mixed enrollment. Does that work?
Yes. The review handles mixed days by design — that's exactly the situation where contract codes slip most.
Ziffern-Finder · free
Every Ziffer, explained
in plain German.
EBM, GOÄ and HzV codes with what they actually mean, when they apply, and what they're also called. Search the way you think, not the way the catalog is written.
03230
Problemorientiertes ärztliches Gespräch, mind. 10 Minuten
Auch gesucht als:
02310
Behandlung chronischer Wunden, Behandlungskomplex
Auch gesucht als:
03220 / 03221
Chronikerzuschlag zur Versichertenpauschale
Auch gesucht als:
03000
Versichertenpauschale, hausärztliche Versorgung
Auch gesucht als:
01732
Gesundheitsuntersuchung (Check-up)
Auch gesucht als:
35100
Differentialdiagnostische Klärung psychosomatischer Krankheitszustände
Auch gesucht als:
Ziffer 1
Beratung, auch telefonisch
Auch gesucht als:
Ziffer 3
Eingehende Beratung, mind. 10 Minuten
Auch gesucht als:
Ziffer 7
Vollständige körperliche Untersuchung eines Organsystems
Auch gesucht als:
Ziffer 5
Symptombezogene Untersuchung
Auch gesucht als:
Chroniker-Pauschale
Vertragsabhängige Pauschale für chronisch Kranke (Beispiel P3)
Auch gesucht als:
The most-searched Ziffern, in plain German. The complete catalogs are next.
Documented, but never billed?
Finding these codes in your own notes is literally what Meda does. Every day, with your approval.
See AI BillingMarket · 5 min read · publishes in German
The Ziffern practices forget most — and why the pattern repeats
The forgotten Ziffer is almost never a knowledge problem. It's a timing problem: the service ends, the next patient is waiting, and the code entry is the step that loses.
Across practices, the same families slip again and again. Not the exotic positions — the everyday ones.
The conversation that ran long
The problem oriented conversation (EBM 03230) is documented constantly and billed inconsistently — because it happens inside a full Sprechstunde, and ten honest minutes of talking feel like care, not like a billable position. The note proves it. The Schein often doesn't show it.
The wound the MFA documented
Wound care (EBM 02310) is a team pattern: the MFA documents the treatment precisely, and the code depends on someone reading that documentation against the catalog at the end of a long day.
The chronic patients everyone knows
Chroniker codes (03220/03221) fail in mixed days — the patient is so familiar that the routine hides the position. The same mechanism catches HzV contract codes: a second billing logic in the same Sprechstunde.
The Vorsorge that happened anyway
Check-ups (01732) and psychosomatic basic care (35100) are performed, documented — and forgotten precisely because they feel like part of the visit rather than services of their own.
What actually fixes the pattern
Not more training — the knowledge is there. The fix is reading: every finished note, against every catalog, every day, with the doctor deciding. That is what Meda does, with the evidence attached to every suggestion.
Customers · 6 min read
How we measure: the method behind our numbers
Every billing tool claims results. We publish our method before our numbers — so when the numbers come, you can check how they were made.
The design
Multi-practice measurement on tomedo and medatixx, in real daily operation. For every patient contact, Meda reads the finished documentation and suggests the documented but unbilled codes. Every suggestion, every doctor decision — bill, reject, unsure — and every reason is logged.
What we count, and what we refuse to count
We count only physician approved codes: services the documentation supports and a doctor confirmed. Rejected suggestions count against us, publicly. We do not count projections, do not extrapolate from best cases, and do not quote a number before the measurement closes.
Why the doctor's rejection matters most
A suggestion a doctor rejects is the most important data point we collect. It trains the reading, and it is the difference between recovery and upcoding: the measured result is, by construction, only what physicians decided was correct.
What publishes
The method, the practice profiles, the acceptance rates, and the recovered positions — with the KV review register in mind: everything traceable to documentation. When it publishes, it publishes whole. Until then, this page is the promise you can hold us to.
Market · 5 min read · publishes in German
GOÄ factors: what your documentation has to support
In private billing, the factor is not a preference — it's a claim about the service. The documentation either supports it, or it doesn't.
The mechanics, briefly
GOÄ services carry a Steigerungsfaktor. Up to the Regelhöchstsatz (2.3 for most personal services), the factor reflects difficulty and time within the normal range. Above it, a written Begründung is required — and the documentation has to carry that justification.
Where practices lose, both directions
Under-factoring: complex, time intensive services billed at routine factors because nobody connected the note to the number. And risk the other way: factors the documentation does not support, which fail exactly when scrutiny arrives. The safe position is the same in both cases — the factor the note proves.
The Verrechnungsstelle question
If a billing office runs your GOÄ, the quality of what reaches them decides everything. Meda works upstream: documented services and supportable factors, physician approved, flowing into the process you already trust.
Market · 6 min read
Why German health data needs German AI
The most sensitive data a country produces is its citizens' health records. Where that data is processed — and under whose law — is not a technicality. It's the whole question.
The structural argument
Health data enjoys the strictest protection European law knows. Every additional jurisdiction in the processing chain adds legal surface: foreign disclosure obligations, transfer mechanisms under permanent legal challenge, sub-processors your AVV can name but your KV cannot audit. The shortest chain is the safest chain — and the shortest chain stays in Europe.
The Doctolib lesson
The European companies that won in German healthcare didn't win by waving a flag. They won by operational Germanness: German entities, European health-grade hosting, German support, fluency in the KV world. Sovereignty is performed in contracts and architecture, not proclaimed in marketing.
How Meda holds it
Practice data is processed in the EU with Meda's own AI — no US AI providers in the chain. The system is read-only on the patient record, every code is a physician's decision, and the billing logic is native: EBM, GOÄ, HzV are the product's DNA, not a localization layer. A tool built elsewhere can translate its interface. It cannot translate its jurisdiction.
What to ask any vendor
Three questions sort the field: Where exactly is the data processed, and under which law? Which sub-processors touch it — all of them? And can it act on the record, or only read it? The answers belong in writing, before any data flows.
For billing offices · Privatärztliche Verrechnungsstellen
More complete input.
Same trusted process.
You can only bill what reaches you — the gap sits upstream, in the practice's day, before your work begins. Meda reads the finished documentation there and surfaces documented services, approved by the doctor, before the billing data goes out. Your process stays exactly as it is.
The structural reality
A note on letters: on this page, PVS always means Praxisverwaltungssystem — the practice software. Billing offices we call by name.
Services get performed and documented, and in a full day some never make it into the billing data that reaches you.
The evidence lives in the clinical documentation, one layer upstream of your process. No one reads it against the billing data.
The place to close the gap is in the practice, at the end of the day, with the doctor deciding. That is where Meda sits.
What this means for you
Meda works upstream. You run the billing.
Meda does not process claims, does not invoice, and does not collect. It improves what flows into the claim, with the doctor's approval on every code.
Documented services surfaced at the source, before the data reaches you.
Every code carries the physician's decision and its evidence from the note.
Documented private services and the correct factors, evidenced in the note.
Relationship led. We work out the fit together, case by case.
Straight answers
Does Meda replace a billing office?
No. Meda does not process claims, does not invoice, and does not collect. It reads clinical documentation and surfaces documented codes for the doctor to approve. Everything downstream stays yours.
Do you pitch against us at our clients?
No. Meda sits one layer upstream. Where a practice works with a billing office, the approved codes flow into the process that practice already runs with you.
How does a partnership work?
Relationship led, not a form. Talk to the founders and we will walk through your setup and where Meda fits.
Want more complete input — without changing your process?
A direct conversation with the founders. WhatsApp or a 20 minute call.
Talk to usCareers · Munich
Build the layer
above the PVS.
We are a small team in Munich building ambient billing intelligence for German ambulant care, with practicing doctors advising from day one. We are hiring.
Legal
Impressum
Information according to § 5 DDG (German Digital Services Act)
Responsible for content
meda AI GmbH
Distlhofweg 18, 81369 Munich, Germany
- Vertreten durch die Geschäftsführer
- Andrei Mancu, Pei-Ning Hung
- Registergericht
- Amtsgericht München
- Registernummer
- HRB 305361
- Umsatzsteuer-Identifikationsnummer gemäß § 27a UStG
- DE459522226
Contact
- support@mymeda.ai
- Phone
- +49 152 02544938
Disclaimer
Liability for content
The content of our website has been created with the utmost care. However, we cannot guarantee its accuracy, completeness, or timeliness.
IMPORTANT NOTICE: meda AI is an AI-powered documentation tool for healthcare professionals. Our software does not provide medical advice, does not replace physician diagnosis or treatment, serves only as documentation support, and requires professional medical supervision.
In medical emergencies, immediately contact Emergency Services at 112 or Poison Control at 030 19240.
Last updated: 01.07.2026
Legal
Privacy Policy
01Introduction
meda AI GmbH (“meda”, “we”, “us”, or “our”) is committed to protecting your privacy and personal data. This Privacy Policy explains how we collect, use, share, and protect your information when you visit our website at www.mymeda.ai, contact us or request information about our products and services, register for or use the beta version of our physician platform, or take part in clinical research conducted with our partner medical institutions.
We treat your personal data confidentially and in accordance with statutory data protection regulations, in particular Regulation (EU) 2016/679 (General Data Protection Regulation, “GDPR”) and applicable German data protection law (the Federal Data Protection Act, BDSG, and the Digital Services Act, DDG).
We act as a data controller for the personal data we process to operate this website and to communicate with prospective and existing customers. When our platform is used by a healthcare provider, we instead act as a data processor, as explained in Section 3.
If your personal data is processed within the platform by your healthcare provider, this Privacy Policy does not govern how that provider uses your data. Your healthcare provider is the data controller for that processing, and you should refer to their own privacy notice. See Section 3 for details of our role as a data processor.
This Privacy Policy serves to inform you in accordance with Articles 13 and 14 GDPR.
02Who We Are and How to Contact Us
meda AI GmbH
Distlhofweg 18, 81369 Munich, Germany
- Role
- Data Controller
- support@mymeda.ai
- Phone
- +49 152 02544938
For any privacy-related enquiry, please contact us by email at support@mymeda.ai or by post at the address above.
03Our Role: Data Controller and Data Processor
meda as data controller. When you visit our website, submit an enquiry, request information, register for the beta programme, or otherwise interact with us as a prospective or existing customer, meda determines the purposes and means of processing your personal data and acts as the data controller in accordance with this Privacy Policy.
meda as data processor. When our platform is used by a customer organisation (such as a medical practice, clinic, or hospital), that organisation is the data controller for the personal data processed within the platform, including:
- patient data, health records, and clinical information;
- account data for healthcare professionals and practice staff; and
- other personal data entered, uploaded, or generated within the platform by the customer.
Acting as a data processor, we process such data only on the customer’s documented instructions as set out in the applicable Data Processing Agreement (DPA). We do not use it for our own purposes, we apply appropriate technical and organisational security measures, we assist the customer with data subject rights requests, we notify the customer without undue delay of any personal data breach, and we delete or return the data at the end of the service, unless retention is required by law.
If you are a patient whose data is processed within the platform provided to your healthcare provider, that provider — not meda — is the controller responsible for your data. Please direct any questions, requests, or complaints to your healthcare provider, whose privacy notice applies to that processing.
04Categories of Personal Data We Process
4.1 Website Visitor Data
- Browser information (type, version, operating system)
- Usage data (pages visited, time spent, click patterns)
- Referrer URL and search terms
- Device information (screen resolution, device type)
- Cookies and tracking technologies (see Section 12)
4.2 Professional User Registration Data
- First and last name
- Email address
- Professional information (medical practice, specialty, licence)
- Phone number (optional)
- Feedback and support requests
4.3 Beta Platform Usage Data
- Authentication data (login credentials, session tokens)
- Usage analytics (feature usage, session duration, error logs)
- Performance metrics (system response times, error rates)
- Feedback and support communications
- Technical logs (automatically anonymised after 30 days)
4.4 Special Categories of Data (Health Data)
Where our platform is used to support clinical documentation, we process special categories of data — in particular health data — solely as a data processor on behalf of our customers. Consultation audio is processed in real time and deleted immediately; it is never permanently stored.
05Legal Bases for Processing
We only process your personal data where we have a lawful basis under the GDPR. Depending on the context, we rely on:
- Art. 6(1)(a) GDPR — consent (e.g. contact forms, newsletter, non-essential cookies);
- Art. 6(1)(b) GDPR — performance of a contract (e.g. beta platform access);
- Art. 6(1)(c) GDPR — compliance with a legal obligation;
- Art. 6(1)(f) GDPR — legitimate interests (e.g. website operation, security, product development).
Where health data is processed within the platform, the relevant conditions of Art. 9(2) GDPR apply and are determined by the healthcare provider acting as controller. You may withdraw any consent at any time without affecting the lawfulness of processing carried out beforehand.
06Purposes of Data Processing
6.1 Website Operation
- Website provision and technical optimisation
- Usage statistics analysis (see Section 8)
- IT security assurance
6.2 Beta Testing and Product Development
- Function testing of AI-powered documentation software
- User feedback collection for product improvement
- Performance optimisation of our medical AI models
6.3 Communication and Support
- Processing enquiries and technical support
- Information about product updates and new features
- Clinical study coordination with partner institutions
07How We Share Your Personal Data
We do not sell, rent, or trade your personal data. We only disclose it where necessary for the purposes described in this policy and as permitted by law, with appropriate contractual safeguards in place. We may share data with:
- Service providers and sub-processors who process data on our documented instructions (see Section 8);
- Professional advisers such as lawyers, auditors, and tax advisers, where required;
- Authorities where required or permitted by law, or to establish, exercise, or defend legal claims;
- Successors in connection with a merger, acquisition, or reorganisation, subject to equivalent safeguards.
All third-party providers are bound by contract to protect your data, process it only on our instructions, and implement appropriate technical and organisational security measures.
08Sub-Processors and Third-Party Services
8.1 EU Cloud Hosting
- Server location: exclusively within the EU (France) — GDPR compliant
- Full audit logging of all access; medical notes encrypted with AES-256
8.2 AI Processing (Medical Documentation)
- Provider: meda AI GmbH — our own in-house AI models. We do not use any third-party or US-based AI providers (such as OpenAI or Google).
- Purpose: real-time speech-to-text transcription and structuring of medical documentation.
- Data location: exclusively on secure EU-based servers — no health data leaves the EU.
- Retention: audio is processed in real time and deleted immediately — no permanent storage.
8.3 Website Analytics
- Analytics: We use Plausible Analytics, a privacy-friendly tool hosted in the EU. It uses no cookies, collects no personal data, and transfers no data outside the EU.
- Booking and contact: When you book a meeting or contact us, we use HubSpot (EU "eu1" data centre) for scheduling and contact management. Where data is transferred to the US, this is based on the EU-US Data Privacy Framework and/or EU Standard Contractual Clauses. HubSpot loads only after you consent via our cookie banner.
09International Data Transfers
We process personal data exclusively within the European Union. No patient or health data leaves the EU. The only limited exception is website analytics, which may involve a transfer under the EU-US Data Privacy Framework with IP anonymisation applied. Where any transfer outside the EEA occurs, we ensure an appropriate safeguard recognised under the GDPR is in place.
10Data Retention Periods
- Audio recordings
- deleted immediately after processing — never stored
- Website logs
- 7 days
- Website analytics data
- 14 months
- Contact / registration data
- until consent is withdrawn
- Beta usage data
- end of beta phase + 3 months
- Medical documentation
- retained by the healthcare provider per medical retention requirements (typically 10 years)
- Support communication
- 3 years
11Data Security and Technical Measures
- EU-only server location (France) — GDPR compliant
- Complete audit logging of all access
- Consultation audio never stored (real-time processing only)
- Medical notes encrypted with AES-256; data encrypted in transit (TLS)
- Separate systems for different medical practices
- Regular penetration testing and security assessments
12Cookies and Tracking Technologies
12.1 Essential Cookies
- Session management: user authentication and session maintenance
- Security: CSRF protection and security headers
- Functionality: language preferences and accessibility settings
12.2 Analytics and Marketing Cookies
- Loaded only with your consent for website optimisation and marketing purposes
- Managed through our consent banner with granular options; consent can be withdrawn at any time
13Your Data Protection Rights (Articles 15–22 GDPR)
Under the GDPR you have the following rights in relation to your personal data:
- Right of access (Art. 15)
- confirmation of whether we process your data and a copy of it.
- Right to rectification (Art. 16)
- correction of inaccurate or incomplete data.
- Right to erasure (Art. 17)
- deletion of your data in the circumstances set out in the GDPR.
- Right to restriction (Art. 18)
- limitation of processing in certain cases.
- Right to data portability (Art. 20)
- receipt of your data in a structured, machine-readable format.
- Right to object (Art. 21)
- objection to processing based on legitimate interests or for direct marketing.
- Right to withdraw consent
- at any time, without affecting prior lawful processing.
How to exercise your rights: contact us at support@mymeda.ai. We will respond within one month of receipt, extendable by two further months for complex or numerous requests. meda does not engage in solely automated decision-making producing legal effects within the meaning of Art. 22 GDPR; any AI features support, and do not replace, human decision-making.
If your data is processed within the platform by your healthcare provider, please direct rights requests to that provider as the responsible controller.
14Supervisory Authority
You have the right to lodge a complaint with a supervisory authority. The competent authority for meda is:
Bavarian State Office for Data Protection Supervision (BayLDA)
Promenade 18, 91522 Ansbach, Germany
- Phone
- +49 981 180093-0
15Changes to This Privacy Policy and Contact
We may update this Privacy Policy when there are material changes to our data processing practices or legal requirements. We will notify you of significant changes by email and post the updated version at www.mymeda.ai with a new “Last updated” date.
Contact: meda AI GmbH · support@mymeda.ai · +49 152 02544938
Last updated: 06.07.2026
This notice is available in German and English. In case of any conflict between the versions, the German version takes precedence.



