Introduction: The High Stakes of Data Portability
You worked for those cases. Every 2 a.m. appy, every hernia you closed while your attending dictated. Now you're transferring.
And if you don't handle the log transfer correctly, you can lose them. Not because you weren't there. Because you can't prove you were there in a way your new program and the ACGME will accept.
Residency transfers are rare, messy, and high-stakes. The ACGME residency program transfer policy is clear: your operative experience must follow you with full verification. But the systems are not built for portability. They're built to keep you inside one institution. The moment your old email and portal access get shut off, which happens fast, usually within 72 hours of your last day, you lose your ability to fix anything.
The number one mistake I see? Residents assume the Program Coordinator will export and send everything. They won't. Or they'll send a PDF summary that's missing role definitions, modifiers, and half your second-assists. I've seen a PGY-3 lose 40+ index cases because they were "pending" when they left. That's a graduation-threatening problem.
Your case logs are your surgical currency. Treat this like moving a bank account, not forwarding an email.
This article is for educational purposes only and is not financial advice, not legal advice, and not tax advice. Figures vary by program and specialty requirements, so consult a qualified professional before you finalize your transfer plan.
1. Verify Institutional Review Board (IRB) and Data Ownership Policies
First thing to check: who owns your logs?
Most residents never ask. You logged cases in New Innovations, MedHub, E-Logbook, or some homegrown system. You think it's your data. Legally, the institution often has a claim, and the data itself contains Protected Health Information if you left MRNs, dates, or identifiers in the notes field.
Here's what you do, 60+ days before you leave:
Before finalizing these logs, review why big case logs can mislead surgical applicants to ensure your data reflects true clinical capability.
1. Read your GME agreement. Some contracts explicitly state that case data stored on institutional servers is institutional property. You have a right to your educational record, but not to the raw PHI.
2. Export a clean backup. Go into your current system and export everything as CSV and Excel. Not PDF. You want raw data. Two files:
- Unfiltered export with CPT, date, role, attending, hospital
- De-identified version with MRN, patient name, DOB completely stripped
3. Scrub it before you save it locally. HIPAA violation on your personal laptop is a fast way to torpedo a transfer. If your export includes any of the 18 identifiers, delete those columns. Keep: Date (year only if needed), CPT codes, role, case complexity, attending initials, verification status.
Store that clean file in two places: an encrypted personal drive and a secure personal cloud. Not your hospital OneDrive. That disappears.
Then email your current Program Coordinator in writing: "Can you confirm I am permitted to retain a de-identified copy of my case logs for ACGME board eligibility purposes?" Get that yes in writing. You'll need it.
2. Aligning Coding Standards Across Systems
This is where people get burned. Not on missing cases. On mis-coded cases.
Your old program called it "Teaching Assistant." Your new program's Clinical Competency Committee only counts "Surgeon Junior" or "Primary Surgeon" for certain CPTs. Suddenly your 15 laparoscopic cholecystectomies as TA don't count toward your minimums.
You have to do a manual cross-walk.
For complex transitions, consider how other residents successfully resolve discrepancies to avoid common credentialing pitfalls.
Pull the ACGME defined category list for your specialty. For general surgery, that's the current Defined Category Minimums. For ortho, plastics, etc., it's their Case Log Information page. Those definitions are the ground truth. Not what your old hospital called it.
Build a simple mapping sheet:
| Action | Example |
|---|---|
| What you logged | Lap Chole CPT 47562 as First Assistant |
| What ACGME says it is | Counts as Surgeon Junior if you did >50% of critical steps |
| What new program needs | Must be coded as Primary Surgeon to hit Category minimum |
Common discrepancies that cost credit:
- Assistant vs. Teaching Assistant. Teaching Assistant often requires you to be senior resident supervising a junior. If you were PGY-2, that code is likely invalid for board credit now.
- Two surgeons, one case. Some systems split bilateral cases into two entries. Others log as one with modifier 50. ACGME wants specific formats.
- Endoscopy and bedside procedures. Your old program might not have required them. Your new one will.
Fix this before you import. Once it's in the new system, cleaning up 300 mis-coded entries is miserable.
Pro tip: Ask your new Program Coordinator for a blank CSV import template. Map your data to their columns exactly. If they use MedHub and you came from E-Logbook, the "Role" dropdown values won't match 1:1. Do it yourself. Don't let the software guess.
3. The Verification Audit: Ensuring Attending Sign-Offs
If it isn't signed off, it didn't happen for the ACGME. That's the rule every Program Director lives by.
Two weeks before your last day, run a filter for all cases marked "Pending," "Awaiting Attestation," or "Draft." Sort by attending. You'll find the same three names. Always.
Here's the aggressive but professional protocol that actually works:
1. Make it frictionless. Don't send a generic "please sign my cases" email. Send each attending a short list: MRN-less identifiers (Date, CPT, OR Room), plus the operative report number. Include a direct link to their attestation queue. Some attendings have 60+ pending clicks. Make yours the easiest.
2. Get secondary proof. For your 10-20 most critical index cases, the ones you need for minimums, take a screenshot of the signed log, or download the signed attestation PDF. Save the op report (de-identified). Put it in a folder called "Transfer - Verification Proof." When the ACGME site visitor asks your new PD where those cases came from, this folder saves you.
3. Don't leave without a letter. Ask your current PD for a brief letter summarizing your verified totals by ACGME category. One page. With program letterhead, signature, date. "Dr. X completed Y cases as Surgeon Junior through [date], all verified in [system]." That letter is gold. Programs trust letters more than CSVs.
I've seen residents leave on a Friday assuming "Dr. Smith will sign them over the weekend." He didn't. He retired. Now that resident is emailing a dead inbox from another state.
Get signatures in person if you have to. Camp outside the surgeon lounge. This is your future case count.
4. Final Checklist: The Logistics of Migration
These last four will make or break a smooth start.
Point 4: Evaluating platform compatibility
Are you moving from E-Logbook to MedHub? MedHub to New Innovations? Each has different required fields. MedHub requires "Participated Level." New Innovations wants "Supervision Level." Test the import with 5 cases first. Does it reject CPTs with modifiers? Does it auto-downgrade your "Primary" role to "Assistant" because you logged PGY-1 cases? Find out on day one, not month three.
Keep your master offline repository in the exact format your new system needs. That's your source of truth.
Point 5: Establishing communication with the new Residency Program Director
Send your new PD and new Coordinator an audited summary before you start. Not 300 rows. One page: total cases by category, percentage of minimums met, any competency gaps you're worried about. For example: "I'm at 85% for Basic Laps but only 40% for Major Vascular."
This does two things: it shows you're organized, and it lets them place you on the right services immediately. No PD wants to discover in October that you've never done a central line.
Point 6: Verifying cumulative minimums for graduation
Your cumulative total is not just Old + New. It's Old (verified) + New (projected) must meet the ACGME minimums by graduation. Some programs also have internal minimums higher than ACGME.
Ask your new PD explicitly: "Based on my transferred totals, what rotations will ensure I hit [e.g., 850 major cases]?" Get that in writing in your individualized learning plan. If you're a PGY-4 transferring with 400 cases, you need a math check.
Point 7: Confirming ACGME reporting compliance
Your new program has to report you as a transfer in ADS, and your case logs have to roll up into their program's aggregate data correctly. If your cases import as "Resident performed at outside institution," they may not count toward their program's board pass rate reporting unless coded correctly.
Ask: "Will my transferred cases be tagged as 'Credit Granted at This Program' in ADS, and do you need any additional forms from my old PD for the RRC?" Yes, they do. The ACGME requires a letter verifying prior training and competence. If your old PD drags their feet, your board eligibility can be delayed.
Conclusion: Securing Your Surgical Legacy
Your logs are more than numbers. They're proof of competence. Proof you've done the work.
Don't wait until your access is revoked. Start 60 days out. Export, de-identify, map your CPTs to ACGME standards, hound attendings for sign-offs, and send a clean summary to your new leadership before you show up.
Keep one encrypted master file forever. Not on a hospital server. On your own drive. I keep mine as Surname_ACGME_Master_2020-2026.xlsx and update it monthly. In ten years, when a hospital credentialing committee asks for your residency case totals, you'll still have them.
You earned those cases. Now make sure you keep them.
