Vaccination Records: UIP, IAP, Catch-Up Plans and Due Reminders
Reconcile public and private vaccination records, identify the schedule version and keep verified administrations separate from catch-up plans and appointment reminders.
Issue a vaccination summary that states which administrations are supported by clinic records, which come from identifiable outside documents and which remain reported or uncertain. Preserve the child's identity, vaccine details, actual administration dates and the version issued. A clinic summary, a programme certificate and a destination-specific travel document may serve different purposes; confirm what the recipient requires before certifying completion.
Indian paediatric and family clinics preparing immunisation histories for parents, schools, another healthcare provider or travel-related requests.
Start with the child's identifying details and the relationship between the available records. Shared family phones can hold siblings' cards, and a spelling or surname change may need explanation. Resolve identity through the clinic's authorised process before combining events.
For each administration, retain what the source actually establishes: vaccine or product information, date, administering service and any available batch or dose label. Missing details should remain missing until verified; do not invent a batch number or infer an exact date from the child's age.
A parent-reported event can be recorded as reported history with appropriate attribution. It should not acquire the same status as a verified clinic administration just because it is placed in the same chronological table.
Keep a link or reference to the evidence used for the issued summary. That allows a later clinician to examine an ambiguous abbreviation or an amended outside record without depending entirely on the transcription.
On a narrow screen, scroll the table horizontally to read all columns.
| Evidence held | How to describe it | What needs separate judgment |
|---|---|---|
| Clinic administration record | Administered by this service, with the recorded details. | Any later correction or missing administration detail. |
| Identifiable outside card or certificate | Transcribed from the named source. | Clinical interpretation and acceptance for the recipient's purpose. |
| Parent or caregiver report | Reported administration with source and uncertainty. | Verification and any clinician-approved catch-up assessment. |
| Appointment or invoice only | Booking or payment evidence. | Whether administration actually occurred. |
| Unreadable or conflicting documents | Unresolved discrepancy linked to the sources. | Which fact can responsibly be attested. |
MoHFW's November 2024 U-WIN description covers digitised vaccination records under the Universal Immunisation Programme and QR-based certificates. That establishes the programme's purpose. It does not prove that every private vaccine administered to a child is present in one programme record.
A clinic may need to reconcile a programme certificate, an MCP card, private clinic records and documents from another location. Preserve their issuer and source instead of replacing them with an apparently universal clinic certificate.
A QR code is a route to particular information or verification; its presence alone does not establish the truth of every handwritten addition or the recipient's acceptance of the document. Check what the code actually resolves to through the legitimate verification process.
Likewise, ABHA linkage is separate from vaccination validity and destination requirements. An identity link should not be presented as an independent clinical endorsement of the schedule or a guarantee that all administrations are available.
Source: MoHFW/PIB: U-WIN vaccination records and certificates
An ordered list of dates is a history. Deciding whether a child has completed a relevant schedule or needs catch-up is a clinical task that depends on the applicable guidance and individual circumstances. Keep that assessment distinct from the transcription work.
State the schedule or recipient requirement used when making a completion statement. Avoid an undated 'fully vaccinated' label that could be read as satisfying every programme, age group and travel requirement.
A combination product may cover several antigens, while two differently labelled entries may refer to the same administration. The clinician needs adequate product and source information to interpret them. The summary should not automatically count a label as an additional dose.
When evidence is uncertain, describe the uncertainty and route the clinical question appropriately. The administrative desire for a completed school form should not force staff to fill gaps with guessed dates or a blanket completion declaration.
A fictional family brings a clinic record, a photographed outside card and an invoice. The clinic record supports one administration on 4 August. The outside card appears to show another on 18 September, but the year is cropped. The invoice shows a vaccine purchase on 20 September without administration evidence.
The clinic can issue a summary of the confirmed local event and a clearly attributed outside entry whose date remains unresolved. It requests a complete source image through the appropriate route. The purchase is retained as supporting administrative material rather than counted as a dose.
When the full card arrives, it shows that the apparent second entry is a copy of an earlier administration in another year. The clinic reconciles the history before making a completion assessment. It does not treat the newer upload time as the vaccination date.
If a summary was already issued, the correction needs a new version and an appropriate communication step. Quietly changing the current chart does not explain the difference between the parent's two copies.
The document should identify the patient, issuing clinic, responsible author and issue date, then distinguish local administrations from external or reported evidence. Include the relevant source notes and any limitations that change how the recipient should interpret it.
Keep the issue date separate from administration dates. A document produced today may describe events from several years earlier. A reprint should not make those events appear newly administered or imply that a new clinical assessment occurred.
Use the identifiers needed for matching and the recipient's legitimate purpose. Avoid adding unrelated diagnoses, full visit notes or unnecessary family information merely because the export can include them. Verify the authorised recipient and delivery route, especially on shared phones.
Where the record contains regional-language entries, preserve the source and use an appropriate reviewed interpretation. A machine-translated vaccine label should not silently become a clinician-certified product identity.
Keep a record of what was issued, to whom and from which source version. This is useful when an outside administration is corrected or a parent asks for another copy. A document history should distinguish a duplicate copy from a revised summary.
If the underlying clinical interpretation changes, preserve the reason and appropriate approval. A clerical date correction and a revised completion assessment are different events; each may require a different explanation to the recipient.
Test retrieval after a doctor leaves, the child changes surname or the clinic migrates software. The record should remain intelligible without relying on the original operator's memory. Export evidence needs to include the history and its provenance, not only a green completion badge.
Use a fictional issuance case for staff training and software evaluation. A successful template demonstration establishes document behaviour only; it does not verify a real child's immunisation status.
A fictional clinic prints a school summary in June and supplies another copy in October. The October copy incorrectly replaces each administration date with the new print date. Review restores the historical dates, labels the issue or reprint information separately and checks the full export. The event history and the document's production history now answer different questions clearly.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
An invoice establishes a financial event, not necessarily administration. Seek the relevant clinical record and retain any uncertainty rather than automatically counting a paid item as a dose.
Do not assume that. The cited programme description concerns UIP records. Reconcile the actual documents available and preserve the source of private or outside administrations.
No. The recipient may require a particular official document, authorised issuer or current destination-specific evidence. Verify those requirements separately; a general summary does not establish universal acceptance.
Do not present an estimate as a verified administration date. Retain the source limitation, seek clarification and refer any clinical interpretation to the responsible clinician.
A completion statement needs a defined schedule or requirement, relevant date and appropriate clinical basis. An unqualified label can be misunderstood as applying to every programme and purpose.
Updated on . This is guidance on evidence and document issuance. It does not prescribe a vaccine schedule, establish an individual child's status or replace official school, programme or travel requirements. No independent clinical or legal review is claimed.
November 2024 programme description covering UIP records and QR-based certificates. It does not establish that every private vaccination is recorded or accepted for every travel purpose.
Reconcile public and private vaccination records, identify the schedule version and keep verified administrations separate from catch-up plans and appointment reminders.
Evaluate prescription signing with a versioned request timeline, export evidence checks and an exception record for uncertain signing responses.
Specify an EMR export manifest, preserve clinical meaning, test FHIR claims and reconcile attachment defects before accepting clinic data portability.
Assemble a fictional history from a clinic record, an outside card and an invoice. Produce a source-labelled summary, reprint it and correct one entry while preserving the issued-version history.
Request a clinic demo