Extend healthcare beyond the point of interaction.
A visit ends. The care pathway does not. This module is in development — this page describes what we are building, and names what exists today.
What happens after the person leaves.
The interaction is recorded
Whatever happened at the counter — a dispensation, a screening, a referral — is a fact the pathway can build on.
A reminder is scheduled
Treatment courses and follow-up visits fail on memory more than on money. A message at the right moment is the cheapest intervention available.
The channel adapts
Where data connectivity is unreliable, SMS carries what an app cannot.
The loop closes at the pharmacy
The person comes back to a point of care that already knows why.
Where this actually stands.
One proof of concept and a module under construction. Nothing here is integrable today, and we would rather write that on the page than in a follow-up email.
- In development
Patient engagement
Reminders, follow-up and referral messaging that extend care beyond the point of interaction. In development — there is no public API for it today.
Being built. Not available to integrate today.
- In development
SMS relay (proof of concept)
An SMS path to reach patients and pharmacy staff where data connectivity is unreliable. Explicitly a proof of concept, not a product.
Being built. Not available to integrate today.
What it would be used for.
Treatment adherence
Reminders across a course of treatment, sent from the pharmacy that dispensed it.
Screening follow-up
Following up on a referral instead of hoping it happened.
Stock and availability notices
Telling someone their product is back, rather than making them come to find out.
Public health messaging
Reaching a network of pharmacies at once, when a campaign needs a last mile.
Written in the conditional on purpose: none of these four is a shipped feature.
Tell us what you would need first.
This module is being designed now. Partners who describe a real pathway shape what gets built first.