Discharge Letter Automation
A possible setup for automated discharge letters: HIS integration, AI draft, physician approval, KIM dispatch. Demo, not a certified product.
- Industry
- Healthcare
- Build, estimated
- 10–12 weeks
At a glance
- It starts with
- Discharge Triggered
- The machine handles
- 13 of 15 steps
- A person keeps
- Doctor Review · QES Signature
- Bottom line
- -89%Time Saved
The problem
Real talk: nobody likes dictating discharge letters. You spend the day seeing patients, evening rolls in, the stack is still untouched, and the medical review board is asking again.
Twenty minutes per letter on average. A clinic with thirty discharges a day means ten hours of dictation time — every day, spread across doctors who should be seeing patients instead.
The uncomfortable part: letters go out two weeks late, referring colleagues call, the patient waits for rehab — all because there's no pipeline between dictation and dispatch.
Here's the pipeline.
Discharge letters are critical for continuity of care, but the manual process is extremely time-consuming: 30–45 minutes per letter, copy-paste between 5–7 systems (HIS, LIS, RIS, pharmacy, OR documentation). With 100+ discharges daily, that's 50–75 physician hours per day. A significant share of letters miss the typical 24-hour deadline for dispatch to the general practitioner. Quality issues from missing information and inconsistent wording endanger patient safety.

Staged scene
Tuesday, 5:30 pm
Consultation hours are over. The doctor's letters are not.
Diagnoses, medication and findings sit in different systems. The workflow can assemble the draft; checking and signing stays with the doctor.
The process, step by step
Scroll through. The diagram stays put and highlights the step you are on.
- 01
Discharge Triggered
HIS Trigger
A discharge is documented in the HIS and automatically triggers the letter creation process.
- 02
Data Collection
FHIR/HL7
The system collects all relevant patient data from the HIS via FHIR R4 and HL7 v2 interfaces.
- 03
Parallel
Data collection is split into parallel paths for optimal processing speed.
- 04
Diagnoses
ICD-10-GM
Diagnoses are extracted with ICD-10-GM codes from the system and prepared for the letter.
- 05
Medication
ATC Codes
Medication data with ATC codes is compiled from the patient's home medication and inpatient prescriptions.
- 06
Join
All data collected in parallel is merged into a complete dataset.
- 07
AI Structuring
LLM (local or EU cloud)
The AI structures all data according to department-specific templates and generates medically accurate wording.
- 08
Draft Generated
Template-based
A complete letter draft is generated, including all relevant sections and recommendations.
- 09Human decides
Doctor Review
2-3 Min
The responsible physician reviews the draft and makes adjustments if needed – typically in 2-3 minutes.
- 10Branch
Approved?
Gateway: Was the letter approved by the physician or are corrections required?
- 11
Corrections
Adjustments
If changes are requested, corrections are incorporated and the letter is resubmitted for review.
- 12Human decides
QES Signature
D-Trust
The approved letter is signed with a qualified electronic signature (QES) via D-Trust, making it legally valid.
- 13
KIM Dispatch
To GP
The signed letter is automatically sent via KIM (gematik) E2E encrypted to the general practitioner.
- 14
Archiving
Patient Record
The letter is archived in the electronic patient record and stored for future reference.
- 15
Complete
Letter Delivered
The process is complete. The GP has received the signed letter, delivery is confirmed.
What changes
Possible setup, not a packaged product
The figures are modelled target values for a possible setup, derived from industry benchmarks and our own tests. They do not come from a customer project; real values depend on your business. We do not sell this setup as a finished product: we measure where your bottleneck is, then build with your team. For systems that require certification (e.g. HIS, gematik, DATEV-certified) we work with specialised partners.
Before vs. After
| Aspect | Before | After |
|---|---|---|
| Time per Letter | Before: 30–45 minutes | After: ~5 minutes (with physician approval) |
| Data Sources | Before: Manual copy-paste from 5–7 systems | After: Automatic aggregation via FHIR/HL7 |
| 24h On-Time Rate | Before: Often below 70% | After: Target ≥ 95% |
| Signature | Before: Handwritten or without qualified signature | After: QES (legally valid under eIDAS) |
| Dispatch to GP | Before: Fax, mail, or unencrypted email | After: KIM (E2E encrypted, with delivery confirmation) |
Technology
Technology Stack
Integrations
Systems this setup can connect to
- SAP IS-HHIS
- Complete integration via SAP interfaces for patient data, diagnoses, and medication
- Orbis (Dedalus)HIS
- Native FHIR R4 connection for real-time data retrieval
- D-TrustSignature
- Qualified electronic signature for legally valid documents
- KIM (gematik)Communication
- Secure dispatch via telematics infrastructure to general practitioners
Security & Compliance
What the setup takes care of
- GDPR Compliant
- Full compliance with EU General Data Protection Regulation. Data processing in Germany.
- ISO 27001
- Data processing in ISO 27001 certified data centers.
- KIM Encryption
- End-to-end encryption via gematik's telematics infrastructure.
- On-Premise Option
- Optional operation in your own infrastructure without external data transfer.
Frequently Asked Questions
What would this look like at your company?
This workflow is a demo. Whether it pays off for you depends on where things get stuck at your company. The method page shows how to find out. To place a workflow of your own, use the free assessment. No call needed.