Can you use SAP Concur Travel for patient travel?

Published 2026-09-15

SAP Concur is the travel and expense system a health system's finance team is most likely to already own, which makes "just book the patient through Concur" the most common version of this question. The answer is the same shape as for every corporate tool: it can, through a guest path, and the patient-specific work stays with a person.

Can you use SAP Concur Travel for patient travel?

What Concur Travel was built for

Concur Travel is the booking half of an integrated travel and expense platform. An employee with a profile books inside a policy, the booking is approved, paid on a corporate instrument, and lands in Concur Expense as the start of an expense report. Arrangers can be assigned to travelers so an assistant books on an executive's behalf. The whole system is organized around the fact that the traveler works for the organization and will account for the money afterward.

Profile, policy, approval, corporate payment, expense report
Arrangers assigned to travelers by the traveler, an admin or another arranger
Travel and expense as one record for the finance team

The guest booking path

For a traveler with no profile, Concur Travel provides guest booking: an authorized user books on behalf of a guest, the reservation is created without a stored traveler profile, and payment comes from a company ghost card, the booker's own card, or a temporary card issued for the trip. This is the path built for interview candidates, contractors and visiting guests, and a patient would use it.

In practice a coordinator with arranger permission books each patient trip as a guest booking, enters the patient's name and details for the reservation, chooses a payment instrument the organization controls, and forwards the confirmation. Nothing about the search knows the patient is going to a treatment site.

An arranger books for a guest with no profile
Payment: company ghost card, booker's card or temporary card
Built for candidates, contractors and visitors

What stays manual for a patient

Choosing the hotel for the door: Concur searches by city and policy, so the arranger has to know which properties are near the site and check the distance elsewhere. Telling the patient: the confirmation is Concur's, so the arranger writes the front-desk details, the reminder and the cancellation terms in their own email. Family-paid trips: a guest booking is paid on an instrument the organization controls, so a room on the family's card is outside the model. And the record: a guest booking sits in the travel data as a guest trip, so "patients served at site X this quarter" is a report someone builds from exports.

Site proximity checked by hand
Patient communication written by hand
Family-paid trips outside the payment model
Per-patient, per-site reporting built from exports

When Concur is the right answer

A health system whose finance team lives in Concur, pays for every patient trip itself, books a small number of them a year through a named arranger, and does not need the patient to feel the trip is the program's can stay in Concur with no regret. The guest path exists for exactly this kind of occasional non-employee trip.

Organization-paid, low volume, a named arranger, finance already in Concur

When it is not

Self-paying patients, volume across many sites, and programs that want the trip in their own name are the three cases that outgrow a guest booking, the same three as for Egencia. The category page compares the options, and the guide on the BAA question covers what a compliance officer will ask about patient details in a corporate system.

Self-paying patients, scattered sites, or a program-branded trip

Common questions

Does a guest booking in Concur create an expense report?

A guest has no profile and no expense account, so the booking is paid on an organizational instrument and reconciled by the booker or finance, not through the guest. That is the intended design for non-employee travel.

Can the patient see or change the booking themselves?

Not in the way an employee can. The guest has no Concur login; changes go back through the arranger, which for a moved surgery date means a phone call to the coordinator.

Is patient data in Concur a HIPAA question?

A guest booking holds a name and travel dates, sometimes a date of birth. Whether that is protected health information in context, and what your Concur agreement says about it, is a question for your compliance officer. Ask before the first booking, not after.