Reviewing Immunization Clearance Follow-Up

Protocol status

Clearance follow-up is reviewable when each requirement has a source, each gap has an owner and a dated contact, and each closure can be traced to a reviewer decision rather than to a document upload alone.

This page describes a review design and its proposed controls. It does not report an executed sample, measured outcomes, or evidence that the controls improved performance.

Review protocol

Planned review sequence

1. Define the eligible population from a fixed extract of students subject to a declared immunization or health requirement for a term or placement cycle. Include general enrollment, clinical placement, and program-specific groups, and record the count for each. State the requirement source, the extract date, and the system used. Exclude students with a documented exemption only if the exemption is recorded in the same extract, and keep the excluded count.
2. Map each requirement to its source
3. Build the status model before examining cases. Use states such as not started, document received, under review, cleared, conditionally cleared, exempt, and expired. Define what evidence changes each state and who can change it. A binary cleared flag hides conditional and expiring clearances that matter for placement.
4. Record the required evidence for each requirement and the reviewer who decides sufficiency. Evidence may include a provider-signed record, a lab result, a prior institution's clearance, or a state registry printout. Record whether the item is present, legible, and linked to the correct student. The review does not interpret the medical content.
5. Test identity and document matching. Compare the name and identifier on the uploaded document to the student record, and flag mismatches, third-party documents, and illegible identifiers. A document that belongs to a sibling or a parent is not evidence for the student, even when it was uploaded from the student's account.
6. Measure the follow-up cadence. For each open gap, record the first contact date, the channel, the number of contacts, and the last response. Compare the cadence to the published policy. A single generic reminder at the deadline is not the same process as a scheduled sequence, and the difference should be visible in the data.
7. Separate general enrollment clearance from clinical placement clearance. Record the placement site, the start date, and any site-specific requirement. A student may be cleared for classes but not for a site, and the two statuses should not be collapsed. If a site rejects a document, record the site reason and the reviewer's response.
8. Review exemptions and deferrals without collecting the underlying explanation. Record the category, the approving office, the scope, and the review or expiry date. Check that an exemption for one requirement is not treated as a blanket clearance for another. The review should not reproduce religious or medical detail in its working file.
9. Sample by requirement, program, term, and status. Include at least one student with a late document, one with an expiring clearance, one with a conditional clearance, and one with an exemption. A sample drawn only from cleared students will not show whether the follow-up process works. If the population is small, review all cases and label the work a census.
10. Compare the tracker to the placement or enrollment record. Record students who are marked cleared in the tracker but blocked in the placement system, and the reverse. Investigate the direction of the discrepancy before assigning a cause. The tracker is a coordination tool, not automatically the authoritative source.
11. Examine closures for evidence. A closure should have a reviewer decision, a date, and a reference to the document or exemption that supported it. An upload with no review is not a closure. Sample reopened cases to see whether the new evidence was assessed or the old status was simply restored.
12. Test the link between the tracker, the secure document repository, and the placement or enrollment system before sampling. Record duplicate student rows, missing requirement keys, and clearances that exist in one system but not the other. Report the match rate. A status that cannot be linked cannot be reviewed for closure, even when the tracker looks complete.
13. Pilot the status model on one program or clinical cohort. Record the cases where received, under review, and cleared were ambiguous, and where an exemption looked like a clearance. Freeze the status definitions after the pilot and apply them to every sampled case. Keep the pilot separate so the final counts use one model.
14. Define decision rights for a disputed clearance. Name who can reopen a reviewer decision, accept a late document, or grant a temporary placement exception. Record the authority and the date. The assistant can assemble the file and the contact history, but should not clear a student because a deadline is close.
15. Review the student-facing messages for clarity and privacy. Check whether the message named the missing requirement, the deadline, the submission channel, and the office to contact. Confirm that it did not include medical detail or imply a diagnosis. If a template changed during the term, record the version and the date.
16. Set the reporting audience and cadence. A program director needs aggregate clearance counts, a clinical site needs a status confirmation, and a privacy officer needs to know where documents are stored. Report counts without names or health detail. Assign a follow-up owner and schedule the next review before the report is shared.
17. Check the requirement change log for the period. If a test, attestation, or site rule changed, record the old requirement, the new one, the effective date, and the students notified. A gap measured against a revised rule may not be a gap. Cases that cross a requirement change should be reported separately.
18. Document the sample selection record. Describe the selection method and the replacement rule in enough detail for a second reviewer to repeat it. Keep the selection file. A sample built from the students who happened to call the office will overrepresent problems and miss silent gaps.
19. Test the correction trail. For any clearance that was reopened, downgraded, or reinstated, record the original status, the new status, the reviewer, the evidence, and the date. Confirm that the placement system received the change. A tracker correction that never reaches the site is not a completed correction.
20. The review stops at documentation; it does not decide whether a student is immune, whether an exemption should be granted, or whether a clinical site must accept a clearance. Those decisions belong to the qualified office or the site. The review reports whether the follow-up and documentation can be reconstructed.
21. Report the population, the sample, the status counts, the follow-up timing, the closure evidence, and the limits. Retain the extract, the requirement map, the sampling frame, and the review notes in the approved secure location. The protocol measures follow-up and documentation; it does not measure whether a student is immune, whether a site will accept the clearance, or whether an exemption should have been granted.

Operational implications

Each requirement needs its source and effective date before student status can be interpreted.

A binary cleared flag is insufficient when clearances can be conditional or expiring.

Document receipt and reviewer approval are separate states and should be counted separately.

Identity matching is part of evidence quality because a correct document can belong to the wrong person.

Follow-up cadence should be measured from the first gap, not only from the final deadline.

General enrollment clearance and clinical placement clearance can diverge and should be tracked separately.

Exemptions need a scope and a review date so they are not treated as blanket clearance.

A site rejection should be recorded with its reason and routed to the reviewer, not handled as a resubmission loop.

A tracker and a placement system can disagree; the review should record the direction of the mismatch.

Closure requires a reviewer decision, not only an uploaded file.

The review measures follow-up and documentation, not medical status or the merits of an exemption.