Skip to main contentSkip to navigation
    Emergency department outpatient encounters
    Autonomous Medical Coding

    Single Path Coding for Hospital Outpatient Encounters

    Facility and professional coding for the same outpatient encounter often run in separate queues, so the chart gets read twice and the claims can drift apart. Single-path coding works from one record, keeping both claims consistent while each side moves at its own pace.

    Nicki Bucceri, RHIA, Senior Director of Coding Solutions
    11/16/2026
    7 min read

    A hospital outpatient encounter can produce two kinds of claims. The hospital bills a facility claim on the UB-04, coded with ICD-10-CM diagnoses and CPT and HCPCS procedures, and Medicare pays it under the Outpatient Prospective Payment System. The physician who provided the care bills a professional claim on the CMS-1500, coded with ICD-10-CM diagnoses and CPT.

    Both claims come from one encounter and one body of documentation. In many hospitals, they're still coded by separate teams working separate queues, often in separate systems.

    Single-path coding brings the two sides together. Facility and professional coding work from the same record at the same time, so the encounter is read once and coded consistently on both claims.

    Where Single-Path Coding Applies

    Single-path coding fits encounters where the hospital and the physician both bill for the same visit. Emergency department visits are the most common example. A hospital-based ED visit generates a facility claim for the hospital's resources and a professional claim for the emergency physician's evaluation and management, both of which depend on the same ED record.

    Outpatient procedures follow the same pattern. When a procedure is performed in a hospital outpatient department, the hospital codes the facility side, and the physician's work is coded on the professional side, often from the same procedure note.

    What Separate Queues Cost

    When facility and professional coders work apart, each team reads the same chart on its own schedule. An emergency department visit or an outpatient procedure gets reviewed twice, and the work isn't shared between the two passes.

    The codes can also drift. A facility coder may capture a diagnosis or procedure that the professional coder doesn't, or code it at a different level of specificity. Payers and auditors can see both claims, and codes that don't line up between them invite questions that someone has to answer later.

    Timing adds friction as well, because when one side is waiting on a query or a late note, the other side often waits too, even when its own coding is ready and the claim could already go out.

    Modifiers and diagnosis linkage add risk on both sides. When an E/M service and a procedure happen on the same day, modifier 25 may be needed on the facility claim, the professional claim, or both, depending on the documentation. Every CPT code also needs a diagnosis that supports medical necessity. When each team makes those calls separately, one claim can pass while the other is denied for the same encounter.

    How Single-Path Coding Works

    InstaCode presents the facility and professional records for an encounter together, in one workflow, and codes both from the same documentation. Diagnosis and CPT codes carry across both records, so the two claims stay consistent from the start.

    The rules that differ between the two sides still apply. In the emergency department, for example, facility E/M levels follow each hospital's own internal guidelines, while professional E/M levels follow CPT guidelines. Single-pass keeps the shared codes aligned while leaving each side's rules in place.

    Each side can also move at its own pace. When the professional claim is complete, it can be finished and submitted without waiting on the facility claim, and vice versa.

    Service Models that Fit the Team

    InstaCode is offered through autonomous, hybrid, and fully managed service models, so health systems can match the model to their coding team's size and goals.

    In the autonomous model, charts that meet the customer's thresholds move forward, and the rest are routed to the health system's own coders. In the hybrid and fully managed models, DeliverHealth's coding team handles exceptions, giving organizations with tight staffing a way to keep coding moving without routing that work back to their own staff.

    Confidence Routing That Each Health System Approves

    InstaCode routes charts by confidence. Thresholds are set for each customer and by coding type, and each customer signs off on them. Only charts that meet defined quality and confidence thresholds are released directly to billing. All others are routed for further review.

    Coding leaders decide where the line sits and can adjust it over time. Automation follows the accuracy standard the organization sets, which is the right order for a coding program. For more on that distinction, see why automation rate isn't accuracy rate.

    Starting From The Documentation You Already Have

    InstaCode codes from documentation in any source, including notes from a hospital's existing EHR workflow or another ambient documentation tool. Single-path coding doesn't require a change to how physicians document.

    For organizations that also use InstaNote, the record arrives more complete. InstaNote supports dictation and ambient capture, and its CDR feature reviews the draft note before sign-off, so documentation gaps are more likely to be resolved before the chart reaches coding.

    What To Measure

    Coding leaders weighing a change to their outpatient workflow can track a few measures before and after. Coding turnaround shows how long encounters wait between documentation and a final code. Touches per encounter show how many times a chart is opened before both claims are complete. Diagnosis agreement between facility and professional claims shows whether both sides describe the encounter the same way. Coding-related denials, separated by facility and professional, show where the remaining risk sits.

    A baseline on these measures makes the impact of any coding change easier to see, whether or not single-path is part of it.

    Question to ask when evaluating single-path coding

    When single-path comes up in a vendor evaluation, these questions help confirm that the facility and professional sides share one workflow:

    • Are the facility and professional records presented together, or does each side open the chart separately?

    • Do diagnosis and CPT codes carry across both records automatically?

    • Can one side submit when it's ready, without waiting on the other?

    • How are charts below the confidence threshold handled, and who reviews them?

    • Does the system code from documentation produced in other tools, or only its own?

    Frequently asked questions

    What is single-path coding?

    Single-path coding is a workflow in which the facility and professional claims for an encounter are coded together from the same record. Codes that apply to both sides carry across, and each side can still be completed and submitted on its own timeline.

    Does single-path coding replace coders?

    No. Coders validate the work and handle charts that fall below the confidence thresholds each health system sets. Single-path changes how the chart reaches them, with both records together, so they aren't reading the same encounter twice.

    Does single-path coding require a specific documentation tool?

    No. InstaCode codes from documentation in any source, so single-path doesn't depend on how the note was created. Organizations using InstaNote also get CDR reviewing the draft note before sign-off.

    Coding the encounter from one record

    Outpatient volume is high, and coding every encounter twice adds up over a coding team's week. Coding both sides from the same record at the same time gives facility and professional coders a shared starting point and keeps both claims aligned with the care.

    To see how single-path coding fits your outpatient workflow, book an InstaCode demo.

    Tags

    medical coding
    autonomous medical coding
    outpatient facility coding
    ED facility coding
    professional coding
    single-path medical coding

    Stay Updated

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