An OB/GYN resident spends a weekend trying to reconstruct an entire certification case list, unable to get Epic to produce it, facing possible job consequences over a Monday deadline. Nobody taught them how to pull this data, nobody taught them to log it as they went, and by the time it became urgent, it had become a crisis instead of a task. This is a genuinely solvable administrative problem — but only if you understand the system before you’re up against its deadline.

Why “complete and accurate” is a professional exposure, not a formality

Case logs and attestations aren’t paperwork in the trivial sense. When you sign an attestation, you’re formally certifying — to your program, your specialty board, and in a meaningful sense to future patients and employers — that the case volume and case types you’re reporting are real and complete. This carries genuine professional weight: attestations are treated as a form of professional integrity documentation, not an administrative checkbox, and discrepancies discovered later (inflated numbers, missing categories, reconstructed data that doesn’t match the actual record) can become a credentialing and professionalism issue that outlasts residency itself. Treat the accuracy of what you’re attesting to as seriously as you’d treat any other formal professional certification, because that’s exactly what it is.

What case requirements actually ask for, by specialty

The specifics vary meaningfully by specialty, and it’s worth knowing your own board’s actual requirements early rather than assuming a generic version applies:

• OB/GYN requires detailed operative case logs across defined categories (obstetric deliveries, gynecologic surgery by type and approach, minimum volume thresholds per category) tracked throughout residency, not compiled retroactively.
• General and subspecialty surgery programs typically require detailed operative logs categorized by procedure type, your role in the case (primary surgeon, first assist, teaching assistant), and specific minimum case-type thresholds set by the relevant board.
• Anesthesia requires logging of case types, patient acuity, and specific procedural categories (regional blocks, lines, airway management types) against defined minimums.
• Emergency medicine requires procedure logs for a defined list of critical procedures (intubations, central lines, procedural sedations, and similar), tracked by volume against minimums the board sets.

The common thread across all of these: the requirement is designed to be built incrementally over the length of training, not reconstructed at the end. Every specialty’s system assumes contemporaneous logging. None of them are actually designed to be extracted retroactively from the EHR under deadline pressure — which is exactly why that approach fails so often and so badly.

Why pulling your own case data from Epic is harder than it should be — and what actually works

This is the specific technical trap the OB/GYN resident above fell into, and it’s worth understanding precisely so you don’t repeat it:

• SlicerDicer is the wrong tool for this job, structurally, not just practically. SlicerDicer is built for aggregate, exploratory population analysis — it shows you patterns and counts across a population, pulling from a data warehouse with roughly a one-day lag, and it does not produce record-level, case-by-case extracts. Trying to get your own individual case list out of SlicerDicer is fighting the tool’s actual design, not a matter of not knowing the right clicks.
• Reporting Workbench is the tool that actually does record-level extraction — but it typically runs from pre-built report templates rather than fully custom, freeform queries, and access to specific templates (or the ability to have a new one built) is gated by institutional permissions that a resident often doesn’t have by default.
• Find out, early in residency, who at your institution can actually build or run a Reporting Workbench query for you — this is usually someone in clinical informatics, health information management, or your department’s own analytics support, not something available through your standard clinician-level Epic access. Ask your program coordinator who this person is before you need them urgently.
• Some programs already have a standing report built for exactly this purpose, precisely because this problem recurs every year. Ask directly whether one exists before assuming you need to build the wheel from scratch under deadline pressure.

Why waiting until the deadline turns a data problem into a career problem

The moment this shifts from manageable to a crisis is entirely about timing, not the underlying difficulty of the task. Requesting a custom data pull from an informatics team with three months of runway is a routine, low-stress ask. Requesting the same pull with 48 hours until a hard deadline turns it into an emergency that depends entirely on someone else’s availability and goodwill — and if your institution’s analytics team is small, backlogged, or unavailable that specific week, you may simply run out of runway regardless of how urgently you ask. The technical problem doesn’t get harder as the deadline approaches. Your leverage to solve it does.

Building a five-minute-per-week logging habit from PGY-1

The actual fix is upstream of all of this: log your own cases contemporaneously, in a format you control, starting in intern year, so reconstruction is never necessary regardless of what any institutional tool can or can’t produce on demand.

• Pick one simple system and stick with it — a spreadsheet, your specialty’s official logging app if one exists, or even a running note — and update it within a day or two of each relevant case, while it’s still fresh and easy to categorize correctly.
• Log the specific fields your board actually requires, not just “did a case” — role in the case, procedure type and subtype, date, and any acuity or category distinctions your specialty’s requirements track. Check your board’s actual requirements once, early, and build your logging categories to match them exactly rather than guessing.
• Treat this as a five-minute weekly habit, not a daily chore — batch it to a specific low-stakes time (Sunday evening, post-call recovery) rather than trying to remember it in real time after every single case, which is where the habit usually breaks down.
• Keep your own copy outside institutional systems. A personal spreadsheet, backed up somewhere you control, means you’re never dependent on EHR access, institutional report-building capacity, or anyone else’s availability when a deadline arrives.

When the tooling or the deadline is genuinely unworkable

If you’ve done everything right and you’re still stuck — the data genuinely isn’t extractable in time, or a true gap exists in your own contemporaneous records — there’s a real escalation path, and using it early is far better than a defensive scramble alone in your final days:

• Your program coordinator is usually the fastest first call — they’ve likely navigated this exact problem with prior residents and may know a faster path than you’d find on your own.
• Your GME office can often escalate an institutional data-access problem faster than an individual resident can, particularly if the issue is genuinely about institutional tooling rather than your own logging discipline.
• Your specialty board’s own extension and hardship policies. Most boards have a defined process for requesting a deadline extension or documenting a legitimate institutional barrier — this is a normal, anticipated situation from the board’s perspective, not a unique failure on your part. Contact them directly and explain the specific, factual barrier (an institutional data-access delay, for instance) rather than assuming the deadline is absolutely immovable.

The paperwork calendar nobody hands you

Case logs are one piece of a larger stack of administrative deadlines that cluster around the same period of training, and it’s worth having a single view of all of it rather than discovering each piece separately:

• State medical license application — often the longest lead time in this entire stack; start as soon as you have any confirmed practice location.
• DEA registration — tied to a confirmed practice address, apply as soon as that’s finalized.
• Fellowship or job applications, with their own separate document and deadline requirements.
• Credentialing packets for your eventual employer — CAQH, primary-source verification, malpractice history — much of which draws on the same underlying documentation (training dates, case volumes, licensure) you’re already tracking for board certification.
• The fee stack nobody budgets for: board certification fees, exam fees, state licensing fees, ACLS/BLS renewal, and required texts or question banks — a real, recurring out-of-pocket cost that lands specifically during the lowest-income stretch of a physician’s career and is worth planning for financially, not just logistically.

Why this discipline pays off again at your first attending job

The exact same documentation habits — accurate contemporaneous logging, understanding what an institution’s systems can and can’t produce on demand, knowing who to ask before you urgently need them — resurface immediately in hospital credentialing and privileging for your first attending position, which will ask for much of the same underlying case and training documentation all over again. Residents who build this discipline early aren’t just protecting themselves against a board certification deadline. They’re building a skill that follows them through the rest of their career, every time an institution asks them to document and verify their own practice.