Notes from the register
Why a vaccine entry may be missing from your VaxLedger view
Separate search filtering, returned source data and authorized categories when investigating a missing immunization entry.
First check whether the view is filtered
A search can hide a record without removing it from the imported data. Clear the vaccine search and compare the entry count. This is the simplest way to distinguish a narrow view from an empty returned ledger.
Then identify the boundary of the imported history
The ledger only contains immunization entries returned to this application. An absent event cannot establish that a person never received a vaccine. Source availability, the selected connection and the information returned for the authorized category define what the app can display.
Use source context to frame the next question
If an expected event is absent, identify which source you expected it to come from and consult that source’s own records. VaxLedger does not search every provider automatically, create replacement entries, or combine personal recollections with imported events.
Do not turn the gap into a schedule
An incomplete ledger is a reason to clarify the documentation, not a basis for the app to recommend a dose. The software deliberately stops at history inspection and export. Future product changes should preserve a visible distinction between source events, user-added notes and any separately validated clinical workflow.
A focused FinchNode request
VaxLedger’s backend scope is limited to demographics and immunizations through FinchNode. The ledger works with that authorized response rather than treating access to one category as proof of a complete lifetime history.
Questions about this guide
Does an empty ledger mean no vaccinations were recorded anywhere?
No. It describes the information available in this app’s current returned view.
Can I type in a missing dose?
The current interface has no manual immunization-entry feature.