Active Illness Cross-Referencing System

Connect the dots.
Intervene where it counts.

WellRoster cross-references student illness reports against class schedules, bus routes, and activity rosters — identifying shared exposures while illness is active. When the contagious window closes, student data is removed. WellRoster is not a charting tool. Clinical records belong in your EHR. This is the cross-referencing layer your health team needs to act fast.

60 min
Idle session auto-logout
6
Role tiers, fully scoped
Auto-Purge
Data removed when illness resolves
Zero
Cross-district data leakage

The right cross-reference, to the right people, at the right time

WellRoster replaces manual lookups and phone trees with automated cross-referencing — connecting each illness report to every shared classroom, bus, and activity while the case is active.

Instant Cross-Referencing on Every Report

The moment a student illness is reported, WellRoster automatically cross-references it against class schedules, bus assignments, and activity rosters — giving your team a live picture of shared exposure before the end of the school day. No manual lookups. No phone trees.

  • Real-time active case counts by condition and school
  • Automatic threshold alerts when case counts exceed configurable levels
  • Transmission chain with venue-type color coding — see whether spread is driven by classrooms, buses, or activities
  • Ranked venue hotspot table identifies the highest-priority intervention targets
📈

Know Where to Intervene, Not Just Who Is Ill

When an outbreak grows, the critical question isn't just who is sick — it's where are they connecting? WellRoster surfaces which specific classrooms, bus runs, and clubs are driving transmission, so interventions are targeted rather than broad.

  • Per-condition class and period breakdown with confirmed vs. suspected counts
  • Bus route cross-referencing across all schools in a district
  • Activity and club enrollment overlap identified alongside classroom exposure
  • Estimated infection-free dates so return-to-school decisions are data-driven
👥

Purpose-Built Roles, Not a General Records System

WellRoster is designed for a specific, time-limited task — not as a general health record or charting system. Each role sees only what the active cross-referencing workflow requires, and student data is removed automatically once illness resolves.

  • School health staff see active exposure cross-references for their school only
  • District administrators see anonymized cross-school trend data — no student PII
  • Health authority staff configure outbreak conditions and monitor thresholds
  • Student records purged after the contagious window — no long-term retention
Not a Charting System

WellRoster tracks active illness only — and removes data when it's over.

Clinical charting and longitudinal student health records belong in your school's dedicated EHR or health management system. WellRoster operates in the window between illness reported and student cleared to return. Once the contagious period ends, student records are purged from the system. What remains is anonymized aggregate data for public health trend analysis — never individual identifiers. If you need a system to chart visits or maintain ongoing health histories, WellRoster is the wrong tool. If you need to know which bus, classroom, or club is driving an active outbreak — this is exactly the right one.

From illness report to cross-referenced exposure map in seconds

A streamlined workflow cross-references each report against every shared venue — giving health teams the specific, actionable picture they need to intervene before a cluster grows.

Active Cases — Lincoln Elementary
🩺 Influenza A
7 active 2 suspected
🩺 COVID-19
3 suspected
Exposed Classes — Influenza A
Period 2 — Ms. Chen 4 cases
Bus 14 — AM Route 3 cases
Soccer — Varsity 2 cases
Infection-free date May 3

Every shared venue, surfaced automatically

The moment a student illness is reported, WellRoster cross-references it against the student's class schedule, bus assignments, and activity enrollments. Health staff immediately see which classrooms, buses, and clubs carry active exposure risk — nothing manual required.

🏫

Classroom cross-referencing

Every period and teacher with shared exposure is identified, with case counts split by confirmed and suspected status.

🚌

Bus route cross-referencing

Bus routes serving multiple schools are flagged when ill students share a run, preventing silent spread between campuses.

🎾

Activity and club cross-referencing

Sports teams, clubs, and after-school programs are checked so exposures outside the classroom aren't missed.

📈

Venue hotspot identification

The transmission chain graph color-codes each connection by venue type and ranks all venues by link count — so your team knows exactly where to intervene first.

District Overview — Riverside USD
🏫 Lincoln Elementary
9 active Influenza A
🏫 Jefferson Middle
2 active
🏫 Riverside High No active cases
Illness Trends — School Year
Peak week Jan 13 — 14 cases
Most reported Influenza A

District-wide oversight — anonymized by design

District administrators and health authority staff see aggregate summaries across every school — no individual student information is visible at the district level. Because WellRoster is not a charting system, individual student records exist only at the school level and only during the active illness window. Once resolved, they are gone.

📊

Multi-year trend analysis

Week-by-week and month-by-month case counts by condition — anonymized data retained after student records are purged, supporting long-term public health analysis.

🏛

Health authority integration

Local health authorities configure reportable conditions and outbreak thresholds that automatically apply to every school in the district.

🗑

Active-window data lifecycle

Student PII exists only while illness is active. Once the contagious window closes, the record is removed — no lingering data, no unnecessary retention risk.

Every stakeholder sees exactly what they need

Access is scoped by role and organizational unit. A health aide at one school cannot view cross-reference data from another school. District staff see anonymized aggregates only. No role has broader access than its active-window cross-referencing function requires.

