Designing the Pre-Arrival Workflow: What to Automate and When to Require a Human Touch
The patient has paid a deposit and received a flight reminder. That evening, they report a new medication. The next automatic message still says everything is ready for treatment.
Automation continued while circumstances changed. The missing element was a rule to pause the sequence and route new information to a responsible person. Pre-arrival workflows need routine delivery and clear exception handling. The scenarios below are illustrative operating examples, not clinical instructions.
Separate delivery from decisions
Routine administrative information can often be scheduled: the address, appointment confirmation, approved document list or transport contact. Suitability, medication, preparation and travel fitness require appropriate clinical review.
Example: A system reminds someone about Tuesday’s consultation. It shouldn’t infer that the appointment clears them for a procedure. Keep statuses for booking, clinical review and other readiness checks distinct.
Write these boundaries before choosing software. Otherwise, a convenient tool may define a process nobody has clinically approved. Include the people who answer patient questions in the design, because they know where standard messages commonly fail.
Automate stable administrative tasks first
Choose tasks with reliable inputs and manageable consequences if corrected. Directions and reminders to complete agreed forms are candidates when their underlying information is current.
Example: After flight details are confirmed, the system sends the approved meeting-point guide and transport contact. Include the date and a way to report changes. Don’t expose health information to travel suppliers unnecessarily.
Every message needs an owner, review date and route to a person. Patients should be able to identify the current information and obtain help without guessing which automated sender accepts replies.
Require approval for clinical instructions
Fasting, medication and preparation guidance isn’t generic travel content. Clinicians determine what applies to the individual. Technology can deliver approved instructions but should not generate or select them without the necessary controls.
Example: The clinician approves a patient’s preparation plan. The system delivers that version and records the action. A changed procedure date or relevant health update flags it for review rather than automatically recycling it.
A familiar template isn’t permission for a coordinator to modify instructions around a new flight. Clinical ownership should be explicit in the record, including who approved a revision and when it became active.
Define events that stop the sequence
List changes requiring human review: new health information, revised treatment plans, unclear instructions, complaints, missing approval or travel disruption. Clinicians define medical escalation rules.
Example: Reporting a new medication pauses readiness messages and alerts the designated clinical team. The coordinator acknowledges receipt and explains when an update is expected. They don’t advise whether to stop or continue medication.
Provide absence cover. “Sent to the doctor” is incomplete unless someone accepts the task and unresolved items remain visible. Test what happens if an alert is missed; the process needs an escalation path rather than endless automatic retries.
Keep one current itinerary
Patients may receive dates from the hospital, accommodation provider and facilitator. Use a controlled itinerary separating confirmed appointments from provisional arrangements. Make the current version easy to identify.
Example: A review moves from Wednesday to Thursday. The coordinator updates the itinerary, checks transport and hotel implications, and confirms the change. Obsolete reminders are withdrawn instead of sending both schedules.
An itinerary shouldn’t imply a clinical promise. Discharge and return travel depend on the treating team’s assessment and relevant carrier requirements. Commercial arrangements should support those decisions, not force them.
Use a shared readiness check
Bring together the checks required by your service, assigning each to the qualified team. An overall status must be traceable to their decisions, not automatically created when a deposit clears.
Example: Coordination confirms documents arrived; clinicians confirm the review outcome; finance confirms payment; the language-support owner confirms interpretation. If a required item remains open, show the gap and next action.
For complex cases, a brief discussion may be more useful than another field on a long checklist. The aim is to expose unresolved decisions. A list full of ticks can still hide uncertainty if people interpret each field differently.
Check understanding and access
Email delivery doesn’t prove someone can open or understand an attachment. Ask about language and accessible formats. Use the clinical team’s process for checking understanding of medical information.
Example: A patient cannot open a protected document on their phone. Arrange an approved alternative and confirm access. Repeatedly sending the same file improves a delivery count without helping anyone.
The JCI hospital standards address handover communication. Make responsibility explicit whenever clinical and administrative teams exchange tasks. That is particularly valuable when software is performing some of the intermediate steps.
Pilot before expanding
Test fictional cases with missing records, changed dates, language needs and a new health concern. Then run a small supervised pilot. Measure overdue tasks, contradictory messages, correction time and unanswered questions.
A first project might automate one reminder linked to a verified appointment. Expand after staff can pause, correct and explain it. Measure time saved after review and rework rather than estimating value from message counts.
Maintain a simple change log for the automation itself. When a template or trigger changes, record why, who approved it and which test cases were checked. Staff should be able to report a problem without needing to understand the software configuration.
Discuss your pre-arrival process with Altay Medical Tourism Consulting. Bring current messages and situations requiring manual rescue. Those exceptions help identify where automation belongs and where a person must remain responsible.