How to check your immunization record before changing doctors

Before changing doctors, check your immunization record by making one row for each source entry you find. Copy the vaccine or record label exactly, preserve the date at the precision shown, name the source organization and document type, save the original file or image, and keep conflicts and gaps visible.

Do not turn those rows into a vaccination schedule. The handoff should help the new clinician see the evidence and decide what needs review; it should not decide whether a dose is due, missing, duplicated, valid, or appropriate.

Current-state note: This guide was verified on July 10, 2026. Immunization Information System contacts, access methods, consent, provider-reporting rules, covered populations, and data-sharing policies can change. Check the current instructions for each source and jurisdiction.

If you are moving all of your primary-care records, use what records to request before changing primary care doctors for the broader transfer. This guide owns only the immunization-record source audit.

The short answer

For every immunization entry, keep these facts separate:

• The vaccine or record label exactly as the source shows it
• The administration date and whether it is exact, month-and-year, year-only, or unknown
• The organization that supplied the record and the type of source document
• The administering organization, only when the record identifies it
• Product, dose, or lot details, only when shown
• Whether a faithful copy is preserved and where it is stored
• Whether the document's provenance and obvious file integrity were checked
• Any conflicting entry, missing field, or unresolved question
• The next source action and clinician-review status

Download the immunization-record source audit CSV. Use an entry row for each source entry, even when two rows may describe the same event. If a checked source shows no entries, use one source-check row with the record label and administration date blank. That records the search without inventing an event.

Why one vaccine list can hide several kinds of evidence

There is no single national holder of individual vaccination records. CDC's adult record guide says CDC does not keep them and points people toward records held by patients or caregivers, prior doctors and clinics, schools or colleges, previous employers including the military, and some state registries.

That means two entries with the same label can arrive through different evidence routes:

• A record from the organization that administered the vaccine
• A portal history that may have been administered there or imported from somewhere else
• A pharmacy or vaccine-clinic record
• A jurisdictional Immunization Information System record
• A school, work, military, travel, or other institutional copy
• A paper card or saved family document
• A patient or caregiver report without a source document

Do not collapse those routes into high, medium, or low confidence. A subjective score hides the reason for uncertainty. Record the observable facts instead: who supplied the artifact, what it says, whether it names the administering source, what date precision it supports, and what remains unresolved.

Build the source audit in six steps

Step 1: define the handoff, not the schedule

The task is to prepare evidence for a new doctor. It is not to determine what a person should receive.

Start with a bounded time period or source scope when possible. Examples include all records already in the current primary-care portal, pharmacy records from the last five years, or childhood records in family and school files. These are filing scopes, not clinical recommendations.

Open the CSV and create a separate entry row for every entry from every artifact. Do not begin with one merged row per vaccine name. When a checked source returns no visible entries, create a source-check row with its organization, route, result, last-checked date, and next action. Leave event fields blank, and do not treat the empty result as proof that no administration occurred.

Step 2: list possible source organizations

Check sources that could reasonably hold the record:

• Current and previous primary-care offices
• Pediatricians and other clinics that may have administered a vaccine
• Pharmacies, grocery clinics, public clinics, workplace clinics, and travel clinics
• The jurisdictional IIS where the person lives or received vaccines
• Schools, colleges, employers, occupational-health offices, and military records
• Paper cards, saved forms, baby books, and caregiver files
• Existing portal downloads, visit summaries, receipts, and messages

CDC's current IIS contacts page says CDC does not have vaccination record information. It directs people to the IIS in the current state or a state where vaccines were received, the immunization provider, or a local or state immunization program.

Record the route you checked and the date you checked it. If it returned no visible entries, preserve that fact in a source-check row. A portal login is an access surface, not proof that every source has been searched.

Step 3: copy only what the source supports

For each entry, preserve:

• The vaccine or record label exactly as written
• The administration date exactly as shown
• Date precision: exact date, month-and-year, year-only, or unknown
• The organization that supplied the record
• The source-document type, such as portal export, pharmacy PDF, IIS record, paper card, or patient report
• Whether an administering organization is identified and its name, only if explicitly shown
• Product, dose, manufacturer, or lot details, only if shown
• Whether the source itself labels the entry as reported history
• The document name, document export or retrieval date, and preserved-copy location

