New in MITA Base: return-ride coupling & DATEV export

With version 2.4 we're shipping two features many of you asked for. Both target the same thing: less manual work at the points where mistakes are most expensive — daily planning and billing.

Return-ride coupling for recurring rides

Until now, outbound and return had to be created separately for recurring appointments. That was error-prone: a forgotten return meant either an emergency call in the afternoon or a van driving back empty and having to set off a second time.

From now on, MITA Base couples the return ride automatically as soon as you create a series:

• One appointment, two rides: you set up the dialysis series once — MITA Base plans outbound and return as a coupled pair.
• Automatic time windows: the return is pre-planned based on the typical treatment duration and can be adjusted per appointment.
• Conflict check included: if the return collides with another route, the system speaks up — before the day begins, not in the middle of it.

In practice this means: dialysis patients on a fixed Tue/Thu/Sat rhythm are fully scheduled after a single setup, return trip included. No more chasing calls.

DATEV export for billing

The second addition concerns everyone who works with a tax advisor or accounting team. The new DATEV export bundles your billed rides in a format that can be imported directly:

• Export per payer and period
• Separation by co-payment, insurer share and private payer
• Handover as CSV or in the DATEV booking-batch format

What used to be a manual transfer of numbers — with all the typos that come with it — is now a click. The accountant gets clean data, you save the evening at month-end.

Availability

Both features are available immediately in all plans where the relevant modules are active — return-ride coupling in Dispatch, the DATEV export in the billing module. Existing series aren't converted automatically; the next time you edit a series, MITA Base offers the coupling.

As always: if something is missing from either of these features, or you have an edge case we didn't consider — write to us. A good part of these two features comes directly from feedback by operations that felt exactly these gaps in daily work.