The School Nurse's Filing Cabinet That Isn't Covered by HIPAA

A university health center vaccinated 4,000 students last fall. Every injection was logged, every consent form filed. A parent later called demanding those records be handled under HIPAA. The compliance officer had to explain something most people outside healthcare law don't realize: HIPAA excludes information considered education records under FERPA law.

That single exclusion confuses hospitals, school districts, and universities every single day. I've seen compliance officers at academic medical centers lose sleep over it. And if you're responsible for protecting sensitive information at any institution that educates and treats people, you need to understand exactly where the line falls.

This post breaks down the exclusion, explains why Congress drew the boundary this way, and gives you concrete guidance for handling student health information without triggering a violation on either side.

What the FERPA Exclusion Actually Says

The HIPAA Privacy Rule at 45 CFR § 160.103 defines protected health information (PHI) and then explicitly carves out records that qualify as "education records" under the Family Educational Rights and Privacy Act (FERPA), 20 U.S.C. § 1232g. If a record meets FERPA's definition of an education record, HIPAA does not apply to it — period.

FERPA defines education records broadly: any record directly related to a student and maintained by an educational institution or a party acting on its behalf. That includes immunization records held by a university registrar, counseling notes in a school's student file, and health screenings conducted by a K-12 school nurse.

The logic is straightforward. Congress didn't want two overlapping federal privacy regimes governing the same document. FERPA got there first for student records, so HIPAA steps aside.

Why This Exclusion Catches So Many Organizations Off Guard

Here's what I see in the field constantly: a campus health clinic operates like any other outpatient clinic. It has physicians, nurses, electronic health records, and billing systems. Staff assume HIPAA governs every patient encounter. And for non-student patients — faculty, visiting researchers, community members — it usually does.

But the moment that same clinic treats an enrolled student and the record becomes part of the student's education record, FERPA typically controls. The clinic might be a HIPAA covered entity and a FERPA-regulated unit simultaneously, depending on whose chart they're opening.

The Dual-Role Problem

Academic medical centers face this constantly. A teaching hospital affiliated with a university might maintain treatment records on students that fall under FERPA and treatment records on non-students that fall under HIPAA. Staff toggling between two regulatory frameworks in the same shift is a recipe for mistakes.

I've reviewed policies at three major state university health systems where the staff had zero training on the FERPA distinction. They applied HIPAA's minimum necessary standard to every record, which sounds safe — until a FERPA-authorized request comes in and they refuse to release records that FERPA actually requires them to share.

HIPAA Excludes Information Considered Education Records: A Quick-Reference Breakdown

Because this is the question people search for, here's the direct answer designed to clear up confusion fast:

  • HIPAA does not cover health information that qualifies as an education record under FERPA (20 U.S.C. § 1232g).
  • FERPA covers records directly related to a student and maintained by an educational institution or its agent.
  • HIPAA does cover health records created by a covered entity (like a hospital) that are not education records — even if the patient is a student.
  • Treatment records at postsecondary institutions have a special FERPA carve-out: they are excluded from FERPA's definition of education records under 20 U.S.C. § 1232g(a)(4)(B)(iv). These records may then fall under HIPAA if the provider is a covered entity.

That last bullet is the one that trips up even experienced compliance professionals. Postsecondary treatment records sit in a regulatory gap that demands careful analysis.

The K-12 vs. Postsecondary Split

K-12 Schools

In most K-12 settings, the school is not a HIPAA covered entity. It doesn't bill electronically for healthcare. The school nurse's records are education records under FERPA. HIPAA simply doesn't enter the picture.

But if that school contracts with an outside healthcare provider — say, a mobile dental clinic — and that provider bills Medicaid electronically, the provider is a covered entity. The records the provider maintains are likely governed by HIPAA, not FERPA, because the provider isn't the educational institution.

Colleges and Universities

Postsecondary institutions are messier. A university health center that transmits electronic claims is a covered entity under HIPAA. The treatment records it creates for students are excluded from FERPA's definition of education records — which means HIPAA does apply to them.

However, if the university registrar's office holds a copy of a student's immunization record as a condition of enrollment, that copy is an education record under FERPA. Same underlying health information, different custodian, different law.

The Department of Health and Human Services (HHS) and the Department of Education have both acknowledged this complexity. HHS published joint guidance on FERPA and HIPAA that remains the most authoritative resource for sorting through these overlaps.

Real Consequences When You Get the Boundary Wrong

Getting this wrong has teeth on both sides. FERPA violations can cost an institution its federal funding. HIPAA violations carry civil monetary penalties enforced by the Office for Civil Rights (OCR) that can reach into the millions.

In 2018, the University of Texas MD Anderson Cancer Center lost its appeal of $4.3 million in HIPAA penalties for ePHI breaches involving unencrypted devices. While that case didn't hinge on the FERPA exclusion, it demonstrated that academic medical institutions are absolutely in OCR's crosshairs. Any confusion about which records fall under HIPAA versus FERPA only increases exposure.

On the FERPA side, the Department of Education's Student Privacy Policy Office investigates complaints. Institutions that wrongly withhold records by claiming HIPAA protections — when FERPA actually governs — can face compliance actions and funding threats.

Five Steps to Get Your Organization on Solid Ground

1. Map Every Record to Its Governing Law

Inventory your student health records. For each category, determine whether the record is an education record under FERPA, a treatment record excluded from FERPA at the postsecondary level, or a standard healthcare record governed by HIPAA. Document your reasoning.

2. Train Staff on Both Frameworks

Your workforce needs to understand that HIPAA excludes information considered education records under FERPA law — and what that means in daily operations. Generic HIPAA training won't cover this. Build scenario-based modules that walk staff through real situations they'll face. Our HIPAA training catalog includes courses designed for organizations that straddle both regulatory worlds.

3. Designate a Point Person for Overlap Questions

Someone in your organization needs to be the tiebreaker when staff aren't sure which law applies to a specific record request. In my experience, this role works best when shared between your HIPAA Privacy Officer and your FERPA compliance lead.

4. Update Your Notice of Privacy Practices

If your institution is a HIPAA covered entity that also holds FERPA education records, your Notice of Privacy Practices should clearly state which records are covered by HIPAA and which are not. Ambiguity here invites complaints from patients, parents, and regulators.

5. Revisit Business Associate Agreements

Third-party vendors handling student data may need FERPA-compliant agreements instead of — or in addition to — HIPAA Business Associate Agreements. Don't assume a BAA covers everything. Audit your vendor contracts annually.

The Question Nobody Asks Until It's Too Late

Here's the scenario I dread: a data breach hits a university health center's server. The breach notification obligations under HIPAA and FERPA are different. HIPAA's Breach Notification Rule under 45 CFR Parts 160 and 164 requires notification to affected individuals, HHS, and sometimes the media within specific timeframes. FERPA has no equivalent breach notification mandate at the federal level, though state laws may impose their own requirements.

If you haven't classified your records beforehand, you'll be doing legal triage in the middle of a crisis. That's when mistakes happen — and when OCR shows up.

Stop Guessing. Start Classifying.

The boundary between HIPAA and FERPA isn't optional knowledge for anyone working in education-related healthcare. It's a core compliance requirement that affects how you store records, respond to requests, report breaches, and train your people.

If your team hasn't been trained on this distinction, now is the time. Browse our complete HIPAA training catalog for courses that address the FERPA exclusion and other critical regulatory boundaries your workforce needs to understand.

The records in your system right now are governed by one law or the other. Your job is to know which — before someone else decides for you.