Integrations

What Medicolize connects to

An integration is only worth having if it removes a repeated human action. These are the ones that do: the message nobody has to type, the clearance nobody has to submit, the eligibility nobody has to look up, the image nobody has to file.

Request a demo All features

WhatsApp BusinessConfirmations, reminders, campaignsConnected

ZATCAPhase 2 clearance with QRConnected

NPHIESEligibility and claimsConnected

Google CalendarTwo-way sync per doctorConnected

Google DriveAutomatic file backupAvailable

Payment gatewaysmada, Visa, Apple PayConnected

X-ray imagingSensors and scanners write straight to the chartConnected

Public APIBuild on your clinic dataAvailable

The ones that carry messages and money

Most of the manual work in a clinic is telling someone something or taking money from them. Four connections cover almost all of it.

WhatsApp Business for confirmations, reminders and campaigns
Payment gateways for mada, Visa, Mastercard and Apple Pay
ZATCA for phase two clearance at the moment of issue
NPHIES for eligibility, pre-authorisation and claims
Google Calendar, two-way, per doctor

The ones that carry clinical work

A result that arrives as an email attachment is a result somebody has to file. These land on the record instead.

Imaging devices and scanners writing straight to the record
Laboratories, with the order raised from the visit it belongs to
Google Drive for automatic backup to storage the clinic owns
SMS providers where WhatsApp is not the right channel
Nothing landing in an inbox for someone to copy across

And the one you build yourself

A clinic group with its own systems should not be limited to what we thought of. The API is documented, versioned and the same one the product uses.

A public REST API, documented and versioned
The same endpoints the product itself runs on
Webhooks for the events you want to react to
Keys per integration, revocable without breaking the others
Rate limits published rather than discovered

Who asks about integrations

The question is usually asked by one person on behalf of another.

Owners

Whether the tools already paid for will keep working.

Clinic managers

Which manual steps actually disappear.

IT and developers

An API with documentation, keys and webhooks.

A list of logos versus a list of removed actions

Every vendor publishes an integrations page. The useful question is what stops being typed.

The way it is done now

Messages typed one at a time
Clearance submitted in a batch
Eligibility looked up in a portal
Images filed by hand
An export when you need your data

With Medicolize

Sent on a schedule the clinic sets
Cleared as the invoice is issued
Answered at the counter
Written straight to the record
A documented API

Questions

Integrations — what clinics ask

Is there a public API?

Yes — REST, documented and versioned, and it is the same API the product runs on rather than a reduced copy of it. Keys are issued per integration and can be revoked individually.

Does WhatsApp use the official Business API?

Yes. That matters because the unofficial routes get numbers banned, and a clinic’s WhatsApp number is not something it can afford to lose.

Can we connect our own imaging devices?

Sensors and scanners can write straight to the patient record rather than exporting to a folder for someone to attach afterwards. Which devices depends on what they support.

What happens to our data if we leave?

It is exportable, through the interface and through the API. We do not treat migration out as a support ticket to be slowed down.

Do integrations cost extra?

What a gateway, a laboratory or a provider charges for their own service is between you and them. Which of these are in your plan is part of the quote, so ask on the call and we will be specific about it.

Keep going

Put Integrations in front of your own week

Half an hour on your own services, packages and price list. Someone calls you back within a day.

Request a demo WhatsApp us