Building on Lithos · Part 4 of 6

Building on Lithos, Part 4: adding one clinical service at a time

Most live programs don’t need a new clinical backend. They need the one piece their current setup does badly: renewals in states their clinicians don’t cover, benefits checks done by hand, prior authorizations nobody owns. Part 4 of Building on Lithos is about adding exactly that piece and nothing else.

TL;DR

You can add clinical services to a live telehealth program one at a time, without moving patients, clinicians or your stack. On Lithos, refill renewals are follow-up encounters triggered by a care_plan.refill_due webhook, billed as completed async visits ($45 on pay-as-you-go, falling with volume). Benefits checks, prior authorization and AI care agents are usage-based add-ons with no minimums. Add first wherever your answer today is to decline the patient, then compare loaded in-house cost per unit with the per-use price.

Add the one service you’re missing

You can add clinical services to a live telehealth program one at a time. Send Lithos only the renewals in states you don’t cover, or only the prior authorizations, and keep everything else where it is. Each service is billed per use, with no setup, implementation or monthly platform fee and no minimums.

Picture a program at 1,200 encounters a month with clinicians licensed in 30 states. It declines every patient in the other 20, and prior authorizations get filed when someone has a free afternoon.

ServiceDoing it yourselfOn Lithos
Renewals in states you don’t coverLicense and staff each state, or decline the patientLicensed providers in the patient’s state; $45 per completed async visit, falling with volume
Insurance benefits checksStaff time and an eligibility tool, about $11.70 a check in our modelUsage-based add-on, per check
Prior authorizationAbout $40 of staff time each, plus appealsUsage-based add-on, per completed authorization, appeals included
Check-ins between visitsAbout 100 staff hours a month per 1,000 patientsAI care agents, usage-based
Fixed cost you take onA hire or a new vendor contract$0

A full move is a different project, covered in migrating a live patient base without a refill gap. This post is for plugging one hole.

Renewals run on one care plan and one webhook

Renewals are the most common first add: a patient moves to a state you don’t cover, and an earned renewal becomes a cancellation.

On Lithos, every encounter belongs to a care plan. The plan moves pending_review → in_review → active, or ends as ineligible or canceled. Treatment lines on an active plan carry refill_due_at. When that date passes, Lithos sends care_plan.refill_due.

For one patient:

  1. POST /v1/patients with the demographics you already hold.
  2. POST /v1/care_plans with the patient and a category such as weight_management.
  3. POST /v1/encounters with patient_id, care_plan_id, intake_form and requested_treatments. This first encounter is a full review, because a licensed provider working through Lithos needs their own clinical basis to prescribe. Schedule it before the next refill date.
  4. On encounter.completed, fetch the encounter. orders[] and patient_message are populated, and the order routes to your preferred pharmacy or a Lithos direct pharmacy partner.
  5. From then on, care_plan.refill_due is your trigger. Send a short check-in, then create the follow_up encounter.
once per patientFirst encounterfull review, before refill dateCare plan activetreatment lines · refill_due_atcare_plan.refill_duewebhook when the date passesShort check-inyour app: what changed?follow_up encounterlicensed provider reviewsencounter.completedorders[] → your pharmacynext refill_due_atevery renewal: one completed async visit · $45 on pay-as-you-go, graduated with volume
A patient’s first encounter on Lithos is a full review that sets up the care plan. Every renewal after that starts from the care_plan.refill_due webhook and runs as a short follow_up encounter on the same plan.

Webhooks are signed and arrive at least once, in no guaranteed order, so fetch the resource and keep the handler idempotent (Part 3 on event-driven webhooks has the pattern). Give one state its own screen: an encounter at escalated with patient_information_required is waiting on the patient, and an unseen pause becomes a late refill.

Renewals in uncovered states cost $45 each

Assume 1,500 active patients on monthly renewals, and 220 of them in the 20 states you don’t cover. Today those 220 are declined or lapse.

Month one is 220 first encounters at $45, or $9,900. Every month after is 220 renewals at $45, another $9,900. Medication passes through at pharmacy cost, plus a small flat fee on mail-order orders. Fixed cost added: $0.

Don’t compare $45 with your own clinicians’ cost per renewal; where they have slack, keep renewals in-house. Compare it with what those 220 patients are worth, or with licensing and staffing 20 more states.

As of late 2026, pricing is graduated by monthly volume, each band at its own rate: $45 async up to 499 visits, $40 from 500, $30 from 1,000 and $25 from 2,500. A volume commitment gets a flat rate from month one.

Benefits checks cost about $11.70 each in-house

