Skip to main content

Vaccination Records: UIP, IAP, Catch-Up Plans and Due Reminders

Maintain vaccination history, the clinician-approved plan and reminders as three separate records. First reconcile the child's actual administrations across public and private services. Then identify the schedule and version used to assess what is due, including any catch-up decision. A booked appointment, paid invoice or delivered reminder is not a dose given, and an old missing entry is not proof that the child was never vaccinated.

By Bractis · Updated · 9 min read

Indian paediatric and family clinics reconciling MCP cards, private vaccine records, outside administrations and follow-up reminders.

Identify the schedule before calling a dose due

UIP programme delivery and IAP professional recommendations have different purposes and may not map one-to-one. Record the source the clinician is applying, its version and the reason for a patient-specific departure. Avoid a universal 'optional vaccine' label that substitutes a commercial category for a clinical discussion.

The IAP ACVIP recommended schedule labelled 2025 was published online on 9 April 2026 and explicitly updates the 2023 recommendations. A clinic displaying only 'latest IAP schedule' without a version cannot show whether its rules have been reviewed against that update. This article does not reproduce a complete schedule or make a recommendation about an individual vaccine.

The Ministry of Health's 2024 routine immunisation manual provides an official programme reference. Programme updates, local implementation and individual clinical circumstances still need verification. Keep a dated rule register so a later staff member can tell which guidance produced an earlier due date.

Source: IAP ACVIP: Recommended Immunization Schedule (2025), published April 2026

Source: MoHFW: Routine Immunization Manual for Health Workers, 2024

Build the history from administrations and their evidence

Ask for available source records: an MCP card, private clinic card, hospital discharge record or an identifiable digital record. Establish the child's identity before entering them. A parent may hold several siblings' cards on the same phone, and a new surname or transliteration should prompt careful matching rather than an automatic duplicate.

For each event, retain the actual administration date, vaccine or antigen information as available, product details, administering service and source. Keep dose-number labels from the original while allowing the clinician to reconcile their meaning. Two services can use different shorthand for the same kind of record.

Distinguish documented administration, parent-reported administration without a source, an appointment and an entry that cannot yet be interpreted. Do not invent a batch number for an outside dose or turn an uncertain memory into a verified administration merely to make the schedule calculate.

Combination products need careful mapping to their components and relevant formulation. A brand-name match alone does not settle validity, interchangeability or completion. Those questions belong to the vaccination clinician using appropriate current guidance.

Keep three records with different rules for completion

This original model prevents a useful reminder system from becoming an unreliable vaccination history. Each record can refer to the others, but their states should not be interchangeable.

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

History, clinical plan and reminder are different records
RecordWhat belongs hereWhat closes it
Dose historyActual event, child, date, product/antigens, source and known batch detailsAn attributable administration record; later corrections remain traceable.
Clinical planSelected schedule/version, history assessment, vaccine decision and authorised eligibility/dateA clinician's plan that can be revised when new history or circumstances emerge.
Reminder taskRecipient, suitable channel, planned contact and appointment stateThe defined contact task, without automatically creating a vaccine event.
Uncertain outside entryOriginal wording, source gap and person resolving itDocumented clarification or a clinician decision retaining the uncertainty.
Changed appointmentOriginal booking, new date and reasonA revised booking; clinical timing is separately reviewed where needed.

Treat catch-up as a clinical reconciliation task

Before calculating dates, the clinician needs an interpretable history, age, relevant clinical circumstances and the applicable current recommendations. A gap in attendance does not by itself prove that a whole series should restart. Equally, a reminder sent on time does not establish that an earlier dose was valid or given.

Keep the catch-up decision and its reasoning with the evidence used. When an outside record arrives later, review whether it changes the plan. Preserve the earlier decision rather than silently rewriting the history so it looks as though the clinic always had complete information.

Do not hard-code one minimum interval across vaccines or automatically reuse the appointment interval as an eligibility rule. Distinguish the earliest clinically permitted date, the selected planned date and the actual administration date when those concepts are used by the approved plan.

If stock availability affects a proposed visit, resolve the clinical and product question before substituting an item. Reception can explain availability and arrange review; it should not infer equivalence from price, packaging or a catalogue category. Document the clinician's authorised change and the explanation given to the family.

Make the actual visit create an accurate administration event

At the administration encounter, follow the service's approved clinical and immunisation procedures. Record what actually occurred: the child, vaccine/product, date, relevant batch and expiry details, dose/route/site as applicable, administering professional and any immediate event or observation required by the procedure.

