A patient is not a parcel with a name
Generic dispatch systems plan routes well. What they do not know as a data field are Muster 4, the co-payment exemption, the weekly dialysis rhythm and the carry chair. So exactly these things end up in free-text fields, where no rule and no report reaches them.
Where MitaBase is not the right fit
- When patient rides are only a small part of your business (courier, parcel, passenger transport without a form) and route optimisation across many stops is the actual problem.
- When you need a connection to payers under § 301 or § 302 SGB V or a fuel-card API today.
| CRITERION | GENERIC DISPATCH SOFTWARE | MITABASE |
|---|---|---|
| Transport form (Muster 4) | No field of its own; ends up in free text | Photo on the ride, checked by the office; automatic AI check in preparation |
| Dialysis: the same week, every week | Create every ride one by one | Paste the week as a block or read it from Google Sheets, duplicates are caught |
| Co-payment / exemption | Free text or a note | Stored with the passenger, visible in the driver app |
| Driver app | Depends on the product | Rides, time, cash, chat |
Frequently asked questions
Can we not solve this with free-text fields?
For a while, yes. But a free-text field is not a data field: no rule reads it, no payment note follows the co-payment exemption, and no report reaches it. Everything in free text is manual work at month-end. Exactly the manual work dispatch software is meant to take away.
What about interfaces to our existing software?
Today: CSV import and export for everything, an import from text and tables for rides, PDF for timesheets. Interfaces to accounting, DATEV included, are in preparation; we name a date only when there is one. There is no connection to payers under § 301 or § 302 SGB V and no fuel-card API. If you need a particular interface, tell us which; we will tell you whether and when.
When is a generic solution the better one?
When patient rides are only a small part of your business, meaning courier, parcel or passenger transport without a form, and route optimisation across many stops is the actual problem. MitaBase is not built for that. As soon as Muster 4, co-payment, wheelchair and dialysis rhythm run your day, a solution that knows these things as data fields is the better one.