From the College Athletics edition of September 29, 2026
UF Athletics Databank: IRB-governed HiPerGator platform claims HIPAA/FERPA/HITRUST for collegiate AI research
University of Florida AI-Powered Athletics / University Athletic Association · NCAA Division I athletics data infrastructure · United States (Florida)
- Publisher
- UF AI-Powered Athletics
- Original publication
- undated program page (retrieved 2026-09-29; content describes current UF Athletics Databank)
- Source retrieved
- 2026-10-01
What happened
UF’s AI-Powered Athletics program describes a centralized, IRB-approved Athletics Databank consolidating performance, health, and academic data for research and operations on HiPerGator. The page asserts HIPAA, FERPA, and HITRUST-aligned controls, role-based access after HIPAA/FERPA training, de-identification for external research, and multi-layer approval (IRB, Data Governance Committee, UAA Research Sub-Committee). It cites literature that little sport-science research occurs in real collegiate environments and that NCAA data often remains siloed. Why now: contrasts injury/recruiting AI product claims with a U.S. Power-conference example of governed data foundations—without publishing new outcome metrics on this page.
Why it matters
Direct college-athletics infrastructure and privacy-governance evidence for AI readiness—useful counterweight to model-first injury tools.
Evidence and measured results
Program statements on HiPerGator controls, review committees, and literature citations (Abt, Claudino, Luczak, Brewer); no primary outcome table on-page.
Limitations and uncertainty
University program page; undated; no measured injury/performance outcomes; governance claims not independently audited here.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- NCAA departments collect rich athlete data that stays siloed, blocking responsible AI research and ops.
- Stakeholders
- AD / UAA leadership
- Campus IRB / privacy
- Sports performance and medicine
- Engineering/research faculty
- Discovery questions
- Which source systems are actually landed today?
- What decisions use identifiable vs de-identified data?
- How are student-athletes informed of secondary research use?
- Value hypothesis
- A governed HPC databank can unlock collegiate AI research and clearer ops analytics if access and purpose limits stay enforced.
- Potential engagement
- Data-maturity assessment mapping sources, consent, and a first governed ML use case with committee path.
- Unsupported claims
- Infrastructure alone prevents injuries
- HITRUST removes all FERPA obligations
- Published win/health outcomes on this page
Pre-sales engineering
Role takeaway
- Fit
- Institutional athletics data platform on secure HPC for analytics/AI with research governance gates.
- Architecture and integration
- Ingest GPS/force/EMR/academic → governed warehouse on HiPerGator → RBAC apps + de-identified research extracts.
- Prerequisites
- Source-system data contracts
- HIPAA/FERPA training pipeline
- De-identification tooling
- Constraints
- Undated program docs
- No public schema/SLO
- Committee latency for research access
- Security
- Encrypt at rest/in transit; strict RBAC; external shares de-identified only; continuous monitoring as claimed.
- Proof of value
- Approved extract turnaround metrics
- Access recertification completion
- Lineage for one cross-domain dashboard
Delivery
Role takeaway
- Work
- Operate ingest/stewardship, run committee workflows, and onboard sport use cases without purpose creep.
- Dependencies
- HiPerGator capacity
- UAA Research Sub-Committee
- IRB calendars
- Ownership
- Platform stewards own infrastructure; sport units own operational interpretations; IRB owns human-subjects gates.
- Skills and adoption
- Mandatory privacy training; analyst enablement on governed tools.
- Governance checkpoints
- IRB
- Data Governance Committee
- UAA Research Sub-Committee
- Periodic access review
- Acceptance criteria
- No external identifiable shares
- Documented source coverage
- Athlete inquiry path defined
- Risks
- Purpose creep from research to high-stakes ops
- Consent gaps
- Silos persist under central branding
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Central longitudinal lake on institutional HPC with analytics/AI workloads—requires identity, de-identification pipelines, and domain separation of performance/health/academic data.
Governance
Who approves, reviews and stays accountable for outcomes?
Models a three-committee gate before research access; operational decision-making use still needs clear athlete-facing transparency beyond research IRB.
Security and privacy
What data, permissions and controls need testing?
Explicit HIPAA/FERPA/HITRUST claims and training requirements; still depends on correct classification of athletic vs education vs medical records in practice.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Internships/research access can build workforce pathways, but training gates and committee reviews may slow smaller collaborators.
Procurement
What should contracts, pricing and exit terms secure?
Prefer platforms that document FERPA/HIPAA mapping and multi-party access review over model demos alone.
Operating model
Which teams own the service once it runs?
Institutionalizes data governance as a prerequisite to athletics AI rather than bolting privacy on after model selection.
Publication history
- 2026-09-29College Athletics · Issue 245 resources
Stable resource ID: uf-athletics-databank-governance