Two things people conflate
"We already have an HIS, why would we need a CRM?" is the most common objection in medical tourism software research. The short answer: they are not competitors; they solve different problems.
A hospital information system runs clinical and administrative processes: admissions, outpatient clinics, beds, laboratory, imaging, prescriptions, billing. Its subject is the patient who has arrived.
A CRM deals with someone who is not yet a patient: the person messaging on Instagram, asking prices, undecided. Its subject is the person who has not arrived, and its job is to bring them.
Side by side
| Dimension | HIS | Medical tourism CRM |
|---|---|---|
| Who it manages | Registered patients | Enquirers and coordination |
| Starting point | Admission | First message / ad click |
| Channels | Internal | Instagram, WhatsApp, ad forms, calls |
| Pricing | Tariffs, insurance, invoices | Line-item quotes, multilingual, packages |
| Travel | Out of scope | Flights, transfer, accommodation, companions |
| Clinical records | Core function | Not kept (documents stored) |
| Reporting | Operational and financial | Channel, conversion, consultant, cost per patient |
| Regulatory status | Usually mandatory | Commercial choice |
Where to draw the line
The most practical test is one question: "Is this information needed to bring the patient, or to treat them?"
- To bring them: which channel they came from, what you quoted, how many times you called, why you lost them, when they fly — CRM.
- To treat them: diagnosis, test results, prescriptions, operative notes, discharge summary — HIS.
The grey area is documents: an X-ray or blood panel the patient sends lands in the CRM because it is needed for pre-sale assessment. That does not make the CRM a clinical record system — it stores the file, not the medical record. The distinction also matters for data protection: the fewer places clinical data sits, the better.
Matching one patient across two systems
When both are in use, the real issue is not integration but a shared reference. It is the root of month-end reconciliation arguments and of "was this patient ours?" questions.
The minimum that works:
- Every patient closing in the CRM gets one reference number.
- That number is written into the HIS record too (file number field or a note).
- Monthly reconciliation runs on that number.
Full automated integration is possible but rarely pays for itself. A shared reference number solves most of the problem for a fraction of the cost. For settlement detail see commission and settlement tracking.
Which one first?
It depends on the shape of the business:
- If you are a facilitator, you do not need an HIS at all — the partner hospital treats. You need only a CRM.
- If you are a clinic or hospital, the HIS already exists. Add a CRM once international enquiries pass roughly 30-40 a month.
- If you are starting out, CRM first: before patients arrive, an HIS has nothing to manage.
See MetoCRM's scope on the product page and the operations side on Meto Operation.