Mark provenance checked yes only after matching the patient, supplying organization, document context, dates, and obvious file gaps against the source artifact. That check concerns the document and its origin, not whether an administration or schedule is clinically valid. Keep copy preserved separate; a file can be saved before that check is complete.

Do not turn October 2024 into a specific day. Do not infer an administering clinic from the portal brand. Do not fill a missing product or lot number from another row that appears similar.

Step 4: keep source roles distinct

The organization that supplied the document and the organization that administered the vaccine can be different.

Provider or portal record: Preserve whether the entry appears as administered, historical, imported, or patient-reported when the source makes that distinction. If it does not, leave the administering source unknown.

Pharmacy or vaccine-clinic record: Save the provided PDF, receipt, or history and copy only the fields it contains. A message that the event was reported to an IIS does not establish that it is currently retrievable there.

Jurisdiction IIS record: Keep the jurisdiction and retrieval date attached. CDC defines an IIS as a confidential, population-based database recording doses from participating providers in a specific geographic area. CDC says IISs can help provide official copies, but that description does not establish that one IIS contains every event.

School, work, military, paper, patient, or caregiver record: Keep the source type visible. A copied form may preserve useful evidence without identifying the original administering organization. A recollection can guide a source search, but it should remain labeled as reported information.

Step 5: record conflicts without resolving them yourself

Two rows may share a vaccine label and date while differing in product, dose, administering source, or spelling. They may be duplicate copies, separate administrations, imported history, or data-entry differences. The source audit should not decide which.

Use a conflict note that states only what differs:

• Same label and date; one record names an administering pharmacy and one does not
• Same source and label; dates differ by one day
• IIS entry has an exact date; family form shows year only
• Portal lists historical vaccine; original source not shown
• Paper card image is preserved; one date is unreadable

Keep both source rows, mark clinician review as unknown, and choose a factual next action. That action may be to request the administering record, ask the source how imported history is labeled, check another jurisdiction, or bring both records to the new clinician.

For repeated requests and response states, use how to keep a missing-record log when portals are incomplete.

Step 6: stop when every gap has a disposition

The first pass is bounded when:

• Every source artifact you found has been inventoried
• Every zero-result source check has a source-check row with its date and result
• Every entry has a source organization or an explicit unknown value
• Date precision is visible instead of silently guessed
• Preserved-copy and provenance-check status are separate
• Every conflict or important missing field has a next action
• Clinician-review status remains unknown unless a specific review occurred
• Each unresolved item is either queued for follow-up or explicitly left open

Restart the audit when a new source, entry, conflict, or handoff requirement appears. Do not wait for a mythical moment when every system certifies that the list is complete.

What an IIS result can and cannot establish

An IIS is an important source, but its scope is jurisdictional. CDC's 2026 IIS policy summary says jurisdictions can differ in consent, which providers must report, which recipients or vaccine types are covered, when reporting is mandatory, and how data is shared.

Those differences matter when a record is absent. An absent IIS entry is not proof that a vaccine was never administered. It can mean the event is outside the jurisdiction, historical period, participating-provider set, covered population, reporting rule, data-sharing path, or available match.

Use the current CDC contact directory to check the relevant jurisdiction's patient-access route. Record what the returned artifact actually covers. Do not describe it as a complete lifetime record unless the source itself supports that exact scope, and keep other source documents attached.

Request a record without overclaiming HIPAA

When a clinic or pharmacy record is missing, name the record type and date range you need. The medical-record request template owns the detailed wording and follow-up process.

HHS explains that individuals generally have a right, with limited exceptions, to access requested protected health information in designated record sets maintained by or for HIPAA covered entities. HHS also says that when a covered entity does not maintain the requested information but knows where it is maintained, the covered entity must tell the individual where to direct the request.

Keep the scope clear. HIPAA does not make every school, employer, family file, app, or registry a covered entity, and it does not require an organization to create a new clinical reconciliation that it does not maintain.

Older records may require several searches

CDC cautions that source records may not remain available indefinitely. Its adult record page says high schools and colleges generally retain records for only one or two years after a student leaves and that doctors' offices maintain vaccination records for a limited number of years.

