These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Public Health Surveillance
- Features
- Vaccination events
Vaccination events
Follow vaccination events through its source records and decisions.
OverviewVaccination event register×
Public Health Surveillance · Vaccination events
New
Vaccination event register
Vaccination events
| Patient | Provider | Vaccine name | Lot number | Administered at | |
|---|---|---|---|---|---|
| PTN-92081 | Vaccine 499 | L26-1333 | 13 Oct | ||
| PTN-93942 | Vaccine 269 | L26-9744 | 06 Oct | ||
| PTN-57881 | Vaccine 603 | L26-0736 | 06 Oct | ||
| PTN-33107 | Vaccine 236 | L26-8935 | 11 Oct | ||
| PTN-64175 | Vaccine 666 | L26-3426 | 07 Oct |
6 of 6 records
Vaccine 499Vaccination events · VE-51281
PatientPTN-92081
Lot numberL26-1333
Administered at13 Oct
What you can do
Work from the source record
A vaccination event records an administered dose with patient, provider, vaccine name, lot and date. The provider points to a person; the patient points to the recipient. The Licensed Clinician checks both identities, purpose-specific consent, care-team assignment and professional privilege before recording the event. Reviewers inspect the saved attribution and authority records to confirm who received and provided the dose.
For a dose given by an assigned clinician, compare the patient and provider references with the consent and current authority records. Enter the vaccine name, lot and administration date from the administration event. A Clinical Reviewer can inspect the saved dose and provider attribution. If the provider was wrong, resolve the attribution on the dose record before using it for any outside handoff.
How the work is organized
- Source. Keep patient, provider, vaccine name, lot number and administration date on the record that owns the work.
- Responsibility. Licensed Clinician starts from the relevant list and checks the linked record before acting.
- Handoff. Use the status and dates to decide what the next person should inspect.
What to agree during setup
Agree how vaccine names and lot numbers are entered and where the administration date comes from. Use the patient and provider references to check attribution. Decide which consent purpose, assignment and privilege cover administration. If doses go to an immunization registry, name the person who checks the outside response; the local dose record itself has no delivery status.
Check the handoff on an actual case
Use a patient with Signed consent and a Licensed Clinician with an Active assignment and Verified privilege. Record the patient, provider, vaccine, lot and administration date on a vaccination event. Ask a Clinical Reviewer to trace the provider through People and the relevant authority records. Repeat with an ended assignment and pause the recording. Finally, correct a wrong provider reference before preparing an outside registry handoff.
Administration date, vaccine name and lot number identify the event that the clinician recorded. The provider reference establishes who gave the dose, while the patient reference establishes who received it. Compare those links during review. When sending dose information elsewhere, use an owned connection and check the receiving system’s response separately from the saved local record.
What your team sees
- Vaccination event register — Inspect administered doses by patient, provider, lot and date.
- Signed Consents — Check purpose and date before recording a dose.
- Verified Clinical Privileges — Check the provider’s authority for the action date.
Follow the work through
Use the process walkthrough to rehearse the decision and the data model to check record links. The roles page explains the access responsibilities.
What it keeps track of
Data model- Vaccination events
- Administered vaccination doses with vaccine, lot and provider.
- Patients
- Individuals under surveillance or care, with consent status and assigned clinician.
- People
- Clinicians, coordinators, reviewers and governance staff who act in the surveillance program.
- Consents
- Purpose-specific patient consent records with version and validity window.
- Clinical privileges
- Verified professional privileges covering a clinician and effective window.
- Care team assignments
- Active care-team access assignments scoping a clinician to a patient.
Who uses it
Permissions- Licensed Clinician
- , Clinical Reviewer, Clinical Governance Administrator.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.