Skip to main content

Diabetes Recalls: Separate HbA1c Testing, Foot Review and Clinical Follow-Up

Build diabetes recalls from the clinician's current plan, with separate due dates and completion evidence for HbA1c testing, foot review and clinical follow-up. Do not apply a universal 90-day timer to every patient or reset a clinical due date when a reminder is sent. A sample collected, a result received and a result reviewed are different events.

By Bractis · Updated · 9 min read

Indian clinics coordinating adult type 2 diabetes follow-up across doctor visits, outside laboratories, foot assessment and patient contact.

Record why the next review is due

The phrase 'HbA1c every 90 days' hides the decisions a recall register needs. The appropriate interval depends on the person's current care plan and circumstances. A patient whose treatment is changing and one with stable control may not need the same schedule.

NICE NG28, updated on 18 February 2026, recommends HbA1c measurement every three to six months, tailored to individual needs, until control is stable on unchanged therapy, and every six months once stable. This is UK adult type 2 diabetes guidance, not a universal Indian appointment rule or guidance for every diabetes population.

NIDDK explains that HbA1c reflects average glucose over roughly three months and can be affected by factors such as altered red-cell turnover and haemoglobin variants. The period reflected by a test does not itself set the date when every patient needs another test.

Store the plan's author, date, intended purpose and review trigger. If a doctor specifies a particular interval or date, the register should retain that instruction and the event from which it runs. If the plan is unclear, send a clarification task instead of inventing a default.

Pregnancy, type 1 diabetes and other specific situations require their own clinical plans. A general adult type 2 recall workflow must not silently determine their testing or follow-up.

Source: NICE NG28: Blood glucose management, 1.5.1–1.5.3; updated 18 February 2026

Source: NIDDK: The A1C Test & Diabetes

Separate the test, foot assessment and clinical review

A test appointment is an opportunity to obtain evidence; it is not proof that the evidence was reviewed. Give collection, receipt and clinical interpretation their own dates and responsible owners. If a laboratory result arrives after the consultation, the review task remains open.

Foot assessment has a different clinical purpose and risk basis. NICE NG19 recommendation 1.3.11 uses foot-risk categories to guide reassessment. Do not make a foot review automatically due only when an HbA1c result is due, or assume a blood test completes it.

New symptoms or a newly reported foot concern should reach clinical assessment through the appropriate pathway, not wait for the next routine recall. An automated calendar cannot decide whether a fresh concern is safe to defer.

Use the table to define operational evidence. The clinician determines the care, while staff can coordinate dates, identify missing documents and route unresolved tasks without independently deciding treatment or foot-risk category.

Some patients obtain tests at a local laboratory near home. Ask for the relevant dated report and reconcile it before arranging a duplicate test. A photo forwarded by a relative still needs patient attribution, report identity and a usable result for the clinician.

On a narrow screen, scroll the table horizontally to read all columns.

Different diabetes tasks need different completion evidence
TaskEvidence to retainWhat does not complete it
Plan next HbA1cClinician instruction, basis, due date or interval and responsible reviewA default timer based only on the previous reminder
Arrange testingPatient agreement and the actual collection arrangementMessage delivered without a booking or plan
Obtain resultPatient-matched report, specimen date and received dateA booking, payment receipt or an undated statement that it was done
Review resultDocumented clinician assessment and resulting planA report uploaded or marked as read by reception
Foot assessmentActual assessment and its clinician-defined next stepAn HbA1c test or generic attendance status
Contact unresolved patientOutcome, appropriate next attempt or escalation and ownerA sent reminder counted as care completed

Source: NICE NG19: Diabetic foot problems, risk-based reassessment, 1.3.11

Use a register that distinguishes tasks from patients

Consider an original register with 18 HbA1c tasks and 12 foot-review tasks. Six patients have both. There are 30 tasks across 24 distinct people: 18 + 12 − 6 = 24. Adding the task counts and calling the result '30 patients overdue' would overstate the number of people.

Now suppose the 30 tasks have these mutually exclusive operational statuses: 16 completed with the required evidence, six booked, four awaiting contact and four awaiting clarification of the clinical plan. The total remains 30. Booking does not make the six tasks complete.

Define completion for each task type before reporting a percentage. A task specifically to obtain an HbA1c report may be completed when that report is reconciled; a linked clinical-review task needs the clinician's review. Do not change the meaning midway through the month to improve the dashboard.