CDC's child record guidance similarly says clinics may save records for only a few years, different vaccination locations may require separate contacts, some IIS records may be incomplete, and schools may keep records briefly after a student leaves.

These are source-discovery cautions, not universal legal retention periods. Check the current policy of the actual school, clinic, employer, military office, pharmacy, or jurisdiction. Preserve a faithful copy when you receive one.

A worked source-audit example

Suppose three artifacts contain entries with a similar vaccine label.

Portal export: The entry has an exact date and is labeled historical. The portal organization supplied the record, but the administering organization is not shown. Copy preserved is yes; clinician review is unknown.

Pharmacy PDF: The entry has the same date, names the pharmacy, and includes product details. Keep it as a separate row. Mark the possible match in the conflict note; do not delete the portal row.

Family paper form: The form lists the same vaccine family with a year only. Preserve the image, set date precision to year-only, name the form as the source document, and record that the relationship to the other two entries is unresolved.

The handoff can now show the new clinician three traceable records and one explicit question. It does not claim that there was one dose or three, that any entry is clinically valid, or that anything should be repeated.

Build the new-doctor handoff

Create a small handoff from the source audit:

• A source-aware entry list with date precision visible
• A short source index naming each attached document
• Faithful copies of the most relevant portal, pharmacy, IIS, and paper records
• A conflict and gap list that avoids guessing causes
• A next-action list for records still being requested
• Questions that require source or clinician review

For the rest of the first visit, use how to prepare a health summary for a new doctor. The immunization section is one part of that summary, not a replacement for the receiving office's instructions.

Where Libby fits

Libby belongs in the organization layer. It can help keep files you obtain, source labels, partial dates, conflict notes, gaps, and a new-doctor handoff together.

This guide does not claim that Libby:

• Connects to every portal, pharmacy, IIS, or EHR
• Requests or retrieves vaccination records automatically
• Verifies that an administration occurred
• Detects duplicate doses or reconciles conflicting entries
• Interprets an immunization schedule or recommends a vaccine
• Certifies compliance for school, work, travel, immigration, or another purpose

If the first organized record is the hard part, white-glove setup provides hands-on help with files you bring and the product workflow. It is record organization and product guidance, not vaccination, medical, legal, privacy, security, or compliance advice.

Questions people ask about immunization records

Is my patient portal immunization list complete?

Do not assume it is. Preserve any labels that distinguish entries administered by that organization, historical entries, or patient-reported history. Check other sources when important dates or administering organizations are missing.

Is a state IIS record my complete lifetime record?

Do not assume it is. CDC describes IISs as jurisdictional systems populated by participating providers, and its policy summary shows that consent, reporting, covered populations, vaccine types, and sharing rules vary. Keep the jurisdiction and retrieval date with the record.

Should I delete two entries that look duplicated?

Not before source or clinician review. Keep both rows, state what matches and differs, and preserve both artifacts. Similar labels and dates do not prove that the entries describe one event.

What if I cannot find an old record?

Record which sources you checked, keep the date or source unknown, and bring the gap to the new clinician. Do not invent a date or use this article to decide whether a vaccine or test is needed.

Can a patient or caregiver recollection go in the handoff?

Yes, if it remains clearly labeled as reported information and is not presented as source documentation. Use it to guide source searches and questions.

Safety boundaries

This guide is about record organization and access preparation. It is not vaccine, medical, legal, privacy, security, school, workplace, travel, immigration, insurance, or compliance advice.

• Do not use this audit to decide whether to receive, skip, repeat, or delay a vaccine or test.
• Do not treat an absent portal or IIS entry as proof that an administration never occurred.
• Do not merge similar entries or resolve conflicting dates without preserving each source.
• Do not promote a patient or caregiver report to source documentation.
• Do not send identity documents or health information through an unconfirmed destination.
• Do not delay urgent care or time-sensitive questions while searching for records.
• Ask a qualified clinician how to handle missing, conflicting, or unclear immunization history.

References

• CDC: Staying Up to Date with Your Vaccine Records
• CDC: Contacts for IIS Immunization Records
• CDC: IIS Policy and Legislation
• CDC: IIS Frequently Asked Questions
• CDC: Keeping Track of Records
• HHS: Individuals' Right under HIPAA to Access their Health Information