Resident data, handled plainly

• Account information — name, email address, program, and role (resident, faculty, or program director).
• Learning records — lesson and module completions with dates, pre- and post-test answers and scores, and didactic-engagement activity.
• Teaching records — faculty sign-offs on completed modules.
• Program settings — enrollment status and program-level preferences set by the program director.

Nothing else. The platform has no field for, and must never receive, patient information. Teaching cases are fictional, and the Q&A feature carries a standing rule: no patient names, dates, or identifiers, ever.

• A resident sees their own full record.
• The resident’s own program director and designated faculty see individual results — completion, scores, and score changes — for their program’s residents only, on the program dashboard.
• No program can see another program’s data. There is no cross-program leaderboard and no public ranking.
• Residents are told this before they start: the About page states plainly that their program director and faculty see their individual results.

Learning records are used to deliver the curriculum, to document participation and knowledge gains for the program’s own evaluation processes (including Program Evaluation Committee review), and to improve the curriculum. Data is never sold, never used for advertising, and never shared with third parties for marketing. Aggregate statistics used to describe the curriculum’s reach do not identify individual residents.

• Records are retained while a program participates, so longitudinal score changes remain visible.
• A program can export its own residents’ results (CSV) from the dashboard at any time.
• When a program’s participation ends, the program may request a final export and deletion of its residents’ records.
• An individual resident may request correction or deletion of their account data at any time; deletion removes the account and its learning records, subject to any record the program itself is required to keep under its own institutional policies.

The platform runs on Google Firebase (hosting, authentication, and database). All non-public content requires sign-in, and database access is restricted by role-based rules: a signed-in user can reach only the records their role and program allow. Programs enrolling under an institutional agreement can request terms covering access, retention, and deletion specific to their institution.

Questions about data handling: Ask Dr. Mahato.