Skip to content

Operations and Patient Journey

Patient Journey Mapping: Turning Five Stages Into CRM Statuses

A CRM configured without a written journey just records everyone's private version of the process. The five stages, their exit criteria and the status list.

Why the map comes first

The most common reason CRM implementations disappoint is that the system is configured before the process is agreed. A status list is created while the team still has not answered "what stages does a patient pass through here?" — and the result is a system everyone fills in according to their own logic, where no report can be trusted.

Patient journey mapping writes that agreement down. What it produces is not a diagram but a shared language: when someone says "in assessment", everyone means the same thing.

Five stages and their exit criteria

Every stage needs an exit criterion — what condition moves a patient onward? A stage without one gets filled in by guesswork.

StageWhat happensExit criterion
1. ContactFirst message, source taggedConsultant assigned and first reply sent
2. AssessmentQualification, documents, clinical opinionTreatment and suitability confirmed
3. QuotePackage prepared, sent, followed upAccepted or declined
4. CoordinationDates, flights, transfer, stay, paymentPatient arrived, procedure done
5. AftercareCheck-ins, satisfaction, referralFinal check-in completed

Stage five needs an exit criterion too, or records sit "open" forever and your real workload becomes invisible.

Turning stages into statuses

Stages map directly onto the status list. Two additional rules:

  • Separate the lost reasons. "Lost" alone is not enough; record why (price, timing, unreachable, unsuitable, competitor). Without the reason there is nothing to improve.
  • Add an on-hold status. For records whose active follow-up ended but which are not dead. This is the pool your reactivation campaigns draw from.

For detail that does not fit a stage, use tags: language, treatment type, VIP, travelling with a companion. Tags may overlap; statuses must not.

One number per stage

The map becomes managerially useful once each stage carries a measure:

  • Contact: average first-response time.
  • Assessment: time to collect documents.
  • Quote: qualification-to-quote time and quote acceptance rate.
  • Coordination: cancellation rate after acceptance.
  • Aftercare: satisfaction and referral rate.

Those five numbers write your monthly meeting agenda by themselves. How to calculate them is in conversion rates.

Keeping the map alive

A journey map is not a document you draw once and hang on a wall. Every quarter, sample at least twenty real records and ask whether the flow in the system still matches the flow in reality. Common drifts:

  • Consultants systematically skipping a stage — it is usually redundant; remove it.
  • An intermediate state everyone uses that is not on the list — add it.
  • A status nobody ever selects — delete it; an unused option is noise.

The product-side equivalent of the whole process is on the medical tourism CRM page.

Frequently asked questions

How many statuses should there be?

Try to stay under seven. Too many statuses lead consultants to pick more or less at random, which makes the reporting meaningless. If you need more detail, use tags rather than statuses.

Can a stage be skipped?

Yes, and that is normal — a referred patient may move through assessment very fast. What matters is that the skip is recorded and that the system also allows moving backwards.

Who should map the journey?

The people who run it, not a manager at a desk. The fastest method is a two-hour session with two consultants and an operations lead, drawing the actual flow of the last ten patients on a whiteboard.

MetoCRM modules mentioned in this article

Status ManagementPatient TrackingTagsMedical Tourism CRMAll modules

MetoCRM is a business management platform built for medical tourism companies. From patient records and quotes to partner hospitals and accounting, it runs the whole operation on one screen.

Request a demo See pricing