Patient Recall for Indian Clinics: From Due List to Follow-Up
Manage patient recalls with clinician-defined plans, overlapping purposes, unsuccessful-contact handovers and a worked follow-up cohort.
A rabies follow-up calendar should be calculated from the documented first vaccine administration, called Day 0, using the regimen selected by the treating service. Day 0 is not automatically the bite date or booking date. Route, prior vaccination and other clinical circumstances can change the plan. Possible rabies exposure needs prompt medical assessment; a date calculator must not delay care or decide the regimen.
Indian clinics recording rabies post-exposure care, vaccine visits and handovers between the OPD and a treating anti-rabies service.
The first task after a possible rabies exposure is appropriate prompt medical assessment, not selecting a convenient vaccination slot. NCDC guidance says post-exposure prophylaxis should be started promptly when indicated. A clinic should not advise waiting for an animal to become ill or for a reminder system to confirm an appointment.
The clinical service determines the exposure assessment and the required care, including wound care and any other indicated prophylaxis. A vaccine calendar describes only one part of that plan. It cannot establish that every component was considered, supplied or completed.
If the clinic does not provide the necessary service, make the referral and its responsibility explicit. Record where the patient is directed and what information is handed over. A list of dates on a prescription is not evidence that the patient reached a treating service.
Source: NCDC: National Guidelines for Rabies Prophylaxis, 2019
Source: NCDC: Rabies, chapter 27 of the 2025 zoonotic-disease manual
NCDC’s 2025 rabies chapter defines Day 0 as the day the first vaccine dose is given. Retain that actual administration date separately from the date of animal exposure, the first clinic contact and the date the record was created.
If the first administration occurred elsewhere, seek the available vaccination record and preserve its source. A patient’s recollection can be recorded while verification continues, but it should not be displayed as a verified facility record. Do not invent a first-dose date to make a calculator run.
The distinction matters when records are entered later. A vaccination card uploaded today may describe an administration from a previous day. Using the upload date as Day 0 shifts every derived appointment and makes an apparently tidy schedule misleading.
Source: NCDC: Rabies, chapter 27 of the 2025 zoonotic-disease manual
Indian national guidance distinguishes schedules by route and clinical context, including previously vaccinated patients. The legacy title’s fixed list of five dates therefore cannot represent every patient’s plan. Record the chosen protocol, route, responsible clinician and relevant prior-vaccination evidence before creating the calendar.
The NRCP training module includes exposure details and previous vaccination history among the information collected in an animal-bite register. That history should distinguish complete, partial and uncertain information. A photograph of a card with one visible entry is not proof of a completed earlier course.
Do not treat visit count, injection count and completion of the overall care plan as the same measure. Retain the actual administration record required by the treating service. A booked visit or an automated reminder is an appointment event, not proof that vaccination took place.
Source: NCDC: National Guidelines for Rabies Prophylaxis, 2019
Source: NRCP: Training Module on Rabies for Medical Officers
In a fictional calendar exercise, assume Day 0 has been verified as 28 October 2026 and the treating clinician has already selected follow-ups at Day 3 and Day 7. Adding three calendar days gives 31 October 2026; adding seven gives 4 November 2026. These example offsets do not select a complete regimen or determine which appointments any patient needs.
Count Day 0 as zero elapsed days. Treating the first administration date as “day one” would move those calculated dates one day early. Display the full date and month rather than only a day number, especially when a course crosses months or years.
Keep intended dates separate from actual attendance and administration. If the patient attends on another day, record the actual event and obtain the clinical service’s instructions about the remaining plan. Do not silently shift every future date or mark the original appointment as completed.
Use local calendar dates for the care record. A timestamp imported from another system should not change the visible administration date merely because of a time-zone conversion. Where the original time zone is unclear, preserve the source and clarify the event rather than guessing.
This original map separates the clinical decision, the calendar and evidence of care. It is not a vaccination protocol or a substitute for an anti-rabies service’s documentation requirements.
On a narrow screen, scroll the table horizontally to read all columns.
| Record | Evidence to retain | What it cannot establish alone |
|---|---|---|
| Exposure history | Date, circumstances and clinician assessment with source | The selected regimen or completion of prophylaxis |
| Prior vaccination | Actual records, completion status and uncertainty | A complete course from one remembered injection |
| Day 0 | Verified first administration date and treating source | The bite date, booking date or upload date |
| Authorised regimen | Clinical protocol, route, reviewer and selected offsets | Suitability of the same offsets for another patient |
| Planned appointment | Derived full date and intended service | Attendance or administration |
| Actual administration | Treating-service record and actual date; product details as required | Completion of all other care components |
| Missed or changed visit | What occurred, clinical advice and revised plan | Permission for an automatic restart or blanket date shift |
Fictional patient R-36 is exposed on 23 October 2026, receives the first vaccine at an outside service on 24 October, registers with a second clinic on 25 October and uploads a clearer card on 29 October. The treating service verifies 24 October as the first administration date. The other dates remain useful history, but none replaces Day 0. The example assumes that the clinician has selected Day 3 and Day 7 for the two follow-up calculations shown; it does not specify a complete regimen.
Using 24 October gives 27 October for Day 3 and 31 October for Day 7. Using the exposure date makes both one day early. Using registration makes both one day late. Using the later upload date makes both five days late. The table exposes a data-selection error before any reminder is issued; it does not offer alternative vaccination dates or permission to delay care.
A clear outside record should also preserve the distinction between an actual administration and a scheduled date printed on the card. Ask which entry records a vaccine given, which identifies the treating facility and which is simply the next appointment. A handwritten date with no clear role is a clarification question, not a verified administration merely because it appears beside a vaccine name.
Time zones can create another one-day error. In a separate technical example, an explicitly UTC timestamp of 23 October 2026 at 19:10 corresponds to 24 October at 00:40 in India, five hours thirty minutes later. Taking the first ten characters of the UTC timestamp would choose 23 October. Conversion is appropriate only when the source timestamp and zone are known. A date-only card reading 24 October must remain a local calendar date, not be assigned a guessed time and shifted.
On a narrow screen, scroll the table horizontally to read all columns.
| Date used as the base | Calculated Day 3 | Calculated Day 7 | Finding |
|---|---|---|---|
| Exposure — 23 October 2026 | 26 October 2026 | 30 October 2026 | Rejected: one day early for this verified administration history |
| Verified first administration — 24 October 2026 | 27 October 2026 | 31 October 2026 | Correct arithmetic for the two clinician-selected offsets in this exercise |
| Clinic registration — 25 October 2026 | 28 October 2026 | 1 November 2026 | Rejected: one day late |
| Later card upload — 29 October 2026 | 1 November 2026 | 5 November 2026 | Rejected: five days late |
Source: NCDC: Rabies, chapter 27 of the 2025 zoonotic-disease manual
Continue the fictional record review: R-36’s planned 27 October visit did not produce an administration at the second clinic. An outside service later supplies a record of an actual administration on 28 October; the clearer record reaches the clinic on 29 October. The original appointment was one day before the actual administration. The upload was another day later. These intervals describe what the evidence says, not an acceptable delay or a catch-up rule.
A missed visit needs prompt contact with the treating service when it becomes known. Do not wait for a future upload date simply because this retrospective example contains one. The clinician must review the actual history and communicate the remaining plan. Keep 31 October identifiable as the original Day 7 calculation while that advice is obtained; do not present an unreviewed old reminder or a newly shifted 1 November date as the current clinical instruction.
At the 29 October review, the four rows below contain two verified administration events, one original appointment and one document-receipt event. That is not four doses. Nor does it establish course completion, because this exercise shows only selected appointments and does not assess all required care. A multi-site administration must also retain the treating service’s details rather than being counted as extra visits merely because more than one injection entry appears.
If the outside record is incomplete, state what is missing and who will clarify it: route, product or administration details, prior history, or another part of the care plan. Staff should not fill a blank from whichever regimen is the clinic software’s default. An unknown field is a visible work item; an invented value can produce a falsely confident calendar and a misleading transfer note.
On a narrow screen, scroll the table horizontally to read all columns.
| Record | Date and evidence | Event represented | Handling at the review |
|---|---|---|---|
| A0 — first administration | 24 October; treating-service evidence verified | Vaccine administration and Day 0 basis | Retain actual date and source |
| P3 — original appointment | 27 October; clinic schedule | Planned follow-up, not administration evidence | Preserve the original plan and the missed-visit account |
| A1 — outside administration | 28 October; outside record verified | Second documented administration event in this example | Retain actual date; obtain clinical advice on the remaining plan |
| U1 — card received | 29 October; upload history | Receipt of evidence about earlier care | Link the file to the events; do not create another administration |
A useful transfer request says what is known, what changed and what answer is needed. For R-36, “please continue vaccines” omits the discrepancy. The request should identify verified Day 0, the original scheduled date, the outside actual administration and the unresolved remaining plan. Attach legible relevant evidence through the agreed care channel and identify the clinician or service expected to respond.
The filled record below leaves the clinical decision pending. It is not an interim vaccination instruction. If an administration decision is due or care access is uncertain, the treating team must resolve that promptly rather than rely on a sent referral. Record whether the receiving service has accepted the handover and what the patient has been told; sending a document does not establish either.
When the response arrives, retain the original calculation and the new authorised plan as separate versions. Record which future reminders refer to the old plan, update those that are affected, and address patient copies already issued. A message can be cancelled or replaced operationally, but the clinical history must still show the dates originally planned and what was actually administered. The reviewer should not have to reconstruct that history from notification logs alone.
Check the patient explanation using full dates, the intended facility and the next action. A family member who receives the reminder should not have to decide whether “Day 7” means seven days after the bite, the first injection or the latest visit. Where a shared phone is used, confirm the appropriate recipient. A successful text delivery does not establish that the patient reached a service or that prophylaxis was completed.
For software evaluation, repeat this example with a date-only card and an explicitly zoned timestamp, then import the same outside card twice. The visible local date should be preserved correctly and duplicate copies should not create duplicate administrations. These checks assess record handling and calendar arithmetic; they do not validate clinical regimen selection or establish that Bractis provides an approved prophylaxis calculator.
If a patient misses a planned visit, contact the treating service for prompt advice and document the response. The appropriate action depends on the clinical plan and history. This article does not supply a universal grace period, catch-up sequence or restart rule.
When care transfers between facilities, send the verified administration history and current plan, not just the remaining reminder dates. Identify missing records, any unresolved questions about previous care and who has accepted responsibility for the next review.
A reminder delivered to a shared family phone does not establish that the patient attended. Agree the contact arrangement and use respectful follow-up, distinguishing no response from a confirmed missed administration. Do not mark a course complete because every scheduled notification was sent.
If another component of the prophylaxis plan remains unresolved, keep it visible alongside the vaccination schedule with a clinical owner. A completed calendar should not hide an open care task or replace assessment of a new exposure.
Complete this outline from verified records and the authorised clinical plan. It is designed for continuity and does not decide exposure category, vaccine route or eligibility for other prophylaxis. Unknown information should be sent as unknown, with a clear clarification task.
Use a fictional verified Day 0 near the end of a month and a clinician-selected set of offsets. Check each calculated date against calendar arithmetic. Then add an outside administration record uploaded later and confirm that its actual date, rather than upload time, controls the relevant history.
Mark one appointment missed. The system should preserve the original schedule and record the clinical response without inventing a new regimen. Test whether a notification success, appointment check-in or note signature can incorrectly mark an administration complete.
Evaluate Bractis against these record and calendar requirements. This article does not claim an approved rabies calculator, automatic prophylaxis selection or clinical validation of a vaccination module.
A patient brings a record showing that the first vaccine was administered on 28 October. The clinic uploads the card on 30 October. The verified administration remains Day 0; the upload date is retained as a separate event. The treating service’s approved follow-up offsets are calculated from the correct date, and a later missed appointment is routed for clinical advice instead of silently moving the entire calendar.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
Day 0 is the date the first vaccine dose is administered. Record exposure and registration dates separately and verify any administration that occurred elsewhere.
No. The treating service selects the regimen using the route and clinical context, including prior vaccination. A fixed calendar must not replace that decision.
Do not apply an automatic restart or blanket date shift. Obtain prompt advice from the treating clinical service and document the authorised plan and actual administration history.
No. Notifications, attendance, actual administrations and other required care components are different evidence. Completion needs the appropriate clinical and administration record.
Possible rabies exposure needs prompt medical assessment and indicated care. A calendar, booking delay or animal-observation assumption must not postpone that assessment.
No. Retain the verified first administration date and record the upload separately. Distinguish administered doses from appointments printed on the card, and clarify ambiguous entries with the treating service.
An explicitly zoned timestamp must be interpreted in the correct local context; a late-evening UTC time may fall on the next date in India. Preserve a date-only clinical record as a date. Do not guess a time zone or use the upload date to fill a missing administration date.
Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.
Current NCDC download route checked 29 October 2026; the document remains the 2019 edition. Relevant pages support prompt indicated care and clinical regimen selection, not a universal calculator.
Page 202, including Table 3 and its Day 0 note, inspected 29 October 2026. The article provides calendar checks, not a patient-specific prophylaxis protocol.
Current NCDC download route and Annexure 3, page 78, checked 29 October 2026 for register fields and prior-vaccination documentation. No complete manual review or independent clinical approval is claimed.
Manage patient recalls with clinician-defined plans, overlapping purposes, unsuccessful-contact handovers and a worked follow-up cohort.
Write focused clinic referral letters with an attachment manifest, patient instructions, returned-advice review and redirection history.
Trace issued prescription corrections through version history, translated copies, queued outputs and recipient-specific communication.
Verify a fictional Day 0 near month-end, import a later-uploaded outside administration and record a missed appointment without automatically changing the clinical regimen.
Request a clinic demo