For Partner Sites

Participating in UT-REAL

This page is for partner-school faculty and their compliance, legal, and IT colleagues. UT-REAL is required to disseminate this capability; a school can run the workflow locally through OASIS, with the UTSW team helping stand that up. See current site status on Participating Sites.

The path

How a school joins

A partner school travels these stops at its own pace. This is a process map, not a live scoreboard. Partner schools are in Approvals. UTSW production is already at live use.

  1. 1

    Getting ready

    Champion · local plan

  2. 2Partner schools now

    Approvals

    IRB · agreement · tech path

  3. 3

    Retrospective check

    AI vs human on past cases

  4. 4

    Live use

    Prospective grading

  1. 1.Champion

    A named faculty owner at the school.

  2. 2.Local plan

    How the school intends to start — often notes or transcripts first.

  3. 3.IRB review

    Local IRB review or reliance on the multi-school template.

  4. 4.Data agreement

    A site-specific research or data-use agreement.

  5. 5.Tech path

    UTSW-supported, local OASIS, or still deciding. No shared production host has been selected.

  6. 6.Approved package

    Only the minimum package approved for that site may move. A school can also run locally and keep data on site.

  7. 7.AI–human check

    Retrospective comparison on an approved historical set, where authorized.

  8. 8.Prospective use

    Faculty-reviewed grading in an active administration. UTSW production is already here.

What is UT-REAL, the UT REAL Health AI Pilot Program, and MAPLES?

UT-REAL is this six-school project — Scaling and Validating AI-Enabled Simulation Assessment Across University of Texas Medical Schools.

The UT REAL Health AI Pilot Program is the UT System funding program ($300,000, awarded March 2026, 18 months).

MAPLES is the AI grading platform already in production at UT Southwestern, which this project is preparing for governed multi-site validation. Wayfinder is the assistant inside MAPLES.

What does participation require?

Participation typically includes local IRB review or reliance on the multi-school template, a site-specific research or data-use agreement, and a data package prepared by the site. Each school moves at its own pace. No school is required to go live on a shared production host.

What data leaves a site?

There is no universal package. Only the minimum package approved for that site may move. Rubrics and retired cases may precede student records. Permissions for text, audio, and video differ by site. No cross-site production host has been selected.

Who assigns the grade?

Faculty retain final authority. In the UTSW production workflow, prespecified low-scoring cases are routed for mandatory human review. AI output is decision support, not an automatic final grade.

Can our school keep its own rubrics?

Yes. The project shares tools and practices for AI-compatible rubrics. It does not require a single shared rubric.

How is this structured legally?

UT-REAL is structured as an academic research collaboration rather than a commercial software purchase; each institution determines which local privacy, security, legal, or technology reviews apply.

How do we request a walkthrough?

Email andrew.jamieson@utsouthwestern.edu with your institution and use case. Include Tra Ngo for coordination questions.

Where is the work hosted?

UT Southwestern production runs on UTSW-managed infrastructure. A partner school may instead run the stack locally. The UT Health Intelligence Platform remains one path under feasibility review. No final cross-site host has been selected.

Can our school run this locally instead of sending data to UTSW?

Yes. UT-REAL is required to disseminate this capability, not only to operate it at one site. That path is OASIS (Open Assessment and Scoring Infrastructure Stack). A participating school can run the workflow on its own infrastructure, with data remaining at the site, and the UTSW team will help stand that up. Local operation and UTSW-supported operation are both in scope; each school chooses with its own privacy, security, legal, and technology reviews.

The public OASIS project page describes the stack and hosts a sanitized demo. It is not a self-serve software download. Local stand-up is arranged with the UTSW team, not by installing a public release.

Ready to talk through a site path?

Email the PI with your institution and use case — including local OASIS stand-up, a walkthrough, or a governance question.