The Data Gathering Rubric Category: What ABOS Examiners Score

Data Gathering is one of the nine official rubric categories the ABOS uses to score candidates on the Part II oral examination. It sounds simple on paper. In practice, it's where a lot of candidates quietly lose points before they even open their mouth.

The question examiners are answering in this category is straightforward: did the candidate collect the information needed to make a good decision? History, physical exam, imaging, labs when relevant, prior records. That's the list. And the first place examiners look for the answer is the candidate's documentation.

What “Data Gathering” Actually Means on the Rubric

The nine-category rubric is how the ABOS standardizes scoring across examiners and candidates. Each category gets a 0–3 score. Data Gathering specifically evaluates whether the candidate collected enough clinical information — and the right clinical information — to justify the decisions they made.

Remember how the exam is structured: case selectors assign twelve of your submitted cases, and you only defend your own cases. You're not freestyling. You're walking through a case summary you submitted, and that summary is the first impression the examiners form of you.

For a deeper tour of all nine categories, start with our full ABOS scoring rubric breakdown. Data Gathering is one slice of it — but it's one of the easiest to influence before exam day.

Examiners Read Before They Listen

In the exam room there are two examiners. One leads the questioning. The other is reading your uploaded PDFs and case summary silently while you talk. If that second examiner finds a gap in your documentation — a missing history element, a vague exam, imaging that doesn't match your described pathology — they will surface it. Sometimes politely. Sometimes not.

This is why Data Gathering starts long before you speak. You're being scored on what's on the page as much as what comes out of your mouth. Candidates who document thoroughly already have points in the bank by the time the first question is asked.

What Hurts Your Data Gathering Score

Incomplete Histories

The history is the foundation. If examiners can't tell what the patient's functional complaints were, how long the symptoms had been going on, what conservative treatments were attempted, or what the patient's goals were — the category score drops. “After failing conservative measures” isn't a throwaway phrase. It's a data-gathering signal. List what was tried: PT, bracing, injections, activity modification, time.

Vague Physical Exam Findings

“Tender to palpation” with nothing else is a red flag. Examiners want to see specific maneuvers, laterality, strength grades, range of motion in degrees, neurovascular status, and the pertinent negatives that rule out the differential. If a provocative test is relevant — a Watson shift, a Spurling, a McMurray — it should appear in the documentation, not just your verbal presentation.

Missing or Mismatched Imaging

Every decision that depends on imaging needs the imaging in the record. That means the right views, the right modality, and ideally imaging that supports the classification you used. If you called it a Schatzker II, the CT should be there. If you templated a total knee, the templating views should be there. Examiners will ask you to classify on the spot — and the images need to back up what you wrote.

Missing Prior Records

Revision cases, failed prior treatments, prior operative reports, prior hardware — if a previous provider touched this patient and you didn't obtain those records, that is a data-gathering failure. Examiners will ask whether you had the prior op report. If the answer is no, it had better be a very good reason.

How to Present Data Gathering So You Earn Points

Walk through the data in the order it mattered for the decision. Not in the order it was collected chronologically. Not in the order EMR templates spit it out. The order that led you to the operative plan.

A solid structure sounds like this: the patient and the complaint, the relevant history and conservative treatments, the focused physical exam findings, the imaging and its key findings, any labs or prior records that informed the plan, and then the decision. Every item earns its place by contributing to the rationale.

Say the pertinent negatives — but don't read every single line of your documentation aloud. You already have the case summary pulled up in front of you for reference. Reference it, don't recite it. The examiners have already seen it.

For the mechanics of how your summary should be structured from the start, see our guide on case summary structure for the ABOS oral boards. The order you document in is the order you'll present in — get it right on the page first.

Documentation Is the First Test

A useful way to think about Data Gathering: your documentation is being graded before anything else happens. If a candidate with a clean, thorough case summary walked into the room silent, they would already be scoring better in this category than a candidate with a sloppy summary who hadn't spoken yet. The rubric rewards the work that happened months before exam day.

That's also why revisions matter. Candidates who edit and tighten their case summaries across multiple passes generally score better in Data Gathering than candidates who submit a first draft. Every pass is a chance to catch a missing element before an examiner does.

For more on why the written record carries so much weight, read documentation quality and the ABOS oral boards. And if you want a one-page reference for what each of the nine rubric categories rewards, grab the ABOS rubric cheat sheet.

A Quick Self-Check Before You Submit

Before any case summary leaves your hands, run it through four questions:

1. Can a stranger reading this understand why surgery was the right call? 2. Is every piece of imaging that supports the decision actually in the file? 3. Are the physical exam findings specific enough that I could defend them without the chart? 4. If this patient had been seen elsewhere first, did I obtain those prior records?

Four questions. A few minutes per case. Twelve cases. That work — done once, done carefully — is the cheapest way to protect your Data Gathering score on exam day.

The rubric is public. The categories are knowable. The candidates who treat Data Gathering as a documentation discipline, not a test-day performance, are the ones who walk into the room with points already earned.