An adherence & follow-up API for digital health.
OneDose runs underneath a digital health product as infrastructure. Medication adherence tracking, structured follow-up, voice contact and clinical escalation operate against your patients and report into your product — so the capability is yours and the patient never meets a second brand.
Building this in-house is not one project. It is telephony, language coverage, escalation policy, an audit trail and a compliance posture — before the first patient is contacted.
Build versus buy, stated honestly
Adherence and follow-up look like a feature until you scope them. The visible part — reminders and check-ins — is a fortnight of work. The rest is not.
The rest is telephony that survives a real phone network, natural conversation in the languages your patients actually speak, an escalation policy a clinician will sign, an audit trail that survives a customer’s security review, and a compliance posture that holds up when a hospital procurement team asks for the BAA. Then it needs to keep working when a model changes underneath it.
That is a team and a roadmap, and it is a team and a roadmap pointed away from whatever your product is actually for.
What changes with OneDose?
Your product stays the interface
The agents run underneath and report into your system. The patient does not download a second app or meet a second brand, which is usually the thing that kills a partner integration.
The hard parts are already built
Telephony, language handling, escalation policy, the audit log and the compliance posture exist. Those are the parts that take quarters, not the reminder scheduler.
Escalation lands in your workflow
When a patient needs a human, the case goes to your clinicians in your system with the context attached — rather than into a queue on our side that you cannot see.
One audit log across the journey
Every agent action is logged and attributable, which is what your enterprise customers will ask for when they review you rather than us.
What exactly can we integrate with today?
Worth asking us directly rather than reading it off a page — and this is a deliberate answer rather than a deflection. The site does not publish an integration matrix asserting depth we have not confirmed per system and per region, because a partner scoping a build against a list that turns out to be aspirational has a much worse problem than one who asked.
Ask what is live for your stack and your region, and you will get it in writing before you commit to anything.
Where to go next
The pages below cover the mechanism in detail — what each agent does, and what it deliberately does not.
Frequently asked
- Can we run OneDose underneath our own product?
- Yes. OneDose is designed to run as infrastructure beneath a digital health product: the agents work against your patients, escalations land in your clinicians’ workflow, and the patient interacts with your brand rather than ours.
- Why not build adherence and follow-up in-house?
- The reminder scheduler is a fortnight. Telephony that survives a real phone network, natural conversation in your patients’ languages, an escalation policy a clinician will sign, an audit trail that survives a security review, and a compliance posture that holds up in hospital procurement are quarters — and they point a team away from whatever your product is actually for.
- What integrations are available?
- Integration depth varies by system and by region, and OneDose does not publish a matrix asserting depth it has not confirmed. Ask what is live for your stack and your region and we will confirm it in writing before you commit to anything.