Keep the patient's view coherent even when the clinic has several tasks. Where clinically appropriate, coordinate visits to reduce travel or time away from work. Combining logistics does not merge the clinical requirements or make every service due at once.

Review the open list by clinical priority assigned by the responsible team, not simply by oldest reminder. A new concern, a missing important result and a routine scheduling query can require different responses.

Make each reminder part of an accountable care process

Confirm the preferred recipient, language and contact route before sending condition-specific information. For a shared phone, a neutral message inviting the patient to contact the clinic may be more appropriate than placing a diabetes label or test result on the lock screen.

Offer a practical alternative when the patient cannot use a link: a phone conversation during staffed hours, assisted booking or a paper instruction. Ask about travel, laboratory access and affordability without promising that the clinic can remove every barrier.

When a patient says the test was done elsewhere, create a report-reconciliation task rather than continuing the same reminder sequence. Record who will obtain the report and what happens if it cannot be verified. Avoid treating an unverified verbal value as a laboratory result.

Use an unsuccessful-contact status honestly. A failed message, unanswered call or wrong number does not mean the patient refused care. A refusal after an informed discussion is a different record and may still require clinician follow-through.

At the next contact, check whether a hospital visit or specialist consultation changed the plan. Preserve the older recall as superseded with its reason when appropriate; do not leave two competing instructions active simply because they came from separate screens.

Rehearse a complete cycle before sending a batch

Use fictional patients to test an unchanged plan, a changed plan, an external laboratory report and an unanswered message. The system should show why each task appears, which event establishes its due date and who is responsible for the next action.

Move the reminder date without changing the clinical plan. The care due date should not move with it. Then record a genuine new clinician instruction and verify that the superseded task no longer produces conflicting reminders.

Test the six people with both tasks in the worked register. The clinic may coordinate contact, but the system must retain each task's evidence. Completing a foot review should not automatically close a pending result review.

Inspect the end-of-day list with the covering doctor or administrator. It should identify outstanding clinical decisions separately from contact work, and provide enough context to hand over safely without opening every chart merely to discover the task's purpose.

Measure useful outcomes with clear definitions: reports reconciled, reviews actually completed and unresolved work by reason. Do not claim that reminder delivery proves better diabetes control. That would require separate clinical evidence and an appropriate evaluation.

Thirty care tasks for twenty-four people

The synthetic register contains 18 HbA1c tasks and 12 foot-review tasks, with six people in both groups. That is 30 tasks for 24 patients. Six booked tasks remain open; sending another reminder does not complete them or reset their clinical due dates.

Build a diabetes recall register

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Clinical timing
Record the current clinician instruction and the event from which its interval runs.
Separate evidence
Define completion for collection, report receipt, clinician review and foot assessment independently.
People versus tasks
Count distinct patients separately from task types and state the denominator used in each measure.
Open work
Assign ownership for external reports, failed contact, changed plans and new concerns.

Questions doctors ask

Does every adult with type 2 diabetes need HbA1c every 90 days?

No. Timing should follow the individual clinical plan. Guidance distinguishes stable control from periods of adjustment, and a test's approximate three-month look-back is not a universal recall interval.

Should foot review always happen on the HbA1c date?

Not necessarily. Foot reassessment has its own risk-based plan. Visits can be coordinated when appropriate without assuming that one service completes the other.

Should the recall date reset after a reminder is sent?

No. The reminder is a communication event. Change the clinical due date only when the relevant clinical plan or reference event supports that change.

What if the patient already tested at another laboratory?

Obtain and reconcile the patient-matched dated report for clinician review. Record uncertainty and pending retrieval rather than ordering a duplicate automatically or treating a verbal value as a verified report.

When is a diabetes recall complete?

When the evidence required for that particular task is present. A booking, report upload and clinician review are distinct milestones; the register should define and track each.

Sources and scope

Updated on . Recall coordination for adult type 2 diabetes, using dated external guidance and original register examples. The responsible clinician sets assessment, testing and treatment for the individual patient. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Build the fictional 30-task, 24-patient register. Show distinct test and foot-review states, reconcile an outside report, change a clinician plan and confirm that a sent reminder does not reset the care due date.

Request a clinic demo