🏛

Health Authority Staff

Scope: Health Authority
  • Manage reportable conditions and pathogen types
  • Configure outbreak threshold rules by case count and scope
  • No access to case data, illness reports, or student records
🏯

District Administrator

Scope: School District
  • Manage user accounts across all district schools
  • View district-wide illness overviews and trends
  • Manage bus fleet and route assignments
📊

District Health Staff

Scope: School District
  • View district-wide illness trends and anonymized data
  • Monitor outbreak thresholds across all schools
  • No access to individual student records
🏫

School Administrator

Scope: Individual School
  • Manage staff, schedules, and user accounts for their school
  • View full active case reports and contact tracing data
  • Access illness trend history for their school
🩺

School Health Staff

Scope: Individual School
  • Submit student illness reports to trigger cross-referencing
  • View active exposure cross-references: classrooms, buses, and activities
  • See estimated return dates — scoped strictly to their assigned school
🚌

Transportation Staff

Scope: School District
  • Manage bus fleet and route numbers
  • No access to student health records or illness data
  • Assigned only the minimum access their role requires

HIPAA and FERPA — built in, not bolted on

Because WellRoster handles student health data during the active illness window, it is designed from the ground up to satisfy both FERPA's student record protections and HIPAA's health information requirements — not retrofitted after deployment.

FERPA § 99.31

Legitimate Educational Interest Enforcement

FERPA permits disclosure of education records only to school officials with a legitimate educational interest. WellRoster enforces this technically — every request is evaluated against the user's assigned role and organizational scope before any data is returned.

Six distinct roles, each with strictly defined data access Role scope tied to specific school, district, or authority — not system-wide Access permissions evaluated server-side on every page request Role expiry dates supported for temporary or rotating staff
FERPA § 99.36

Data Minimization by Design

District-level and health authority staff see only anonymized aggregate counts — never individual student names or identifiers. Individual student records are visible only to school-level staff with a direct operational need.

District overview and trend reports contain no student PII Anonymized illness statistics retained after student records are purged Transportation staff have zero access to health or identity data Built-in data purge tool removes student PII on a defined lifecycle
Technical Safeguards

Strong Authentication & Access Controls

Unauthorized access is the leading cause of student data breaches. WellRoster supports three authentication methods — including phishing-resistant passkeys — and enforces protective policies that significantly reduce credential compromise risk.

Password login with bcrypt hashing — never stored in plaintext Time-based one-time password (TOTP) two-factor authentication FIDO2 passkey and hardware security key support — fully phishing-resistant Account lockout after 5 failed attempts — 15-minute hold
Technical Safeguards

Session & Transmission Security

Shared workstations are a common reality in school offices. WellRoster enforces session policies designed specifically for shared-computer environments, and all data is protected in transit.

Automatic logout after 60 minutes of inactivity Session cookies flagged Secure — never transmitted over plain HTTP HttpOnly cookie flag — inaccessible to browser scripts SameSite=Strict policy prevents cross-site session hijacking Server-side session revocation on logout — tokens cannot be replayed
Data Integrity

Protection Against Unauthorized Modification

Illness records must be trustworthy. WellRoster uses parameterized database queries throughout, eliminating SQL injection as an attack vector, and validates all input at the server before any data is written.

100% parameterized SQL queries — no injection attack surface CSRF tokens on all state-changing forms Strict PHP type enforcement throughout the codebase Input validation at all system boundaries
FERPA § 99.32 · HIPAA

Tamper-Evident Audit Trail

FERPA § 99.32 requires schools to maintain a record of every access to and disclosure from student education records. WellRoster logs every significant action across all roles — who accessed what, when, and from where — verified against a completed 30-point HIPAA/FERPA audit with all findings resolved.

Every illness report submitted or updated is recorded with the acting user's identity All report views logged with timestamp, IP address, and school scope Audit records reference entity IDs only — no student PII stored in the log District and system administrators can filter and search the full audit trail
HIPAA · Encryption at Rest

Database Encryption at Rest

HIPAA requires that protected health information be encrypted wherever it is stored. WellRoster satisfies this at the infrastructure level — the entire database tier is encrypted using MySQL InnoDB tablespace encryption, meaning data is protected on disk regardless of how the underlying storage is accessed.

InnoDB tablespace encryption enabled — all tables encrypted at rest Encryption applied at the storage engine level, not the application layer Protects against data exposure from physical media access or storage-level breaches Complements in-transit TLS encryption for end-to-end data protection
Data Lifecycle

Student Record Lifecycle Management

Retaining student PII longer than necessary creates unnecessary FERPA exposure. WellRoster provides tools to remove student records once they are no longer operationally required while preserving de-identified public health statistics.

Purge tool removes student PII outside the active contagious window All related records (schedules, bus, activities) removed in a single operation Anonymized illness_stats table preserves aggregate data with no PII System admin-only access to the purge function

Ready to cross-reference illness the right way?

Get your team set up with a cross-referencing system built for active school health workflows — not long-term charting. Fast to deploy, easy to use, and designed to meet your HIPAA and FERPA obligations.

🔐  Sign In to Your District