For pre-health offices and programs
Give your office one system. Give your students their data.
MedPath runs the whole advising operation: roster onboarding, per-advisor caseloads, comment threads on real drafts, and end-of-cycle outcome reporting. It all runs on a consent model where the student, not the institution, holds the account.
Outcomes · 2026 cycle
Prepared by Dr. Elena Ruiz, Pre-Health Advising, Westbrook University · as of 7 Sep 2026
Outcomes recorded
n = 58 of 71- Matriculating71% · 41
- Reapplying21% · 12
- Still deciding8% · 5
Every rate is taken over the 58 outcomes actually recorded, never over all 71.
Outcome unknown · 13
Kept apart rather than collapsed into “other.” You can chase a student who closed without recording one; you can’t do anything about one who never shared.
- Cycle still open4
- Closed without recording an outcome6
- Never shared decisions with the office3
What an office gets
Four things that change how the cycle runs.
One place your advisors actually work.
Every advisor in the office sees their own caseload, with the same signals and the same rules. No more one spreadsheet per advisor, each shaped differently and none of them current.
Onboard a cohort in an afternoon.
Upload the roster as a CSV of names, emails and class years. Every student gets an invitation explaining who’s asking and why. They decide what to share.
Close the cycle with a number you can defend.
Outcome collection happens at close-out, while students still have a reason to answer, not through a survey emailed to a graduated senior’s dead university address.
Continuity across advisor turnover.
When an advisor leaves, their caseload doesn’t leave with them. Reassign within the office, subject to the same student-granted scopes.
Rollout
No migration. No implementation quarter.
There’s no institutional data store to move into, because each student’s account is their own. Standing the office up is mostly sending invitations.
- 01
Advisor accounts
Each advisor sets up advisor mode with their name, institution and title. Fifteen minutes for the office.
- 02
Roster upload
One CSV of names, emails and class years. Duplicates and bad addresses are caught before anything sends.
- 03
Students accept
Each student picks their scopes. Acceptance rates go up when the invitation says who’s asking and why.
- 04
Cycle close-out
Students record outcomes while it still matters to them. The report is ready when the Dean asks.
Security & privacy
The questions your general counsel will ask.
Short answers, because the long ones are in the privacy policy and we’re happy to walk your team through the model.
- Student-granted access, enforced at the database
- Row-level security on every table. An advisor’s reach is bounded by an active relationship and the scopes on it, not by a filter in application code that a bug could skip.
- Read-only by construction
- There is no write path from an advisor to a student’s application. Comments are the one thing an advisor creates, and they can only resolve their own.
- Expiring access, revocable instantly
- Every relationship carries an end date. Students can revoke at any moment; the office is notified that access ended, never why.
- No training on student content
- Essays and application data are never used to train outside models. AI coaching runs against the student’s own material and returns questions, not prose.
- Reports carry provenance
- Every export is stamped with who ran it, for which office, and as of what date, so a figure in a board deck can be traced back to its source.
- Export and deletion are self-serve
- Students can take their data out or delete it without a support ticket. Institutions are not a party to that decision.
Security questionnaire, DPA, or a technical review with your team:privacy@medpathapp.com.
Get onboard
Tell us about your office.
How many advisors, how many applicants a cycle, and what currently breaks. We’ll come back with a walkthrough against your actual roster shape, not a generic demo.
- A 30-minute walkthrough of advisor mode with your cohort in mind.
- A straight answer on pricing for your number of advisors.
- Security review materials up front, not after you ask twice.
Prefer email? advisors@medpathapp.com
Send us four lines
Email advisors@medpathapp.com and tell us:
- 1.Your institution and your role in the office
- 2.How many advisors would need a seat
- 3.Roughly how many applicants you carry per cycle
- 4.The part of the cycle that currently costs you the most time
We reply to every one of these, usually within a working day.
What offices ask first.
Who is the customer, the office or the student?
The student owns the account and the data; the institution buys the advising layer on top. That distinction is not a technicality. It means the office cannot see a student who hasn’t shared, cannot override a revocation, and cannot export a student’s essays. Offices tell us this is the part that gets it past their general counsel.
Can we require students to share with our office?
You can invite everyone on your roster, and you can make a strong case for why sharing helps. You cannot force a share, and MedPath won’t build a way to. A coerced share produces a caseload full of accounts nobody trusts.
Do you integrate with our SIS or CRM?
CSV import and export today, which covers roster onboarding and end-of-cycle reporting for most offices. Direct integrations are scoped per engagement. Tell us the system and we’ll tell you honestly whether it’s in reach.
Is there an implementation period?
For most offices it’s an afternoon: set up advisor accounts, upload the roster, send invitations. There’s no data migration, because there’s no institutional data store to migrate into. Each student’s account is their own.
What happens to our reports if we stop using MedPath?
Export everything your office holds, caseload records and cycle outcome reports alike, as CSV before or after you leave. We don’t hold reporting history hostage.