Home / Guides / Medical tourism

Medical tourism

How do you safely collect photos and history before a remote consultation?

Ask only for what the clinician needs, get clear consent that explains the purpose and storage, use a controlled upload route instead of open chat, and give simple instructions so patients send usable material. Check your local privacy rules.

Your clinician wants photos and a medical history before the video call. The patient sends six blurry pictures on WhatsApp, a PDF in another language, and a voice note. Now your team is wondering where this material lives, who can see it, and whether the patient ever agreed to this.

The short answer: decide what the clinician really needs, ask for consent in plain words, use a secure way to receive files, tell patients exactly how to take useful photos, and store everything with limited access. Privacy rules differ by country, so check what applies to you. This is not legal advice.

Step 1: Define the minimum you need

Ask the clinician to list what they need for each type of consultation. Less is better. Collecting everything "just in case" increases your risk and annoys patients.

  • Which photos, if any, and from which angles?
  • Which parts of the medical history are relevant?
  • Which reports or test results are useful, and how recent should they be?
  • What can wait until after the first consultation?

Turn the answer into a short checklist per consultation type, so every coordinator asks for the same things.

Step 2: Get clear consent first

Before any file is sent, tell the patient what you are asking for, why, who will see it, how long it will be kept, and how they can ask for it to be deleted. Use plain language and the patient's own language where you can. Record the consent with the date and what was agreed.

  1. Explain the purpose: for the clinician to review before the consultation.
  2. Name who will access it, for example the treating clinician and a small named team.
  3. Explain storage and retention in simple terms.
  4. Explain that sending files is optional and that they can withdraw.
  5. Do not use the files for marketing, case studies or social media without separate, explicit permission.

Step 3: Choose a controlled way to receive files

Open chat is convenient, but it is a poor place to keep health information. Where you can, use a secure upload route set up for this purpose, with access limited to those who need it. If a patient sends something in a chat first, thank them, confirm receipt, move the file to your controlled storage, and remove it from personal devices according to your policy.

  • Do not ask patients to send files to a personal phone or personal email.
  • Do not forward patient files between staff through casual messaging.
  • Use consistent file names that do not expose more detail than needed.
  • Keep a log of who accessed what and when, if your system allows it.

Step 4: Give instructions that produce usable photos

Poor photos waste a consultation. Send a short, friendly guide with examples.

  • Use natural light, a plain background, and no filters.
  • Take each photo from the angles the clinician lists, with the camera steady and in focus.
  • Include a close view and a wider view where requested.
  • Remove jewellery or clothing only as the checklist says, and only to the extent the patient is comfortable.
  • Photos of minors need a parent or guardian's involvement and consent, so check your rules.

Say clearly that the photos are for review by a qualified clinician and that nobody on the coordination team will interpret them. Patients should never be told what a photo "means" by a coordinator.

Step 5: Handle history and records with the same care

Offer a structured questionnaire instead of asking patients to write it all in a message. Allow documents in other languages and note that they may need translation by a qualified translator before the clinician relies on them. Let patients say what they do not want to share, and tell the clinician what is missing rather than guessing. Keep your own notes factual, and avoid recording opinions about the patient.

Step 6: Store, limit and delete

Decide where files live, who has access, and when they are deleted if the patient does not proceed. Write a short retention rule and follow it. If a facilitator or agent is involved, agree in writing what they may see and what they may not. For more on how enquiries and documents sit in a wider process, see our inbound page.

Common mistakes

  • Asking for files before consent. Explain first, collect second.
  • Keeping patient photos on staff personal phones. They get lost, shared and never deleted.
  • Using photos in marketing without separate permission. Consultation consent does not cover it.
  • Coordinators commenting on photos. Interpretation belongs to the clinician.
  • Collecting more than needed. Every extra file is extra risk.
  • No deletion rule. Old files sit around for years.

Next steps

We build the intake steps, consent wording and handover into the enquiry process through our done for you service, and you can start a conversation on the contact page. The Clinic Lead Kit also includes templates you can adapt, though you should have your own adviser review consent wording for your location, and you can find it at /kit.

Questions people ask

Can patients send photos over WhatsApp?

They often will, but it is better to move files to a controlled upload route quickly, get consent first, and follow your local privacy rules on health information.

Do I need consent before asking for medical history?

You should explain the purpose, access and storage before collecting anything and record the patient's agreement, and a qualified adviser can confirm what your local law requires.

Can we use patient photos in our marketing?

Not without separate, explicit permission that is distinct from consent for the consultation, and many clinics choose not to use patient images at all.

Want this handled, or want the playbook?

We can set the whole thing up for you, or you can follow the same steps yourself with the manual, templates and trackers.