Why Student Health AI Agents Need Dedicated Governance
No federal regulation currently issues AI-agent-specific requirements for student health and counseling environments. Governance leaders must instead build runtime controls by mapping existing frameworks onto agentic systems. FERPA (20 U.S.C. §1232g; 34 CFR Part 99) governs education records, including most student health records, at institutions receiving federal education funding. Joint Department of Education and HHS guidance clarifies that these records are generally subject to FERPA rather than HIPAA, except where the health center operates as a HIPAA-covered healthcare component. This distinction is not resolved by a single rule. It depends on institutional structure and billing practices, which means governance design must start with a system-by-system determination of which legal framework applies before agent permissions are defined. Treating FERPA and HIPAA as interchangeable, or assuming one framework covers all student health data, creates compliance gaps at the point agents begin making tool calls against live records.
Emerging Use Cases and Their Risk Profiles
AI agents in this setting are being deployed for intake routing, appointment scheduling, triage support, and mental health screening. These functions carry materially different risk profiles. Scheduling and administrative intake routing typically touch low-sensitivity data and present limited exposure if misconfigured. Triage support and mental health screening involve clinical judgment signals and treatment-adjacent data, and in many cases trigger the FERPA health-or-safety emergency exception (34 CFR §99.36) when a student presents acute risk. Governance frameworks that treat all agent functions as equally sensitive tend to either over-restrict low-risk administrative tasks or under-restrict clinical ones. Runtime controls should instead be scoped per function, so a single agent performing both scheduling and screening operates under different permission boundaries depending on which task it is executing at a given moment.
Crisis Escalation: Where Governance Must Be Institution-Defined
No federal regulation or AI-specific standard currently defines acceptable automated crisis-escalation behavior for student mental health contexts. Existing crisis response standards, including 988 Suicide and Crisis Lifeline protocols, operate at the institutional and clinical-practice level rather than as a technical AI standard. FERPA's health-or-safety emergency exception provides the regulatory basis institutions use to permit disclosure without consent, but it does not specify how an AI agent should detect, log, or act on a crisis signal. In the absence of an external template, institutions bear direct responsibility for defining a bounded escalation pathway rather than granting an agent open-ended discretion to access or share records. This pathway should be reviewed and approved by clinical and legal stakeholders before deployment, tested against realistic scenarios, and logged with the same rigor applied to other high-sensitivity tool calls.
Key point
Crisis-escalation logic has no external regulatory template. It must be defined, reviewed, tested, and logged as an institution-owned policy, not treated as a default agent capability.