Case study · Anonymized · Care coordination
Medical travel fails when the quote, the consent, and the flight are three products
The patient is buying a journey: a procedure, a place to stay, a transfer, and a person who answers when the visa date slips. A hospital system does not run that journey. A chat group does not either.
In plain terms: one case holds the package price, the people allowed to see it, the consent, and the travel checklist. The hospital’s own clinical system keeps running the ward. This platform runs the trip around the ward.
The price the patient saw is not the invoice
Coordinators describe the same scene. A facilitator sends a PDF. The hospital sends another number. Accommodation is a third message. By the time finance invoices, the all-in price has moved and nobody can point at the version the patient accepted.
A package is one object: procedure, length of stay, accommodation, and transport, with a price the patient was shown. Changing a line is a new version, not an edit that rewrites yesterday’s quote. The invoice is raised from the accepted version. Currency is whatever the sale was actually made in, which is often not the hospital’s home currency. The margin between the hospital’s cost and the package price is visible to the coordinator and hidden from the patient.
Four people, four logins
The patient, the facilitator, the provider, and the internal coordinator do not share a thread.
- The patient sees their package, their documents, their dates, and a way to ask a question that reaches the coordinator.
- The facilitator sees the cases they are responsible for, not the company’s other patients.
- The provider sees the clinical and scheduling facts they must confirm, not the facilitator’s margin.
- The coordinator sees all of it, including the pieces the others must not.
Comparison pages (specialty, what is included, what others charge) are how a patient chooses. They are public information. The case file behind the choice is not.
Consent has to be on the case
Signed consent that lives in an email will not be the file the clinician opens. Uploads, the signed consent, and a teleconsult before travel and after travel belong on the case. A video call that is not attached to the case is a call the next coordinator cannot find.
This is not the recuperative-care chart and not a full hospital record. It is the cross-border file: identity, the package, consent to share records with the destination clinic, and the notes from the consults that bookend the trip.
The visa slips, the hotel does not
Travel fails on status nobody owns. A checklist with a named owner per step (invitation letter, visa, flight, airport transfer, hotel, procedure date, follow-up) is the difference between a date that moves everywhere and a date that moves only in someone’s head.
When the procedure date moves, the stay and the transfer have to move with it on the same case. A spreadsheet column called “status” that is optional will be empty the week it matters.
What we do not pretend this replaces
The destination clinic still needs its own clinical system for the day of the procedure. Mixing ward orders into the travel product makes both worse. The travel platform hands over a patient who is expected, consented, and paid against a package. The clinic system takes it from there. If the clinic also needs that ward system, that is a separate build.
Patients, hospitals, and facilitators in one thread?
Tell us the markets and whether you need the patient side, the facilitator side, or both.