13.3 Physician Education Tools, Forms, and Presentations
Key Takeaways
- Build education from that service’s repeat query themes and de-identified local cases, not from a single generic be specific lecture used on every unit.
- Physicians, nurse practitioners, and physician assistants need case-based specificity teaching because they write the notes coding can use; administrators need a separate metrics briefing (CMI, response rates, quality implications), not bedside diagnosis phrasing.
- Pair a short live presentation with an original leave-behind (tip card, huddle deck, orientation checklist) and remeasure the same query topics about 90 days later.
- Create original hospital tools; do not photocopy or lightly rebrand copyrighted ACDIS, AHIMA, or vendor query forms and education packets.
- Education teaches complete, clinically truthful description—not which diagnosis raises reimbursement or a quality score.
13.3 Physician Education Tools, Forms, and Presentations
Quick Answer: Effective inpatient CDI education is department-specific, case-based, and aimed at the people who write the note—including physicians, nurse practitioners, and physician assistants—while a separate, metric-focused version is built for administrators. The goal is fewer repeat queries, not a one-time lecture. Build original tip sheets and slide decks; do not copy copyrighted ACDIS or vendor forms.
A query repairs one encounter. Education is how a CDI program stops asking the same question on the same service every week. ACDIS lists two related Domain V skills: methods for creating physician education forms and tools, and the ability to produce basic educational presentations tailored to a department or service—including physicians, nurse practitioners (NPs), and administration. This independent OpenExamPrep section teaches how to build those products without turning CDI into a revenue-coaching roadshow.
Start From Repeat Work, Not From a Generic Deck
The method that holds up on an application item is boring and effective:
- Export or tally queries by service and by theme (unspecified heart failure, AKI versus dehydration, encephalopathy versus delirium wording, sepsis without linked organ dysfunction, postoperative complication versus expected finding).
- Pick three to five themes that actually recur—not the themes you find interesting.
- Pull two or three de-identified local notes that show the gap and a cleaner rewrite the provider could have written.
- Write one learning objective per tool (After this huddle, hospitalists can document heart-failure type and acuity when the echo and treatment are already in the record).
- Choose the vehicle: five-slide huddle, one-page card, orientation checklist, or administrator briefing.
- Name an author, a physician-advisor reviewer, and a review date so the tool does not fossilize.
- Deliver the teaching, then remeasure the same themes (a common window is about 90 days).
If you skip step 1, you will give cardiology the same malnutrition lecture you gave orthopedics and wonder why query volume did not move. Department-specific means the cases, the vocabulary, and the length match the people in the room.
Audiences Are Not Interchangeable
Physicians (attendings, hospitalists, specialists, residents, fellows) need clinical language and their own cases. Ten to fifteen minutes at a standing service meeting beats a 50-minute noon conference that restates the entire MS-DRG system. Show the note they already wrote, the indicators that were present, and the one sentence that would have made the condition reportable. Teach how to find and answer a query in this electronic health record. Leave time for pushback; defensiveness is data about whether your last queries felt leading.
Nurse practitioners and physician assistants write a large share of inpatient progress notes. For coding purposes, a provider is a physician or other qualified healthcare practitioner legally accountable for establishing the patient’s diagnosis. If NPs and PAs document on your units, they are a primary education audience, not an afterthought. Give them the same specificity content you give physicians on that service. Do not send them a separate “mid-level” deck that talks down or that swaps clinical teaching for throughput tips. If medical-staff rules require attending attestation for certain statements, teach that workflow too—otherwise you will keep querying the attending for a diagnosis the NP already wrote in a note the attending never acknowledged.
Administration (CMO, CFO, service-line directors, quality directors) does not need a slide on how to stage chronic kidney disease in the progress note. They need hospital-level or service-level metrics: query volume and response rate, agreement versus disagreement patterns, case-mix movement that you can honestly attribute to documentation completeness (not to a promised revenue lift), denial themes that started as vague notes, and quality-program exposure when diagnoses that feed claims-based measures are missing or unsupported. A quarterly 20-minute briefing with three charts and one ask (protected time at the hospitalist meeting; advisor hours) is a different product from the huddle deck. Reusing the cardiology specificity slides in the board packet signals that CDI cannot tell a clinician from a finance audience.
Residents and fellows need a short orientation in the first weeks plus a monthly case, because they rotate. Nursing and allied staff generate many of the indicators CDI cites, but they do not establish reportable diagnoses. A nursing in-service on why a wound-care note is not enough to code a pressure-injury stage without provider documentation is useful; it is not a substitute for physician and NP/PA teaching.
| Audience | Teaching goal | Typical vehicle | Do not |
|---|---|---|---|
| Service physicians | One or two specificity habits using their cases | 10–15 minute huddle plus one-page card | A generic code-set lecture |
| NPs and PAs | Same clinical specificity plus who must attest | Same huddle or a dedicated 15-minute slot | A separate revenue-target talk |
| Residents / fellows | How this hospital queries and what “after study” looks like | Orientation checklist plus monthly case | One-time intern boot camp with no follow-up |
| Administration | Program impact and resource needs | Metrics one-pager and 20-minute briefing | Bedside diagnosis phrasing or copied vendor forms |
| Nursing / allied | What they can document versus what a provider must state | Unit huddle | Asking nurses to name MCCs so CDI can skip the query |
Tools and Forms You Can Build—Without Copying ACDIS
ACDIS, AHIMA, and commercial vendors publish query templates, pocket cards, and education packets that are copyrighted. Domain V asks you to identify methods and to produce basic presentations. That is not a request to photocopy an ACDIS sample form, strip the logo, and call it your hospital’s toolkit. Use published query-practice rules (nonleading, sourced indicators, no reimbursement language) as constraints. Write the hospital’s own words. If you quote a clinical definition (for example a Kidney Disease: Improving Global Outcomes (KDIGO) AKI statement), attribute it and keep it neutral at the end of a teaching card—the same discipline the 2026 query guidance uses when definitions appear on a query.
Original tools that map cleanly to exam scenarios:
- Service specificity card (one page). Three columns: what we keep seeing, what the record already shows, the sentence that would complete the thought. One diagnosis family only.
- Query theme tracker. A simple table: service, theme, query count, response rate, education date, 90-day recount. This is a form for the program, not a form the physician fills out.
- Five-slide huddle deck. Title and one objective; de-identified case A; de-identified case B; how to answer a query in the EHR; where to find the leave-behind. No slide titled How this raises CMI.
- New-provider orientation outline (20 minutes). Who CDI is, what a query is and is not, two local examples, who to call, and the hospital’s policy that CDI will not add diagnoses or edit notes.
- Administrator one-pager. Volume, response, top themes, one quality or denial example, one resource request. Dated.
- Query-response walkthrough. Screenshots from your EHR (or a sketched path if you are designing the tool on paper) so providers stop ignoring alerts they cannot find.
Design rules: one objective, readable on a phone, reviewed by a physician advisor, free of reimbursement coaching, and retired when the theme dies. An EMR smart phrase can support education if it still requires the provider to think; a cloned phrase that drops acute-on-chronic systolic heart failure into every note is the opposite of integrity.
Presentations That Match the Room
A basic service presentation is short on purpose. Open with a number the room already believes (last quarter this service received 40 unspecified-heart-failure queries). Show two notes. Ask the group what is missing before you show a model sentence. Close with the card and the query path. If a physician advisor co-teaches, the advisor speaks the clinical controversy; CDI speaks the query and coding consequence. Do not let the advisor become a second coder at the podium.
For administration, invert the order: start with risk (unsupported MCCs, denials, publicly reported measures that need complete claims), then show that education—not query volume alone—is the control. Ask for calendar time on the services that generate the themes. Do not promise a published CMI target you cannot defend.
Reducing Repeat Queries Is the Outcome Measure
If the same hospitalist is queried weekly for the same gap, the program has a teaching failure, a leading-query problem, or a provider who will not engage. The educational response is not to raise every specialist’s query quota and not to stop querying. It is to teach the high-frequency topics for that service, offer nonpunitive one-to-one coaching (often with the physician advisor as the peer), and remeasure those topics. Track whether those queries fall. If they fall and the clinical care did not change, you taught documentation completeness. If they fall because staff stopped querying, you taught silence—and Domain VII will call that a compliance problem.
Worked Example: Hospitalist Heart-Failure Theme
Query data show that 40 percent of hospitalist queries last quarter were unspecified heart failure, even though echocardiograms and intravenous diuretics were already on the chart. CDI builds an original one-page card (HFrEF versus HFpEF; acute, chronic, or acute-on-chronic) and a 12-minute huddle with three de-identified notes from that group. NPs on the same service attend. The CMO briefing the next week shows the query share, the response rate, and a request for the huddle to sit on the standing hospitalist agenda; it does not include the card’s model sentences. Ninety days later the unspecified-heart-failure query share is recounted. That cycle—data, audience-specific tool, presentation, remeasure—is the method Domain V is pointing at.
Education must never become “document this MCC.” Teach the clinical truth the record already supports and the words that make that truth reportable. The claim will follow the record. The record must follow the patient.
CDI is asked to present at the monthly hospital operations meeting. Which design fits an administrator audience?
One surgical service generates the same postoperative-complication query every week. What education strategy is aimed at reducing those repeat queries?
Why should NPs and PAs be included in inpatient CDI education for a service they staff?
A new CDI program wants a standard query form and a pocket card next week. Which approach matches Domain V tool-building without creating a copyright or integrity problem?