Local health department infrastructure that closes the contact-tracing loop, handles outbreak surge, and disaggregates outcomes by equity domain — without buying new hardware.
Digital contact-tracing roster, STI/HIV partner-services case management, SDOH-aware harm-reduction routing, cloud-elastic outbreak surge mode, 10 Essential Services reporting, health-equity disaggregation by race and ethnicity — executed BAA chain, white-label tenant in 48 hours. Built by a clinician who watched paper rosters fail during the HIV surge and the opioid crisis at the same time.
Where the pathway breaks — and how we close it
Paper-based contact-tracing roster with no closed-loop confirmation
Most local health departments still run contact tracing on paper forms or fragmented Access databases. The investigation opens; the case worker calls the contact; the index case updates verbally; none of it closes to a documented linkage. During a routine STI caseload that gap is administrative. During an outbreak — COVID, mpox, hepatitis A among unhoused populations — it becomes a surveillance blind spot. A contact that was never confirmed as notified is a transmission event the department cannot prove it interrupted.
Cost when unaddressed: Paper rosters cannot be audited in real time. An outbreak that outpaces paper capacity defaults to reactive containment — the math works against the department from the first missed confirmation.
Digital FHIR R4 contact roster with 14-day closure tracking and outbreak surge mode
Every investigation generates a FHIR R4 Observation and a linked contact event chain. Each contact is assigned a case worker, a notification attempt is timestamped, and a closure status — notified, attempted-unreachable, declined — is recorded within 14 days. Surge mode auto-queues cases by transmission risk tier so the highest-exposure contacts are worked first regardless of staff-to-caseload ratio. The dashboard surfaces the open contact queue, the overdue queue, and the closure rate per case worker in real time.
Fragmented STI and HIV partner-services case management
STI and HIV partner-services programs in most local health departments are managed across multiple disconnected tools: a state-provided surveillance system for case reporting, a separate interview form for partner elicitation, a handwritten or spreadsheet-based partner notification log, and a follow-up call record that lives in a case worker's personal notes. When a case worker turns over — which happens frequently in public health given pay compression relative to clinical roles — the partner chain disappears with them. The CDC STD Surveillance data consistently shows that partner-services completion rates vary by three to four times across jurisdictions with comparable caseloads but different infrastructure.
Cost when unaddressed: Every unnotified partner is an untreated transmission risk. For HIV, a delayed notification is a delayed viral-load suppression opportunity — the window where treatment interrupts transmission most efficiently.
Unified STI/HIV partner-services case management with field-interview workflow and partner chain tracking
The platform provides a structured field-interview workflow that elicits and records partners against the index case, assigns each partner a case worker and a notification attempt timeline, and tracks notification status — reached, declined, unreachable — through a 30-day closure window. The partner chain is visible to supervisors in real time. State-mandated case-report fields populate in FHIR R4 and are exportable to the state surveillance system in the required format. Case-worker turnover does not erase the chain — it exists in the platform, not in a notebook.
Harm-reduction programs capacity-blind to SDOH-aware service routing
Naloxone distribution programs, syringe-service programs, and medication-assisted treatment linkage are the three evidence-based harm-reduction interventions with the strongest overdose-mortality reduction data. In most local health departments they operate as siloed programs: Narcan is distributed through a specific program, SSP operates under a separate authorization, MAT linkage is a verbal handoff to a county behavioral health provider. No system routes a participant to the right intervention based on their SDOH profile — housing status, insurance, transportation, language — at the point of contact.
Cost when unaddressed: A harm-reduction program that does not route to MAT on a SDOH-aware basis leaves the highest-risk participants in the highest-cost position. An overdose death is not a system failure in the abstract — it is a specific person who was present at a service and not matched to the next intervention.
SDOH-aware harm-reduction routing: Narcan, SSP, MAT linkage from a single intake
At participant intake, the platform screens SDOH domains — housing, transportation, insurance status, language — and routes to the intersection of harm-reduction programs available and access barriers the participant has. A participant with a housing barrier and no insurance is matched to different resources than one with stable housing and Medicaid. Narcan distribution is logged; SSP participation is tracked; MAT linkage generates a FHIR R4 ServiceRequest with a 30-day closure window to confirm the appointment was kept. The resource catalog has 691,000-plus verified entries; the routing is insurance-aware and geography-aware.
Outbreak surge capacity that exceeds paper and static infrastructure
Every local health department has a theoretical surge plan. The practice is that paper-based and on-premise-database systems do not scale with an outbreak. During COVID-19, health departments that were running contact tracing on Access databases and spreadsheets were overtaken by caseload within two to three weeks of sustained community spread. Staff-to-case ratios that were serviceable at routine STI volumes became impossibly thin at outbreak volumes — and the tools themselves became the bottleneck, not the staff.
Cost when unaddressed: A system that cannot scale is a system that fails in the exact moment the department needs it most. The harm from an inadequate outbreak response is measured in transmission events, not in paperwork inconvenience.
Cloud-elastic tenant that scales to 10× baseline without capital spend
The platform runs on AWS with auto-scaling configured per tenant. A health department at routine STI caseload and a health department at outbreak peak are running the same system — the infrastructure scales up with case volume and back down when the outbreak resolves. There is no hardware procurement cycle, no IT project, no six-month lead time. Outbreak surge mode prioritizes the contact queue by transmission risk tier so staff are working highest-priority cases when the queue exceeds normal staffing ratios. The department pays for what it uses; the surge does not require a capital budget line.
10 Essential Public Health Services performance data trapped in narrative reports
The CDC and ASTHO 10 Essential Public Health Services framework is the federal standard for evaluating local health department performance. Accreditation through the Public Health Accreditation Board, state performance contracts, and federal cooperative agreements all reference the framework. The problem is that most health departments produce performance data for the 10 Essential Services through narrative self-assessment and aggregate Excel exports — the data is not structured, not queryable, and not comparable across time periods or peer jurisdictions.
Cost when unaddressed: Performance data that cannot be structured cannot be used for grant justification, accreditation response, or peer-jurisdiction benchmarking. Narrative self-assessment is evidence of effort. Structured data is evidence of outcome.
Structured data export mapped to the 10 Essential Services framework
Case management, referral-completion, partner-notification, harm-reduction-linkage, and health-equity data are stored in structured FHIR R4 format and tagged to the relevant Essential Service domains. The export engine generates a structured report mapped to the 10 Essential Services framework on a configured cadence — quarterly for internal review, annually for accreditation submission. The report is queryable by time period, by service domain, by case type, by demographics, and by equity strata. It is not a narrative. It is data.
Community-resource directory stale and unverified for patient referral
Local health departments depend on community-based organizations for referral — food banks, housing navigation, transportation programs, harm-reduction services, mental-health linkage, re-entry services. The list of available resources is typically a PDF that was last updated eighteen months ago, a Google Sheet maintained by whoever on staff has time, or an ad-hoc referral to a 211 system that cannot confirm whether the resource has current capacity. An incorrect referral does not just fail the patient — it wastes a case-worker interaction and reduces the patient's confidence that the health department can help.
Cost when unaddressed: A stale resource listing is a broken referral. A broken referral is a patient interaction that used up trust and produced nothing.
691,000+ verified community resources with insurance-aware and geography-aware routing
The platform's resource catalog has 691,000-plus verified community resource entries, continuously updated through direct provider outreach and automated accuracy monitoring. Each resource is tagged by type, insurance accepted, geographic catchment, capacity status, language, and accessibility accommodations. Referrals from contact-tracing, partner-services, and harm-reduction workflows route automatically to resources that match the patient's actual access profile — not the generic list. Every outbound referral generates a FHIR R4 ServiceRequest with a 30-day closure window.
Health-equity tracking missing disaggregated outcomes by race, ethnicity, and SDOH domain
The COVID-19 pandemic made health-equity data disaggregation a federal reporting requirement in ways that STI and TB surveillance had not yet normalized. The reality in most local health departments is that race, ethnicity, and SDOH data is captured inconsistently at intake, is not linked across case types, and cannot be exported in a format that produces an equity report without a manual analytical project. Health Equity Accreditation through PHAB and virtually every federal cooperative agreement signed since 2022 requires disaggregated outcome data. The gap is not willingness — it is infrastructure.
Cost when unaddressed: Federal cooperative agreements increasingly require equity-disaggregated outcome reporting as a condition of continued funding. A department that cannot produce the data does not win the next grant cycle — and the populations the funding is supposed to reach do not get the services.
Disaggregated outcome reporting by race, ethnicity, and SDOH domain — built into the data model
Race, ethnicity, language, and SDOH domain data are captured as structured FHIR R4 fields at intake — not as an afterthought or a separate survey. Every outcome — contact notified, partner linked, harm-reduction referral closed, MAT appointment kept — is queryable by these strata. The equity report generates on demand or on a configured export cadence. It does not require a separate analytical project. The data is in the model from day one.
Methodology
How we measure
A contact-tracing closure counts when three conditions are met against a single contact event record within 14 days of the index case investigation opening: (1) a notification attempt is documented with a timestamp, the method used — phone, in-person, written — and the case worker assigned; (2) a contact status is recorded — notified and acknowledged, notified-refused, attempted-unreachable-with-documented-attempts, or declined-by-contact; (3) the contact event record is set to a terminal status in the FHIR R4 Observation chain. Contacts exceeding 14 days without terminal status are reported as open and excluded from the closed-loop numerator. They are not deleted. A harm-reduction routing closure counts when an outbound FHIR R4 ServiceRequest to a community-based organization has a returned status — appointment confirmed, patient declined, organization at capacity — within 30 days. SDOH domain data is captured using structured intake fields mapped to the Healthy People 2030 SDOH domain framework. Every closure, every routing event, and every SDOH record is tagged with the race, ethnicity, and language fields at the patient or participant level — disaggregated reporting is a query, not a project.
What counts
- FHIR R4 contact event record with timestamped notification attempt and assigned case worker
- Documented contact status — notified, attempted-unreachable, declined — within 14-day window
- FHIR R4 ServiceRequest for harm-reduction or SDOH referral with destination organization identifier
- Closure status — completed, declined, capacity-limited — within 30 days of issuance
- Race, ethnicity, language, and SDOH domain fields captured as structured FHIR R4 elements at intake
- STI/HIV partner chain recorded with elicitation timestamp and assigned case worker
- 10 Essential Services data tagged to service domain at time of case event creation
What doesn't count
- Verbal-only notification attempts without a timestamped record in the contact event chain
- Contact records closed after 14 days without documented attempts during the window — reported as open
- Harm-reduction referrals routed to resources outside the verified catalog without a BAA in place
- Equity-disaggregation exports generated from retrospective survey data rather than structured case records
- Partner chains recorded only in case-worker personal notes without a system record
- SDOH screens captured as free-text narrative without structured domain mapping
How we compare
Sourced from primary citations — not vendor marketing claims.
| UsHealthcareCheck (LHD) | vsIn-house Access DB / spreadsheet | vsUnite Us (community-resource routing) | vsCustom build | |
|---|---|---|---|---|
| Time-to-deploy | 48 hours (tenant config against live FHIR R4 + AWS + Vertex AI stack) | Weeks (IT department + data-migration project) | Weeks (network configuration) | 9–18 months (build + HIPAA review + state integration) |
| Contact-tracing closure tracking (14-day window)cite | Native — FHIR R4 contact chain with closure status and case-worker queue | Not designed for it — manual tracking in spreadsheets | Not the product (referral routing focus, not contact investigation) | Possible — but you build it |
| STI/HIV partner-services case managementcite | Native — structured field interview, partner chain, notification timeline, state-export format | Not designed for it | Partial — referral routing, not investigation workflow | Possible — but you build it |
| SDOH-aware harm-reduction routing (Narcan, SSP, MAT linkage)cite | Native — insurance-aware, geography-aware routing from 691K+ verified resources with 30-day closure | Not designed for it | Partial — resource routing, not harm-reduction specific + SDOH-aware | Possible — but you build it |
| Outbreak surge mode (no capital spend)cite | AWS auto-scaling per tenant — 10× baseline without hardware procurement cycle | Static — crashes at outbreak caseload volume | Not the product | Possible — but capital cycle required |
| 10 Essential Services structured export for PHAB accreditationcite | Native — case data tagged to ESS domain at creation, queryable export on configured cadence | Manual — retrospective Excel aggregation | Not the product | Possible — but you build it |
| Health-equity disaggregation (race/ethnicity/SDOH) without analytics projectcite | Native — structured FHIR R4 fields at intake; equity export on demand | Not queryable — data in spreadsheets, no structured equity strata | Partial — depends on partner data quality | Possible — but you build it |
| Executed BAA chain (subprocessor list published)cite | Published + weekly-verified (AWS, Google Cloud Vertex AI, RDS pgcrypto, SES) | IT department's responsibility — typically undocumented at subprocessor level | Vendor BAA available; subprocessor chain varies | Your responsibility to assemble |
| Built by | LCSW with fourteen years across thirteen clinical settings — not a tech founder | Your IT department + whoever updates the spreadsheet | Tech founder + healthcare advisors | Your in-house team |
Frequently asked questions
- Does the platform replace the state surveillance system or does it connect to it?
- The platform does not replace the state surveillance system. It is the navigation layer that runs alongside it. Case workers use the platform for contact-tracing workflows, partner elicitation, harm-reduction routing, and closed-loop referral tracking. The platform exports structured FHIR R4 data in the format the state surveillance system requires for case reporting — STI, HIV, hepatitis, and reportable-condition fields map to state reporting schemas rather than requiring a manual transcription. The department's case reporting obligation to the state does not change. What changes is that the contact-tracing and partner-services workflow now produces a structured artifact that can be exported, audited, and disaggregated rather than a paper form that lives in a binder.
- How does the platform handle outbreak surge without a capital infrastructure spend?
- The platform runs on AWS with auto-scaling configured per tenant. When a department's caseload triples during an outbreak — the median surge documented in the COVID-19 response data was 3.4 times baseline STI/TB capacity — the infrastructure scales with it automatically. There is no hardware procurement, no IT capital project, no six-month lead time. Outbreak surge mode activates on a case-volume threshold the department configures and prioritizes the open contact queue by transmission risk tier so the highest-exposure contacts are worked first when staff-to-caseload ratios stretch. When the outbreak resolves, the infrastructure scales back. The department pays for compute on a usage basis during the surge, not for permanent capacity that sits idle between outbreaks.
- How does the harm-reduction routing work for syringe-service program participants?
- At SSP participant intake, the platform captures SDOH fields — housing, insurance status, transportation, language, substances used — as structured data. The routing engine matches the participant to the intersection of harm-reduction services available in the department's resource catalog and the access barriers the participant has. A participant without insurance and without transportation is routed differently than a participant with Medicaid and a car. Narcan distribution is logged per participant. MAT linkage generates a FHIR R4 ServiceRequest with a 30-day closure window to confirm that the appointment was kept — not just that the referral was made. The Abdul-Quader 2013 CDC MMWR meta-analysis documented 27 percent SSP-to-MAT linkage in standard practice. Bratberg 2016 documented 48 percent with SDOH-informed navigation support. That gap — 21 percentage points — is the routing problem, not the willingness problem.
Cited:abdul-quader-2013-ssp-mat-linkage-mmwr, bratberg-2016-harm-reduction-sdoh-linkage
- What does health-equity disaggregation look like in practice, and what does it require from staff?
- Race, ethnicity, language, and SDOH domain data are captured at intake as structured FHIR R4 fields — not as a separate survey or an annual data-collection project. Because they are in the data model from the start, every outcome — contact notified, partner linked, harm-reduction referral closed, MAT appointment confirmed — is queryable by these strata at any time. The equity report is a query run on demand or configured on a cadence. It does not require a dedicated analyst, a separate data-pull request, or a manual reconciliation. What it requires from staff is structured intake — consistent capture of race, ethnicity, language, and SDOH fields at the first contact. The 61 percent of health departments that NACCHO 2021 documented as unable to routinely produce disaggregated outcome data were not lacking willingness. The data was not in a format that could be queried. This fixes the format problem at the source.
Cited:naccho-2021-lhd-profile-study, odphp-2030-sdoh-framework
- How does the BAA chain work for a local health department running PHI across contact tracing, STI case management, and harm reduction?
- The BAA chain is executed and published before the first case record is created. Mutual BAA with the health department on day one. Subprocessors: AWS for hosting, RDS PostgreSQL with pgcrypto encryption at rest, and AWS SES for transactional notifications under the existing AWS BAA; Google Cloud Vertex AI for clinical inference under the Google Cloud BAA with no-training settings enforced at the project level. The subprocessor list is published on the compliance page and is re-verified on a weekly cadence under the standing HIPAA gate. Under the 2013 HIPAA Omnibus Rule, subcontractors are directly liable to the federal government. A health department that runs contact tracing, partner services, and harm-reduction case management under one platform has one subprocessor chain to document and one BAA to execute, not three separate vendor procurement tracks to manage. The compliance page exists. The chain is not a verbal representation.
Cited:hhs-2013-omnibus-rule-baa-requirements, hhs-45-cfr-164-312-technical-safeguards, ocr-2024-hipaa-enforcement-statistics
- Can the platform support 10 Essential Public Health Services performance reporting for PHAB accreditation?
- Yes. Case-management events, referral-completion records, partner-notification outcomes, and harm-reduction-linkage data are tagged to the relevant Essential Services domains at the time of case event creation — not retroactively. The export engine generates a structured performance report mapped to the 10 Essential Services framework on a configured cadence. The report is queryable by service domain, by time period, by case type, and by equity strata. It is not a narrative self-assessment. PHAB accreditation, state performance contracts, and federal cooperative agreements that reference the framework all require structured data with a documented measurement methodology. The methodology block on this page is that documentation.
Cited:naccho-2021-lhd-profile-study, cdc-10-essential-public-health-services
Why this exists
A closed contact-tracing loop is a transmission interrupted. The infrastructure problem is not glamorous — but the math on getting it wrong is measured in lives, not paperwork.
I am a Licensed Clinical Social Worker. I have run crisis programs. I have worked in community mental health clinics that operated as de facto outpost public health departments — the people walking in the door had active STIs, active substance-use disorders, active housing crises, and were in contact with the health department for at least two of those things simultaneously. I watched the paper break. I watched the coordinator take their notebook home and the partner chain disappear with it. I watched the outbreak hit and the spreadsheet not scale.
I built HealthcareCheck for local health departments because the problem is always the same: the department has people who know what to do and does not have infrastructure that can hold what those people know. The contact investigation is tribal knowledge. The partner chain is a notebook. The harm-reduction routing is a PDF last updated eighteen months ago. The equity report is a manual analytics project that takes three weeks and does not line up with what the grant requires.
The infrastructure problem is not glamorous. Nobody gets a press release for buying the right case-management system. But a closed contact-tracing loop is a transmission interrupted. An SSP participant linked to MAT instead of just given Narcan is a life that did not end at the next overdose. A health department that can produce a disaggregated equity report on demand is a health department that wins the next federal cooperative agreement and serves the populations that agreement is designed to reach.
Patient navigation should be infrastructure a department owns — not a spreadsheet that crashes at outbreak volume, not a notebook that walks out the door when the case worker quits, not a PDF resource directory that sends patients to programs that closed last year. That is what this is built to fix.
Matthew Sexton, LCSWFounder · Mental Wealth Solutions Inc.
Citations
naccho-2021-lhd-profile-studySeecitations/naccho-2021-lhd-profile-study.mdxfor primary source, DOI/PMID, and key statistics.kahn-2021-digital-contact-tracing-outcomesSeecitations/kahn-2021-digital-contact-tracing-outcomes.mdxfor primary source, DOI/PMID, and key statistics.cdc-2022-std-surveillance-reportSeecitations/cdc-2022-std-surveillance-report.mdxfor primary source, DOI/PMID, and key statistics.cdc-2022-hiv-prevention-program-evaluationSeecitations/cdc-2022-hiv-prevention-program-evaluation.mdxfor primary source, DOI/PMID, and key statistics.abdul-quader-2013-ssp-mat-linkage-mmwrSeecitations/abdul-quader-2013-ssp-mat-linkage-mmwr.mdxfor primary source, DOI/PMID, and key statistics.bratberg-2016-harm-reduction-sdoh-linkageSeecitations/bratberg-2016-harm-reduction-sdoh-linkage.mdxfor primary source, DOI/PMID, and key statistics.leider-2020-lhd-surge-capacity-covidSeecitations/leider-2020-lhd-surge-capacity-covid.mdxfor primary source, DOI/PMID, and key statistics.cantor-2022-sdoh-resource-directory-accuracySeecitations/cantor-2022-sdoh-resource-directory-accuracy.mdxfor primary source, DOI/PMID, and key statistics.cdc-10-essential-public-health-servicesSeecitations/cdc-10-essential-public-health-services.mdxfor primary source, DOI/PMID, and key statistics.odphp-2030-sdoh-frameworkSeecitations/odphp-2030-sdoh-framework.mdxfor primary source, DOI/PMID, and key statistics.hl7-fhir-r4-2019Seecitations/hl7-fhir-r4-2019.mdxfor primary source, DOI/PMID, and key statistics.hhs-2013-omnibus-rule-baa-requirementsSeecitations/hhs-2013-omnibus-rule-baa-requirements.mdxfor primary source, DOI/PMID, and key statistics.hhs-45-cfr-164-312-technical-safeguardsSeecitations/hhs-45-cfr-164-312-technical-safeguards.mdxfor primary source, DOI/PMID, and key statistics.ocr-2024-hipaa-enforcement-statisticsSeecitations/ocr-2024-hipaa-enforcement-statistics.mdxfor primary source, DOI/PMID, and key statistics.