Skip to main content
MedicMind
Log InSign Up
For Programs

Run your clinical rotations on the same platform your students already study on.

Preceptorship is the field side of MedicMind: preceptor approvals, shift scheduling, and signed evaluations that neither party can game. Separate from classrooms — run either, both, or neither.

What Preceptorship actually is

When your students go into the field, somebody has to schedule the shifts, somebody has to evaluate each one, and somebody has to keep the paperwork in a state that survives an audit. Preceptorship does those three things in one place, and keeps the evaluations honest by making sure neither the student nor the preceptor can see the other's answers before they have both committed to their own.

It runs independently of classrooms. A program can use Preceptorship for field rotations without ever creating a classroom, or use both side by side.

How it works

From join code to signed report

  1. Create your program and share two codes
    Your program gets its own join code for preceptors and a separate one for students. Nobody joins without a code, and the two are distinct so a student can never land in the preceptor queue by mistake.
  2. Approve your preceptors yourself
    Field preceptors apply using your code — they cannot sign themselves up and start working. Each application waits for you to approve or reject it, so the people evaluating your students are people you have vetted.
  3. Assign students and set a shift target
    Each student is paired with a preceptor and given the number of shifts they need to complete. Progress against that target is tracked automatically as shifts are logged — no separate spreadsheet.
  4. Students schedule their own shifts
    Students book their shifts, which appear on their preceptor's calendar straight away. You are not the middleman for scheduling, but you can see the whole picture at any time.
  5. Every shift becomes a numbered report
    Each completed shift produces its own report, numbered in sequence, including a log of the individual calls that were run on it. The paperwork is a by-product of doing the work, not a separate chore.
  6. Both sides evaluate without seeing each other
    The student rates their own confidence and the preceptor rates the student. Neither can see the other's answers until both have signed. That is enforced by the database itself — not merely hidden on screen — so an honest self-assessment stays possible.
  7. Signing locks the report
    Submitting a report is the signature. It records the signer's name, role, and certification level. After that only you can reopen it, doing so requires a written reason, and the record carries a stamp that proves whether anything changed afterwards.

Why it is built this way

Why blind evaluations matter
If a student can see their preceptor's rating before submitting their own, they will match it. Keeping both sides sealed until they have each signed is what makes a self-assessment worth reading.
Records that hold up later
Every signed report keeps who signed it, when, and at what certification level, plus a seal that reveals any later edit. If a report is ever questioned months down the line, the record answers for itself.
Your paperwork, not ours
Build your program's own evaluation form from eight question types and publish it. Each report permanently keeps a copy of the form version it was completed under, so changing the form never rewrites past reports.
In full

Preceptorship — Clinical Preceptorship

A complete system for the clinical side of your program, separate from classrooms — run either, both, or neither. Create a program with its own preceptor and preceptee join codes; field preceptors apply with the code and you approve or reject each one. Preceptees are assigned to a preceptor, carry a required-shift target tracked as they go, and schedule their own shifts, which appear on their preceptor's calendar. Every shift produces a numbered report with a log of individual calls, and the evaluations inside it are genuinely blind — neither party sees the other's ratings until both have signed. Submitting is the signature; only you can unlock a submitted report, it takes a reason, and the record carries a tamper-evident seal you can re-verify at any time. Bring your own paperwork, too: build your program's report form from eight question types, publish it as a numbered version, and every report keeps a physical copy of the version it was created under.

Preceptorship starts with the program. So the first step is yours.

Preceptors apply to you with your code, and you approve them — which means there is nothing for them to sign up to until your program exists. Tell us about yours and we will help you set it up.