Referral Management: Hospital Occupancy Is Decided at the Front Door
1,000 to 2,000 faxes a month, ten inquiries per admission, 20 to 30 practices behind 80 percent of the volume: why hospital occupancy is decided at the front door — and what to measure referral management software against.

Dr. Sven Jungmann
CEO

Monday morning in the patient admissions office of a rehabilitation clinic. The fax machine has been working through the weekend: a good forty referrals, some five pages long, some forty. A staff member sorts the stack. The third referral is missing the current physician letter, the seventh is missing the medication list, and page three of eight of the twelfth never arrived. She starts making phone calls.
At the practice that sent the third referral, nobody answers the phone — consultation hours. The medical assistant there calls back in the afternoon, retrieves the missing document and faxes it again. By the time it arrives, the referral is already sitting on a different stack at the clinic. Days pass this way, on a case that could have been decided on Monday.
The practice learns nothing of any of this. It does not know whether the referral arrived, whether something is missing, or when a decision will be made. If the patient asks, the practice calls the clinic. Then two people are on the phone with each other, both of whom have more urgent things to do.
Where occupancy is decided
The scene is not an outlier. Individual German rehabilitation sites receive 1,000 to 2,000 faxes per month, five to forty pages per transmission, frequently incomplete — with follow-up request loops that stretch over days [1]. The funnel behind this is steep: one facility we spoke with counts around 9,000 referral inquiries per year for around 900 admissions — ten inquiries for one occupied bed [1]. We described the mechanics of this bottleneck in detail in How ten inquiries become one admission (in German).
Added to this is a concentration that appears in hardly any occupancy plan: at a single site, 20 to 30 practices typically generate over 80 percent of the referral volume [1]. A facility's occupancy therefore hangs on a manageable number of relationships — and on how quickly and reliably the clinic responds to incomplete documents. A clinic that takes days to request missing documents risks the practice sending its next patient wherever it gets an answer faster. Occupancy is decided at the front door, long before a bed is scheduled.
What digital referral management has to deliver
Four requirements can be stated in vendor-neutral terms.
Submission must not take longer than the fax. A practice that has to retype form fields for a digital referral will stay with the fax machine, and rightly so. Upload the documents, extraction proposes the entries, the practice confirms: in the routine case, this has to be done in under a minute. What machine extraction from faxes and scans realistically delivers today is described in Structured data extraction from faxes (in German).
Completeness must be visible at the moment of submission, at the level of document types. "Physician letter present, medication list missing": this feedback removes the follow-up loop that otherwise costs days. The limit of this check matters: it establishes whether a document type is present. The assessment of its content stays with the clinic.
The status must be visible to the practice without a phone call. Received, under review, documents requested, response sent — an administrative vocabulary that answers the patient's question before it turns into a phone call.
And the fax stays. If 20 to 30 practices carry the bulk of the volume, some of them will never switch to a portal. A system that turns fax referrals into second-class cases damages precisely the relationships that occupancy depends on. On the clinic side, this calls for a working surface on which portal and fax referrals arrive as equals.
Where aiomics stands
This clinic-side working surface is live at aiomics: the admissions board is in production at one site of a large German hospital group. There, every referral becomes a card with document status, deadlines and ownership — whether it arrived by fax or digitally. Two details carry the daily work: cases with outstanding document requests automatically resurface as soon as new documents arrive, marked "update received"; nothing is left lying on the proverbial other stack. And accepted cases come back on their own three working days before the confirmed admission date, with public holidays taken into account. Incidentally, a field for clinical urgency does not exist in the data model; sorting follows administrative criteria such as receipt, deadline and document status. That is a deliberate boundary, not a gap.
The working surface for the practice — the portal for referring physicians (Zuweiser) — is in pilot preparation; a prototype has been demonstrated to physicians in private practice, but the portal is not yet in production. Two design decisions from it are still worth explaining, because they address the trust problem on both sides.
The first: a firewall with two axes. The practice sees document presence and administrative status, nothing else. Everything the clinic reviews internally — plausibility, knockout criteria, contractual quotas — stays on the clinic side; the portal services have no read path to these data sets, which is safeguarded with regression tests. Knockout criteria are never shown to referring physicians under any configuration. Both sides gain from this: the clinic can review rigorously without straining the referral relationship. And the practice knows its referrals are processed in a documented manner, without being graded itself. The portal's design guideline contains one sentence on this:
A 62-year-old chief physician must never feel graded by software.
That is why there are no referrer scores and no rankings. If an admission does not come about, the system calls it a "response", and the practice can forward the referral — with the patient's consent — to another facility in the group. The practice answers a document request with one click; the missing document is attached directly to the existing referral, with no new fax and no new sorting work at the clinic. On acceptance, the portal generates a printable information sheet with the organizational details of the admission.
The second: notifications without patient data. The push notification schema contains no patient fields; even a compromised notification service would reveal nothing but a reference number and a status class. Data protection thus rests on the architecture — what the schema does not know, no message can contain.
For the practice, the portal costs nothing; it is funded by the receiving facility. Practice onboarding is designed to require no IT project, with a design goal of under five minutes from invitation to first referral. The portal does not currently offer a connection to KIM (the German healthcare sector's secure messaging service).
What to measure any vendor against
How to structure a selection process overall is described in Choosing hospital admission management software (in German). For referral management in particular, five questions help:
- What does the referring practice see? Ask to be shown the practice view of a live referral. If it displays more than document status and administrative steps — ratings or acceptance criteria, say — ask under which configurations that becomes visible.
- What is in the push notification? Request the payload schema. If it contains fields for patient data, data protection rests on configuration discipline rather than on architecture.
- How do fax referrals enter the system? The same working surface and the same deadlines as digital referrals — or a side process that someone maintains by hand?
- Are referring physicians rated? Scores, rankings and per-practice response-time metrics may look good on a sales dashboard. Ask yourself how the practice will react when it finds out.
- How long does onboarding a practice take, and who runs it? If every practice requires an appointment with IT involvement, the channel effectively ends after the first ten practices.
If you want to walk through your admission pathway once, from fax stack to occupancy decision, write to us — even if you are not evaluating aiomics. Or simply read along: in our weekly briefing Visite (German; English edition Grand Rounds is in preparation), we write regularly about admissions, documentation and revenue integrity.
Sources
- Fax volumes (1,000–2,000 transmissions per month and site, 5–40 pages per transmission), the ratio of inquiries to admissions (around 9,000 to 900 per year) and referrer concentration (20–30 practices for over 80 percent of the volume): anonymized experience figures from German rehabilitation facilities and prospect conversations, as of July 2026. They serve as context; they are not industry averages.
The referral portal described here is in pilot preparation and not yet in production. Live today is the admissions board at one site of a large German hospital group.