The operational distinction is important: prescribing, billing, removing stock and administering are separate actions. If a family pays but the dose is deferred, the record should explain the deferral and preserve the financial event without inventing an administration.

The MoHFW routine immunisation manual covers programme records and immunisation practices. Use the relevant official procedure and current local arrangements for administration and adverse-event reporting. This article's outline does not train injection technique, select a vaccine or replace an AEFI response process.

Make corrections attributable. If the wrong batch was entered, preserve the original entry, corrected evidence and responsible person, and consider any affected stock or patient output. Do not solve a record error by changing the administration date to the day it was discovered.

Source: MoHFW: Routine Immunization Manual for Health Workers, 2024

Explain what is known, what is planned and what remains uncertain

Give the family a readable history and a clear next action. Use full dates, identify the child and avoid an unexplained list of abbreviations. If an outside entry remains uncertain, show that distinction instead of printing an apparently complete official-looking certificate.

Confirm who should receive reminders and what a shared-phone message may safely say. A parent who books visits is not automatically the right recipient in every family arrangement. Record the appropriate contact and communication preferences and offer a practical alternative where digital access is unreliable.

Separate the reminder's purpose from clinical advice. A message can say that the clinic wants to review the vaccination plan; it should not imply the child has received the dose, diagnose a problem or instruct an unauthorised catch-up schedule.

Ask the caregiver to explain the next step and what records to bring. If a family travels between a village service and an urban clinic, a clear portable record can be more useful than a duplicate set of automated reminders.

Document the reasoning behind the next due-list entry

Use this original outline after history reconciliation. It helps a second clinician understand why the planned date exists, particularly after a move between services or a change in the information available.

Audit due lists by children and events, not messages

Review a small sample of due-list entries against original evidence. Ask whether each has an identifiable child, an authorised plan and a reliable administration history. A hundred sent messages can represent repeated attempts for a few families; it is not a vaccination-coverage figure.

Keep declined, deferred, attended elsewhere, unreachable and clinically revised plans distinguishable. These states need different responses. Do not erase overdue history merely by issuing a later reminder, and do not mark an outside vaccination verified without the evidence or clinician decision used.

Test any software update against fictional histories that cross public/private services, contain combination products or arrive out of sequence. A rules update should be reviewable and should not quietly rewrite earlier clinical decisions. Ask the vendor to identify exactly which schedule data and verification process the configured product supports.

Fictional example: six uploaded pages, four administration events

A parent supplies six images: three pages documenting three administrations, a second photograph of one of those pages, an appointment card and a record of a fourth administration at another service. There are four documented administration events to reconcile, not six. The appointment creates no additional event, and the duplicate image adds no dose. The clinician then determines how the four events fit the child's current plan. Counting photographs or invoices would inflate the history before any catch-up calculation begins.

Vaccination History and Due-List Worksheet

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

History evidence
Which administrations are documented, reported, duplicated or still uncertain, and what source supports each?
Guidance version
Which programme or professional recommendation and version does the clinician's plan use?
Timing basis
Are eligibility, planned appointment and actual administration dates distinct and explainable?
Reminder outcome
What happened after contact, and did a verified administration or revised clinical plan result?

Questions doctors ask

Should UIP and IAP records be treated as identical schedules?

Keep their source and purpose visible. The clinician must reconcile actual administrations and apply appropriate current guidance. Do not assume that matching dose numbers or catalogue labels establishes equivalence.

Which IAP update was checked for this guide?

The IAP ACVIP recommendations labelled 2025, published online on 9 April 2026, were checked. They update the 2023 recommendations. This guide does not reproduce the complete schedule or replace patient-specific vaccination advice.

Does a lost card mean no vaccines were given?

No. Record the available account and seek appropriate source evidence. Keep uncertainty visible while the clinician decides the plan. Do not fabricate dates or automatically mark the child unvaccinated.

Can sending a vaccine reminder mark the dose complete?

No. A reminder is a communication event. An appointment, payment and actual administration are separate events. The vaccination history needs an attributable administration record.

What if an outside vaccination record arrives after a catch-up plan?

Preserve the new source and ask the responsible clinician to reconcile it with the earlier history and plan. Record any revised decision. Do not quietly insert the event and let software issue changed clinical instructions without review.

Sources and scope

Updated on . The history model, reconciliation example and handover outline are original. They do not select vaccines, determine catch-up validity, authorise administration or certify a vaccination record. No independent clinical or legal review is claimed.

Try the workflow
with Bractis.

Request a demonstration with an invented child who has a public card, a private combination-product entry, a duplicate image and a late outside record. Verify history, clinician-approved planning and reminder states separately.

Request a clinic demo