Followups That Actually Happen: Cut No-Shows, Increase Repeat Visits

Indian clinics have a followup problem.

You see a diabetic patient on May 15. Their HbA1c is 7.2. You tell them "come back in 3 months for repeat testing." They nod. They leave.

October arrives. You haven't seen them. December arrives. Still nothing. You assume they've switched doctors.

Then in February, they walk in. HbA1c is 9.8. They forgot about the followup. They don't feel sick. Without proper reminders, they assumed they were "fine." Now they're back, but with significant damage that could've been prevented.

According to WHO's SAGE2 study, the average medication adherence rate for Indian patients with chronic conditions is just 51%. For hypertension, real-world adherence is as low as 15.8%. A huge driver of these numbers: missed followups.

Here's how DRP-OS handles followups properly.

The followup system

DRP-OS treats every followup as a tracked entity in clinic_followups. Each followup has:

• patient_id — who needs to come back
• doctor_id — which doctor (in multi-doctor practices)
• visit_id — which visit this followup was set from
• due_date — when they should return
• reason — short note: "HbA1c review", "BP check", "Suture removal"
• notes — longer internal note for the doctor
• status — pending / done / skipped
• reminded_at — when they were last reminded
• completed_at — when they actually came back
• completed_visit_id — which visit fulfilled this followup

When you finalize a visit, you can add a followup with one click: "Followup in 14 days for suture removal." The system creates the entry.

Three views every doctor should check daily

1. Due Today

Patients whose followup date is today. You expect them. If they don't arrive by closing time, send a reminder.

2. Overdue (most important)

Patients whose followup date has passed but they haven't returned. This is your win-back queue.

DRP-OS auto-flags overdue followups. The system computes:

overdue = (status === 'pending' AND due_date < today)

The status column in the followups list shows these in a warning color, distinct from on-time pending.

3. Upcoming (next 14 days)

Patients due in the next 2 weeks. Useful for proactive outreach — "send WhatsApp 2 days before due date asking if they need to confirm/reschedule."

Why "skipped" matters as much as "done"

The status enum has three values:

• pending — followup is open, patient hasn't come yet
• done — patient came back, followup completed (linked to completed_visit_id)
• skipped — explicitly marked as not needed anymore

"Skipped" exists because sometimes followups become moot. Patient called and said "doctor, my fever is gone, I don't need to come." You mark it skipped, not done. That preserves the data accurately for analytics: "what % of pending followups were skipped vs done vs went overdue?"

This distinction matters because:

• "Skipped" patients aren't lost — they just resolved differently
• "Overdue" patients ARE lost (or at risk) — these need outreach
• Tracking the ratio reveals patient engagement health

Realistic followup compliance rates

Without a system: 30-45% of doctor-recommended followups actually happen. Patients forget, get busy, assume they're fine.

With a tracking system + manual reminder (call/WhatsApp 2 days before due): 60-75% compliance.

With proactive reminders + easy rescheduling: 75-85% compliance.

That difference — going from 35% to 75% — means twice as many followup visits. For a clinic with 200 active patients and 50% needing followups, that's ~80 additional visits a year. At an average revenue of ₹800/visit, that's ₹64,000 in recovered revenue annually. Plus the patient outcomes are dramatically better.

Followup-driven visit creation

When a patient comes back for a followup, the workflow is:

1. Open the patient's record
2. See their pending followup at the top
3. Click "Start visit from this followup"
4. System creates a new visit, pre-populated with the followup reason as the initial diagnosis
5. You finalize the visit
6. System auto-marks the followup as "done" and stores the completed_visit_id

This means your followup data is always accurate. You can run reports later: "Of all followups in 2026, what percent were completed within their due window?"

Reason-based followups

The reason field is free-form, but smart clinics standardize it. Common Indian clinic followup reasons:

• HbA1c check — every 3 months for diabetes
• BP review — every 1-3 months for hypertension
• Lipid profile — every 6-12 months
• Suture removal — typically 7-14 days post-surgery
• Wound check — varies by injury
• Medication review — for chronic patients on multiple drugs
• Vaccine booster — per schedule
• Pregnancy followup — varies by trimester
• Post-op check — typically 7 days, 30 days, 90 days

Standardizing reasons lets you run analytics later: "Are my diabetic patients keeping their 3-month followups?"

Followup vs appointment — they're different

This trips up many clinic owners. They use "appointment" and "followup" interchangeably. In DRP-OS they're separate:

• Appointment — a scheduled time slot. May be a new consultation, may be a followup, may be a routine checkup. Visible in the doctor's calendar.
• Followup — a clinical reason to return, with a target date but no fixed time. Patient may or may not have an actual appointment booked yet.

A patient might have a pending followup (due Dec 15) but no appointment yet. When they call to book, you create an appointment AND link it to the followup. When they show up, the followup is marked complete.

This separation matters because you can:

• Track followups separately from calendar slots
• Send "your followup is due — please book a time" reminders without already having a scheduled slot
• Report on followup compliance independent of appointment scheduling

Try it

The followup system is included in DRP-OS Clinic from the starter plan (₹1,499/month). It works with patient lifetime value tracking, so you can see followup compliance correlate with patient revenue.

Start your 24-hour free trial. WhatsApp +91 9560793054 for setup tips.