Erimworks

Erimworks/Medical tourism softwareLast updated:

International Patient OS: from the first message to the closing of the incentive file

International Patient OS is a browser-based medical tourism operations and CRM system for clinics that treat patients from abroad. From the first message to the closing of the incentive file, surgeon review, quotes, flights, hotel, transfers, surgery, follow-up and the incentive application run on a single case record. Steps that most clinics keep in six separate places are tied to the same patient. The interface is in Turkish and English; the infrastructure for six more languages is ready.

What is a medical tourism CRM?

A medical tourism CRM is software that manages, in one record, the patient communication, quote and case process, travel plan and per-case finance of clinics that treat patients from abroad. It differs from a general CRM in that the work does not end when the quote is accepted: flights, hotel, transfers, surgery, follow-up and the incentive file (the application record for government support) are tied to the same patient. International Patient OS is a medical tourism CRM that runs these steps on a single case record.

Who uses it

What it does

One inbox and multilingual communication

Every message from WhatsApp Business, email and the web form lands in the same inbox. Team assignment, tags, response-time targets and internal notes sit on the same conversation. If the patient's language is different, the original text, the translation and any correction are stored as separate versions; who corrected what is not lost.

Voice notes and transcripts

A clinician leaves a note by speaking and the recording is turned into text. What comes out is a draft: it waits in a review queue and does not leave it until a clinician has read it and said it is right. The queue is not an archive — it shows only what has not been decided on, so decided items do not bury the ones that need somebody. A transcript is translated into the patient's language when it needs to be.

From lead to case

An incoming message becomes a lead, and the lead becomes a case. The case moves through a state machine: which stage can follow which is defined in code and cannot be skipped. The medical profile, consent versions, photos and test files are attached to the case; viewing and downloading are separate permissions.

Surgeon review, quotes and packages

The surgeon reviews the file, writes the suitability note, and a task falls to the coordinator. The quote is generated from a package, a discount requires approval, and the accepted quote is frozen on the case together with its price.

Surgery, travel and the field

When surgery is scheduled, conflicts are refused at database level. The flight record carries the time zone of both ends and the PNR is masked; for hotels, the cost and the price charged to the patient are kept separately, so the margin is visible as it is. For transfers, the driver sees only that day's manifest, not the whole case.

Finance and incentives

The payment record is an immutable ledger; the same receipt is never posted twice. The exchange rate is chosen for the day of the transaction and frozen on the line; it does not change afterwards. On the incentive side, regulations are not hard-coded; they are held as versioned data, so when a rule changes, past calculations are not broken. A salary month cannot be claimed twice, and double funding is checked.

Partner and agency commission

Who sent the patient, what they are owed for it and what is still to pay sit on one screen. Agencies, referring doctors and partners are defined with their commission plans; a case is attributed to a partner and the commission accrues against the accepted quote, passes through approval and is paid. A case that has been paid cannot be quietly re-attributed to another partner; the record locks.

Complications and clinic health

A complication is opened on the case's own register and its status moves there. Complications that are open across the clinic are also listed in a single queue: answering "which of our patients is in treatment for a complication right now" does not require opening every case.

The clinic health board says what this clinic should do differently today — operational work, not a connection error or a provider response. Technical detail lives on a separate screen under a separate permission; a clinic manager is not shown a raw failure dump.

Patient portal

Patients see their own journey, in their own language, on their own screen: their dates, their documents, their quote, their payments and the messages they have written to the clinic. Visibility is off by default: nothing is visible to the patient unless the clinic explicitly opens it.

The documents and payments pages ask for a second factor, and that proof is renewed every ten minutes. The reason is the realistic threat: a phone left unlocked on a table. Downloading a medical document is not the same act as checking a flight time.

Load-bearing decisions

DecisionWhat it means in practice
Tenant isolation is enforced in the databaseA query with no tenant returns zero rows; it fails closed, not open.
Money is held as integersRounding errors in cents do not accumulate.
The audit log is append-onlyWho changed what and when cannot be deleted.
Regulation is dataWhen an incentive rule changes, old files are not recalculated.
AI makes no clinical decisionIt summarises and flags; it does not diagnose or decide on suitability.
No silent failureSomething unmeasured is not counted as zero; an incomplete calculation says it is incomplete.

Access and deployment

Desk work runs in the browser. For work in the field there is a separate mobile app — Patient OS Field: the driver's day, the surgeon's morning list and the coordinator's inbox. It has no advertising, tracking or in-app purchases; the clinic opens the account. It is not an app for patients: patients reach the clinic on WhatsApp and see their own records in the web portal.

A clinic can publish the platform under its own domain. The domain is added from an admin screen, the setup instruction is generated from that record itself and verification is carried out by the system; the address the patient sees is the clinic's own.

On the calendar side, a personal subscription link is generated so appointments appear in Google or Outlook. Only a digest of the link is stored, so the address is shown exactly once — if it is lost, a new one is issued and the old one stops working.

The interface is in Turkish and English. The infrastructure for German, French, Arabic, Russian, Italian and Spanish is ready and enabled on request.

The clinic-side legal texts are on the product's own domain: privacy, terms, support.

Frequently asked questions

How is it different from a general CRM?

The difference between International Patient OS and a general CRM is where the work ends. A general CRM tracks the sales funnel and its job is done when the quote is accepted; in medical tourism the real work starts there: surgeon review, flights, hotel, transfers, surgery, follow-up and the incentive file all belong to the same patient. International Patient OS keeps all of those steps on a single case record.

We have several clinics. Can we manage them all from one place?

International Patient OS can manage several clinics from one place. In multi-clinic organisations, ownership is defined once, isolation stays at clinic level, and the central operations board is read separately for each clinic. Delegating authority never widens a role, only narrows it.

What is needed for the WhatsApp integration?

The WhatsApp integration of International Patient OS needs the clinic's own Meta WhatsApp Business account and template approval. That step takes calendar time on Meta's side; the rest of the deployment does not depend on it, and the integration is connected later.

Can we import our existing patient records?

Existing patient records can be imported into International Patient OS: patient, quote and payment records held in spreadsheets are imported. Field mapping is agreed together during deployment.

We pay commission to agencies — can we track that in the system?

You can. Agencies, referring doctors and partners are defined with their commission plans; a case is attributed to a partner, the commission accrues against the accepted quote and passes through approval and payment. Who has earned what, and how much is still unpaid, is on one screen. A case that has been paid cannot be quietly re-attributed to another partner.

Will our patients see our own domain?

Yes. A clinic can publish the platform under its own domain: the domain is added from an admin screen, the setup instruction is generated from that record itself and verification is carried out by the system. The address the patient sees is the clinic's own.

Is there a mobile app for patients?

There is no app aimed at patients, and that is deliberate: patients already reach the clinic on WhatsApp, and they see their own dates, documents, quote and payments in the web portal, in their own language. Patient OS Field is for the field team — driver, clinician and coordinator; it is distributed to the clinic's staff as part of deployment.

What does it cost?

International Patient OS follows an enterprise licence model; the price is quoted based on the number of clinics and users. For a quote and a live demo, write to contact@erimworks.com.


Deployment and licensing

It is enough to contact us with your clinic's name, monthly patient volume and the countries you receive patients from; your enquiry is answered with proposed times for a live demo.