Continuous Care

Close the items a visit leaves open

The same outbound engine as recall, pointed at whatever the visit left open.

After the visit
On the schedule the clinic sets
Same engine
Configured as an outbound use case
Recorded
Outcomes land against the patient

What Changes

How it goes without automation

  • Follow-up calls are the first thing dropped when the day gets busy.
  • A patient who was meant to book a review simply does not, and nobody notices.
  • Outstanding items are tracked in somebody’s head or a sticky note.
  • The gap only surfaces at the next visit, if there is one.

How it goes with Joud Health

  • Follow-ups happen on a schedule rather than when there is time.
  • A patient who needs to book is booked on the call.
  • Attempts that miss are retried rather than quietly abandoned.
  • What happened is recorded, so an unclosed item is visible.

Step By Step

Your team
The clinic defines the follow-up
What kind of visit triggers it, how long after, and what the call should say. Configured once as its own outbound use case.
Set up once
Joud Health
Due patients are picked up
On the schedule that use case is configured with, rather than on request.
Daily
Joud Health
The patient is called
A post-visit check-in, a reminder about something outstanding, or a prompt to book the review that was meant to be arranged.
Calling
Per run
Joud Health
Booked where it applies
If the follow-up needs an appointment, it is made on the call against your live schedule rather than left as an action for the patient.
On the callWrites to EMR
Joud Health
Outcome recorded either way
Reached, retried, or not reached at all. An item nobody could close stays visible instead of disappearing.
Reached · booked
Instant

What It Hands Off To

A point solution finishes its own job and stops. These workflows run on one platform and one EMR connection, so the end of one is the start of the next.

  • Outreach And Recall

    The same outbound engine and the same controls, configured as a different use case.

  • Booking

    A follow-up that needs an appointment books it on the call.

  • Referrals

    A referral that has not turned into a booked visit is exactly the kind of open item this closes.

How It Is Set Up

Trigger
Visit type and interval, configured per clinic
Engine
The same outbound system as recall
Booking
Made on the call where the follow-up needs one
Retries
Configurable ladder
Control
Stoppable per use case from the dashboard
EMR write-back
Bookings and call outcomes

Questions

Is this separate from recall?
Same machinery, different use case. Recall is about patients who are due for care; follow-ups are about what a visit left open. They are configured separately because the timing and the wording differ, but there is one outbound system underneath and one set of controls.
Are these calls covered under US calling rules?
Post-discharge and wellness follow-ups, prescription and lab-result notifications, and appointment reminders all sit inside the TCPA healthcare exemptions. As with recall, what runs is reviewed per clinic against your own patients’ consent rather than assumed.
Does it handle clinical follow-up?
No. It closes administrative loops: check-ins, prompts to book, outstanding items. Anything clinical belongs to your physician, and a call that turns clinical is routed to your team rather than answered.
More Care. Less Admin.

All of it, on one platform

JOUD Health works quietly in the background so your team is free to focus on what matters: patient care.

Request a demo