Skip to main contentSkip to navigation
    What Concurrent Documentation Review Catches in an Inpatient Stay
    AI in Clinical Documentation

    What Concurrent Documentation Review Catches in an Inpatient Stay

    Care can happen throughout an inpatient stay without ever appearing in the physician's note. Nicki Bucceri, RHIA, walks through one admission and shows how reviewing the draft note before sign-off catches that gap while the patient is still in the hospital.

    Nicki Bucceri, RHIA, Senior Director of Coding Solutions
    11/3/2026
    6 min read

    When I coded inpatient charts, the gaps that cost hospitals the most were rarely due to wrong codes. They were care provided during the stay that never made it into the physician's note. The nursing notes and orders showed it clearly. The coder still couldn't code it because the provider never documented the diagnosis.

    Concurrent documentation review exists to catch that kind of gap while the patient is still in the building. Here's what it looks like in a single admission, and what changes when the review moves into the note itself.

    A patient admitted for one condition, treated for two

    A patient arrives through the emergency department and is admitted for a urinary tract infection. The admitting physician focuses on the UTI, which is reasonable. It's the reason she's there, and it's what the physician is managing most closely.

    Over the next few days, other care starts to show up in the chart. She's on supplemental oxygen. Nursing is monitoring her 02 levels. The ED notes record her daughter saying she's been recovering from pneumonia for the past four weeks. The physician knows about the pneumonia and is treating around it, but the progress notes keep coming back to the UTI.

    The care for the pneumonia is real. In the physician's documentation, it barely exists.

    Why the second condition matters to the claim

    Inpatient coding follows the Uniform Hospital Discharge Data Set (UHDDS) definition of other diagnoses. A secondary condition is reportable when it affects the patient's care, for example by requiring clinical evaluation, treatment, diagnostic work, a longer stay, or more nursing care and monitoring.

    Our patient's pneumonia meets that test. She's receiving oxygen and extra monitoring because of it. Compare her with a second patient who has a history of pneumonia that is fully resolved, needs no treatment, and changes nothing about the stay. The same word may appear in both charts, but only the first patient's pneumonia belongs on the claim.

    The difference matters because secondary diagnoses can qualify as complications or comorbidities (CCs) or major complications or comorbidities (MCCs). Under MS-DRG payment, a documented and coded CC or MCC can move the admission into a higher-weighted DRG that reflects the resources used during the stay. When the condition is treated but not documented, the coder has no basis to report it, and the claim understates the care.

    This is a simplified example. Real charts carry more nuance, and clinical validation still applies. The pattern is common, though. Physicians document the reason for admission well and document the conditions they're managing in the background less completely.

    How CDI finds the gap today

    A good CDI specialist reviewing this chart would notice care that doesn't line up with the documented diagnoses. Oxygen and nursing monitoring aren't part of UTI treatment, so the specialist would send the physician a query.

    A complaint query lays out the clinical indicators and leaves the conclusion to the physician. It might read something like this:

    Nursing is monitoring 02 levels, and the patient is on supplemental oxygen. ED notes indicate the patient's daughter reported pneumonia over the last four weeks that has been improving. Does this patient have an additional diagnosis impacting care?

    The query doesn't suggest an answer or mention payment. It shows evidence and asks the physician to make the clinical call, consistent with AHIMA and ACDIS guidance on query practice.

    The weak point is timing. Many hospitals start CDI review while the patient is still in-house, because that's the best window to get an answer. Even then, the query lands after the note is written, often in a queue the physician works through between patients. When the review happens after discharge, the physician is reconstructing a stay from memory, and the chart waits in DNFB until the answer comes back.

    Moving the review to the draft

    InstaNote CDR (Clinical Documentation Review) moves part of this work earlier, into the note itself. Afte InstaNote drafts the ntoe from dictation or ambient capture, CDR reviews the draft before the clinician signs.

    CDR looks at the draft across four areas. Completeness flags where treatment, procedures, or prescriptions may need clearer support. Consistency flags mismatches within the note. Specificity points to places where added detail would make the record clearer. Quality support surfaces items tied to care and quality measures. Established frameworks, including MEAT and TAMPER, support the checks. Each organization can configure what CDR reviews.

    In our example, the completeness check is the one that matters. The record shows oxygen and monitoring, but the draft note doesn't connect them to a diagnosis. CDR surfaces that gap to the physician moves on. Every finding is for the clinician to review and confirm, which keeps clinical judgment where it belongs and keeps the record defensible.

    What changes for CDI and coding teams

    When gaps like this are resolved before sign-off, fewer turn into queries. CDI specialists can spend their time on cases that need clinical expertise, such as unclear principal diagnosis and clinical validation questions, instead of chasing care that was visible in the chart all along.

    Coders benefit in a different way. They start from a note that reflects the full stay, so they spend less time interpreting what the physician meant and more time validating what the physician wrote. For a deeper look at how documentation drives inpatient code assignment, see our guide to inpatient medical coding.

    What it doesn't replace

    Review inside the note is a first pass. It doesn't replace a CDI program. Complex admissions will still need a specialist's eye. Queries will still be part of the workflow, and they still need to follow compliant practice. Coders still validate every code against the documentation and the guidelines.

    What changes is where the easy catches happen. Gaps that a physician can resolve in a few seconds while the note is open shouldn't have to wait days for a query.

    Documentation is where the revenue cycle starts

    I've seen a lot of revenue lost to gaps that were obvious in hindsight. The care was delivered and charted by nursing, but the physician's note never said it. Catching those gaps while the patient is still in the bed, and while the physician still remembers the case, is the most reliable way I know to keep the record and the claim aligned with the care.

    To see how CDR fits your documentation workflow, talk with the DeliverHealth team.

    Tags

    concurrent documentation review
    inpatient CDI
    CC/MCC capture
    CDI query
    Clinical Documentation Review

    Stay Updated

    Subscribe to our newsletter for the latest healthcare AI insights and company updates.