Building on Lithos
Putting physician-reviewed care inside your product — integration patterns, embedded care, webhooks, agents, and what to build around the API.
Read the Series
The four integration patterns
Which integration pattern fits which team — from a fully custom patient app on the API to a forked portal template to an AI assistant ordering care — and what every pattern includes.
Read part 1Adding prescriptions to an existing app
For fitness, wellness, supplement, and women’s-health products that want to offer real treatment: the integration path from your existing user to a shipped prescription, in weeks.
Read part 2Event-driven integration with webhooks
Why polling breaks care products, the event sequence from encounter.created to order.completed, thin payloads you fetch on receipt, and the idempotent handler pattern that keeps your app and the clinical pipeline in sync.
Read part 3Adding one clinical service at a time
Refill renewals, insurance benefits checks, prior authorization and AI care agents, added one at a time to a program that already runs. The integration shape, a worked cost model per service and a rule for what to add first.
Wiring clinical events into Slack, your CRM and your support desk
Ops fan-out from clinical webhooks: which encounter, order, care plan, appointment and inquiry events belong in Slack, your CRM and your help desk, and how to keep PHI out of the places it shouldn’t be.
Give your AI assistant the ability to order care
The tool set that lets an assistant start a care request and follow it, why there is no “prescribe” tool, and how to design consent, identity and escalation so a licensed provider always decides.
Put a medical practice behind your product
Book a call and we'll scope your program together, or get free sandbox access and start building.