The conversation writes the report.
MiRA listens to the doctor-patient conversation and turns it into a structured draft in under 60 seconds, entirely inside your hospital.
The reality in clinical practice
Three of eight hours go into documentation.
A third of physicians’ working time goes into reports, coding and handovers. That time is missing at the bedside, and the shortage of staff does not make it cheaper.
176,800physicians work in German hospitals under this split.
Under 60 secondsis what MiRA needs from the end of the conversation to a structured draft.
Figures from published surveys on documentation workload in German hospitals.
From conversation to draft, in under a minute.
Five stations that sit inside the treatment process, not next to it.
Consent
Recording starts at the push of a button, only after the patient has consented. MiRA records that consent with the case.
Listening
Speech recognition runs on your hardware. No audio leaves the building.
Understanding
MiRA separates physician and patient voice and identifies history, findings, diagnosis, treatment plan and medication.
Drafting
A structured draft appears: medical report, nursing note, ICD-10 coding, follow-up tasks.
Release
You review, correct, confirm. Only then does the report enter the hospital information system.
Why MiRA is built differently
Built for German hospitals, not adapted to them.
No audio leaves your hospital.
Audio, transcript and patient data stay on your hardware. No processing by third parties, no detour through external servers, no dependency on an internet line.
GDPR by design
Developed under German and European data protection law, not retrofitted. A prepared data protection impact assessment is included.
Trained on German
Medical vocabulary, clinical abbreviations and dialects from ward routine, not from a textbook.
Integration via HL7 FHIR
MiRA extends your existing environment instead of placing a second one next to it. The released report lands where your team already works.
Two ways to document one conversation.
The difference is not the language model, it is the architecture: does the data leave the building or not.
Processing outside the hospital
Recording goes to an external service- Data location
- Provider’s data centre
- Legal basis
- Data processing agreement, contractually secured
- Operation
- Outbound connection required
- Control
- Model and updates sit with the provider
Processing inside the hospital
MiRA runs on your infrastructure- Data location
- Your hospital
- Legal basis
- Processing stays in your responsibility
- Operation
- Runs without an internet connection
- Control
- Model version and releases stay with you
What hospitals ask before rollout.
Where are the recordings processed?
On servers inside your hospital. Audio, transcript and patient data never leave your infrastructure, not even for model improvement.
How is patient consent documented?
Recording only starts once consent is given. MiRA records that consent is in place and logs the process traceably.
Which hospital information systems can MiRA connect to?
Integration runs via HL7 FHIR, including Orbis, SAP IS-H and i.s.h.med. We review further systems in the initial call.
Who is responsible for the finished report?
The treating physician. MiRA produces a draft and not findings, the release stays medical.
See MiRA on a conversation from your own department.
In the demo we walk the whole path once, from recording to released draft, with an example from your department.