Description
Separate unique resident coverage from all client contacts and nonresident visits.
Public-health summaries depend on who is counted, which observations are verified, and the period and population used as the base. Shares, weighted contributions, and inventory balances describe supplied records; they do not by themselves establish a health outcome or a clinical recommendation.
Separate unique resident coverage from all client contacts and nonresident visits.
When to use this tool
Use it for health service coverage geographic denominator when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter servedResidents, localPopulation, nonresidentClients, allClients. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read residentCoverage, nonresidentShare, residentClientGap. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require positive integer localPopulation and allClients, servedResidents within localPopulation, and nonresidentClients within allClients, with resident clients at least servedResidents. Return residentCoverage, nonresidentShare, and residentClientGap.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| servedResidents | Served Residents | Required. Safe integer; minimum 0. |
| localPopulation | Local Population | Required. Safe integer; minimum 1. |
| nonresidentClients | Nonresident Clients | Required. Safe integer; minimum 0. |
| allClients | All Clients | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| residentCoverage | Resident Coverage | Required. Finite number. |
| nonresidentShare | Nonresident Share | Required. Finite number. |
| residentClientGap | Resident Client Gap | Required. Safe integer. |
{
"input": {
"servedResidents": 80,
"localPopulation": 200,
"nonresidentClients": 20,
"allClients": 110
},
"output": {
"residentCoverage": 0.4,
"nonresidentShare": 0.18181818181818182,
"residentClientGap": 10
}
}Limitations and assumptions
- AllClients and servedResidents may reflect different counting bases; the tool reports their supplied gap without deduplicating visits or establishing unique-person coverage.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For health service coverage geographic denominator, check the source records and the supplied rule before comparing the result with another method. Use an appropriately validated measurement or analysis method for clinical interpretation.
References
Similar or alternative tools
- Public Health Service Capacity Session Term
Calculate public health service capacity session term from explicit caller-supplied inputs.
- Service Coverage Boundary Weight Term
Calculate service coverage boundary weight term from explicit caller-supplied inputs.