Enquiry
Enquiries from web and ad forms, email and messaging land in one pool.
FAB Health · Healthcare
Health Tourism Software
One patient record from first enquiry to post-treatment follow-up.
A platform that tracks the patient journey from enquiry to procedure and follow-up on one record, with agency, commission and multilingual communication management.
- No enquiry is lost on any channel
- Document access is logged
- Agency settlement tied to the case
Product tour
FAB Health, screen by screen.
FAB Health · Enquiries & cases
Every enquiry becomes a case; no channel gets lost.
Enquiries from web, email and messaging in one pool; status changes with date and owner.
- Multi-channel enquiriesEnquiries from web forms, e-mail and messaging channels collected in a single pool.
- Case lifecycleEnquiry, pre-assessment, quote, scheduling, procedure and follow-up, each with a date and an owner.
FAB Health · Patient file
Communication, quote, planning and finance in one file.
Commercial roles see the case and finance; medical documents sit in a separate permission scope.
- Multilingual communicationThe patient language is stored on the record and templates are versioned per language.
- Secure document sharingMedical documents shared with an access log showing who opened what and when.
- Consent recordsRecords which version of which text was accepted, and when.
FAB Health · Planning
Transfers, stays and procedures on one calendar.
The calendar is built from case planning fields; conflicts raise alerts.
- Procedure date, accommodation, transfer and companion details
- Patient notices from language-specific templates
FAB Health · Agencies & finance
Commission is tied to the case; reconciliation leaves no dispute.
Agency, commission rate, case list, payouts; collections and balances in multiple currencies.
- Agency and commissionAgency per case, commission rate, settlement state and currency.
- Enquiry-to-quote time reported by channel
How it works
One patient journey from first enquiry to follow-up.
Clinical records stay in the hospital system; the platform runs pre-sales, logistics and commercial relations.
Case record
Language, channel tag and owner are set; the consent version is recorded.
Pre-assessment
Medical documents are shared with access logs; clinical review stays with authorised roles.
Quote
Versioned quote from a language template; the approved version is recorded.
Payment
Multi-currency collections and balances tracked on the case.
Transfer & stay
Arrival transfer, hotel and companion plan with conflict alerts.
Procedure
Procedure date on the case; notices go out per language.
Follow-up
Follow-up is scheduled; agency commission enters the payout list after the procedure.
Who uses it?
Every role sees its own screen.
- PPatient coordinator
Enquiries, communication, quotes and reminders.
Cases · Patient file - PPhysician
Medical documents and pre-assessment, under separate, logged permission.
Documents - OOperations
Transfers, stays, companions and procedure calendar.
Planning - FFinance
Collections by currency, balances and agency payouts.
Agencies & finance - MManagement
Enquiry-to-quote time, channel and agency performance.
Reports
In a day
A patient coordinator’s day
New enquiries
All channels in one pool.
Quote approved
v2 on record; v1 unchanged.
Transfer plan
Arrival, hotel and procedure on one calendar.
Reminders
Balance and follow-up, in the patient’s language.
Integration surface
The product is not an isolated island.
Data ownership, error handling, security and audit trails are designed as part of the implementation.
- Clinic and hospital systems
- Email and messaging
- Banking and payment services
- ERP and accounting
- BI and reporting
- REST API · Webhook
What is the health tourism platform?
A health tourism operation solves a different problem from a hospital information system: the pre-sales process, logistics and a multi-party commercial relationship. This platform tracks the journey from the moment an enquiry arrives to the follow-up call, on a single record.
Which problem does it solve?
The typical starting picture is this: enquiries scattered across messaging apps and e-mail, medical documents on personal devices, agency reconciliation in a separate spreadsheet. It appears to work, but three things cannot be measured:
- How long an enquiry takes to answer,
- How many cases each agency brought and the state of its settlement,
- Who accessed a medical document.
The third is not only operational but legal: where special categories of personal data are processed, access must be logged.
How it works
Every enquiry opens a case. The case moves through defined states, and each transition is recorded with a date and an owner. Questions such as "how many days from enquiry to quote" and "from quote to approval" are then answered from a report.
Communication history (e-mail, messages, call notes) is attached to the case rather than left scattered across channels. Medical documents sit in a separate authority scope: the user running the commercial process sees case state and financial data, not clinical documents.
Modules
- Enquiry and case: multilingual forms, channel tagging, pre-assessment, quote generation.
- Scheduling: procedure date, accommodation, transfer and companion details.
- Documents: upload, versioning, access log and retention period.
- Agencies: agency records, commission rates, case lists, settlement and reconciliation.
- Finance: multi-currency, collection tracking, outstanding balance.
- Communication: templates per language, consent state, delivery history.
Integrations
Web forms and advertising channels, e-mail and messaging channels, CRM processes, bank integration and fintech infrastructure for collections, accounting and e-documents, and API integration for data exchange with hospital information systems.
Architecture and data responsibility
- Data scope in addition to role-based authority: an agency sees only its own cases.
- Access to medical documents is protected by separate rights and an immutable access log.
- Marketing consent and clinical information are separate permissions; withdrawing one does not stop the other.
- Consent texts are versioned, recording which version was accepted.
- Retention periods are defined per record type and applied when they expire.
Data residency: server, backup and sub-processor locations are each determined separately and defined in writing. This scope is clarified with the legal side at the start of the project.
Usage scenarios
- International patient unit of a clinic or hospital: enquiry pool, quoting and scheduling.
- Intermediary agencies: multiple clinics, agency networks and commission management.
- Single-speciality centres: a narrow procedure set with standard quote templates.
Roll-out
- Data inventory and authority: roles, access scope, retention periods, consent texts.
- Enquiry and case tracking: channels, states, quote generation.
- Documents and communication: secure sharing, access logging, multilingual templates.
- Agencies and finance: commission, settlement, multi-currency.
Phase one is not skipped: when authority and retention rules are added later, everything accumulated until then sits outside those rules.
Frequently asked questions
Does this replace a hospital information system?
No. Clinical records, tests and prescriptions belong to the HIS. This platform manages the pre-sales process, logistics and the commercial relationship, exchanging data with the HIS where needed.
Should an agency portal see all patient data?
No. Case state, scheduling date and financial information are enough to run the commercial process. Medical documents and clinical detail sit in a separate authority scope.
How is multilingual content managed?
Every text field has its own record per language. For patient information texts, translation approval is a distinct step, recording which version was approved in which language.
What happens when a deletion request arrives?
Deletion or anonymisation is applied according to record type; data under a statutory retention obligation, such as financial records, is handled separately. How that distinction works for each record type is defined before go-live.
See the product with your process
Explore the health platform →