A benefits check answers two questions before anyone prescribes: does the plan cover this medication, and what will the patient owe? You hold coverage on the insurances resource and request the check as an add-on. The result tells your flow which path to offer: branded with coverage, branded pending prior authorization, or cash-pay.

In-house, assume 20 minutes per check at $30 an hour, plus $500 a month in tooling, at 300 checks a month:

  • Staff: 100 hours × $30 = $3,000
  • Tooling: $500
  • Per check: $3,500 ÷ 300 ≈ $11.70, before supervision and rework

Put Lithos’s per-check rate next to that figure, and remember the step cost: the day volume needs a full-time hire, your fixed cost jumps.

Prior authorization costs $40 of staff time each

Prior authorization is the service most programs underestimate: after the submission come follow-ups, payer requests, denials and appeals. On Lithos it attaches to the patient, their coverage and the encounter where a licensed provider made the decision. With benefits checks, it’s how branded prescriptions such as Wegovy are supported.

Assume 45 minutes to submit and 30 more for follow-up and appeals, at $32 an hour: $40 per authorization. At 100 a month that’s 125 hours, about 0.8 of a full-time role. Billing per completed authorization turns that role into a line that grows with branded volume.

AI care agents cover the work between visits

The Lead-to-Purchase Agent recovers abandoned intakes and carts. The AI Care Coordinator runs adherence check-ins, side-effect questions and refill coordination, and escalates to a licensed provider when something needs clinical judgment. AI prepares and coordinates; a licensed provider makes every clinical decision.

Assume 1,000 active patients, each due a 6-minute monthly check-in: 100 staff hours, about $3,000. Busy teams skip some, and skipped check-ins become missed refills (the refill lapse problem). Judge the usage-based price against both.

Add first wherever you say “no” today

If this is trueAdd first
You decline patients in states your clinicians don’t coverRenewals, plus first encounters
Coverage questions stall branded intakeBenefits checks
Authorizations queue up or get abandonedPrior authorization
Patients lapse between renewals or abandon intakeAI care agents
Your clinicians are full in states you do coverOverflow encounters by state

A declined patient costs more than any per-unit price, so start there. After that, add a service only where your loaded cost per unit beats the per-use price, and run it for a month.

Engineers can wire the next service in the free sandbox while the first runs in production. Protocols and compliance review come before go-live: integrate in days, live in weeks.

Not sure which gap to start with? Send us last month’s declined-patient count and your prior-authorization backlog, and we’ll size the first service with you on a call. Book a call.

Your brand, patients and data stay yours

Patients keep paying you through your own merchant account. Every service writes to the same patient record, so a patient renewed through Lithos in one state and by your clinician in another is still one patient, and your data stays exportable. The same approach covers whole new categories in adding a second vertical without a second stack. If you’re weighing full consolidation instead, see what your vendor stack actually costs.

Lithos is licensed clinical infrastructure you can use one service at a time: renewals, overflow encounters by state, benefits checks, prior authorization and AI care agents, billed per use with no platform fee and no minimums. Build your own care experience on licensed infrastructure, and add only what’s missing. Bring your current monthly volume and we’ll price it against the graduated bands, with a plan for the first service. See adding services to a live program, or book a call.

Frequently asked questions

Can I use one Lithos service without moving my whole program?

Yes. Lithos services are usable à la carte: send only renewals, only benefits checks or prior authorizations, or only patients in certain states. There is no setup, implementation or monthly platform fee, so one service carries no fixed cost.

How do refill renewals work through the Lithos API?

Treatment lines on a patient’s care plan carry a refill_due_at date, and Lithos sends a care_plan.refill_due webhook when it passes. Your app collects a short check-in and creates a follow_up encounter on the same plan. A licensed provider reviews it, and the completed encounter carries the orders and patient message.

Can patients from my existing practice be renewed on Lithos right away?

Not as a first step. A licensed provider working through Lithos needs their own clinical basis to prescribe, so the first encounter is a full review that establishes the care plan. Schedule it ahead of the patient’s refill date; renewals after that are short follow-ups.

How are benefits checks and prior authorization priced on Lithos?

Both are usage-based add-ons with no minimums: benefits checks per check, prior authorization per completed authorization with appeals included. Rates are set on a call against your expected volume. Medication passes through at pharmacy cost, plus a small flat fee on mail-order orders.

Which clinical service should a live telehealth program add first?

Start where your in-house answer today is to decline the patient, such as renewals in states your clinicians can’t cover or prior authorizations nobody has time to file. After that, add a service only where your loaded in-house cost per unit is above the per-use price, and measure it for a month.

Get started

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.

Book a call Get sandbox access

Free to startNo setup or platform fees