Skip to content

Main content

Vaccination Coverage Known Status Base Tool

Descriptive coverage with known-status and all-record denominators; not adjusted for missingness or vaccine schedule completeness.

Loading tool…

Description

Return vaccinated/known and vaccinated/all-records coverage.

Epidemiological shares depend on who or what enters each denominator. Tests, distinct people, known-status records and eligible contacts describe different populations; a ratio computed from them is not automatically population risk or an individual diagnosis.

Return vaccinated/known and vaccinated/all-records coverage.

When to use this tool

Use Vaccination Coverage Known Status Base when you need a stated surveillance or screening count summary.

How to use the tool and how it works

  1. Enter vaccinated, unvaccinated, unknown. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read knownStatus, knownCoverage, allRecordsCoverage. Use the output convention below.

Require nonnegative integer vaccination status counts and a positive known total. Return vaccinated/known and vaccinated/all-records coverage.1

Input fieldMeaning and unitsAccepted input
vaccinatedVaccinatedRequired. Safe integer; minimum 0.
unvaccinatedUnvaccinatedRequired. Safe integer; minimum 0.
unknownUnknownRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
knownStatusKnown StatusRequired. Safe integer.
knownCoverageKnown CoverageRequired. Finite number.
allRecordsCoverageAll Records CoverageRequired. Finite number.
json
{
  "input": {
    "vaccinated": 80,
    "unvaccinated": 20,
    "unknown": 25
  },
  "output": {
    "knownStatus": 100,
    "knownCoverage": 0.8,
    "allRecordsCoverage": 0.64
  }
}

Limitations and assumptions

  • Unknown status changes only the all-records denominator. Counts do not establish unique people, verified vaccination, population representativeness or an individual protection recommendation.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use the appropriate study design and verified case definitions for health interpretation. Address ascertainment, repeated records, missing status, selection and uncertainty before generalizing a descriptive proportion.

References

  1. Calculation and input contract: epidemiology/vaccination-coverage-known-status-base — tool.io

Similar or alternative tools