Epic EMR Workflow for Charge Capture, Infusions, Modifiers, and Clean Claims (2026)

Revenue leakage in hospital outpatient settings often starts small, then snowballs, a missed injection charge here, an unsupported supply there. Real-world estimates put outpatient leakage in the 10 to 30% range, and a big share traces back to missed or weak charge capture.

As a charge capture specialist, you're the bridge between what happened in care and what makes it onto a compliant claim. You're not just chasing charges, you're protecting revenue while keeping the record defensible.

In this post, you'll follow a step-by-step epic emr workflow you can use daily, from charge review through edits and final claim readiness. Guidelines matter, but they're only half the story, because documentation decides what you can code, what you can bill, and what you'll have to write off.

You'll also see the common problem zones that cause the most rework, infusions, modifiers, charge edits, and status changes (including Condition Code 44). By the end, you'll know what to check, where to click, and what to confirm before a claim ever leaves your system.

Start your day in Epic with a plan, not a hunt: dashboard, workqueues, and your priority rules

An at-a-glance charge capture dashboard view to set daily priorities.

If your first hour is spent searching for problems, your day will feel like rework. A consistent Epic EHR workflow starts the same way every morning:

check the Revenue Excellence view (or your charge capture dashboard), then go straight into the right workqueues (WQs). That order keeps you focused on risk, not noise.

Use a simple, repeatable order of operations before you open a single chart:

1. Start in the dashboard to spot volume, lag, and anything spiking today (missing charges, charge router errors, rising hold counts).

2. Sort your priority list by dollars and aging first, then by clinical area (OR, ED, infusion), then by provider or location.

3. Enter workqueues with a purpose, clearing the highest-risk items before you touch routine volume.

For broader context on what strong Epic governance looks like (ownership, assignment, monitoring), see this independent review on Epic workqueue oversight practices.

Set up work queues that surface high-risk charges first

Workqueues organized by status and risk so you can start with the most urgent items

A good WQ setup works like triage. You want your highest financial and denial risk at the top, every time, without extra clicks. Start by separating queues by service risk and timeliness risk, then apply sorting rules that match how denials happen in real life.

Prioritize WQs in this order so the biggest exposure clears first:

• High-volume areas: ED and infusion, because small misses repeat all day. A minor charge issue becomes a weekly trend fast.

• High-aging accounts: Older dates of service need attention first, because payer filing limits and timely filing edits do not care how busy your day was.

Within each WQ, sort your columns so your eyes land on the right work first:

• Days since service date (oldest first)

• Department or clinical area (to batch similar work)

• Provider and location (to spot training issues and repeat patterns)

Watch for common status cues that tell you why the item is stuck. Your labels may vary by build, but the patterns are consistent:

• Unsubmitted: Charges exist but have not dropped to the claim flow yet, often a routing or completion issue.

• Charge edit: Something failed edits, such as required fields, charge-router rules, or a mismatch between documentation and charge detail.

• Pending: Waiting on another step, such as documentation completion, order closure, or reconciliation.

• Held: Intentionally stopped, usually due to compliance review, missing medical necessity support, or an authorization concern.

A quick, practical move is to add specialty filters so you only see what matters to your service line. For example, filter to cardiology to isolate cath lab items (devices, contrast, additional procedure lines), or filter to oncology to keep infusion drugs and admin charges together. When you keep the view tight, you stop bouncing between unrelated work and you make fewer mistakes.

Build your "My List" views so you stop missing specialty-specific charges

Workqueues help you clear problems, but "My List" views help you prevent misses. Think of "My List" as your personal control panel inside Epic. When it is set up well, it pulls the same high-signal encounters to you every day, so you do not rely on memory or inbox luck.

Keep personalization simple and consistent. Build a few saved views using:

• Saved filters (service area, encounter type, charge status, aging buckets)

• Favorite departments (ED, infusion center, cath lab, OR)

• Provider lists (high-volume surgeons, cardiologists, oncologists)

• Location-based views (main campus vs. freestanding infusion, hospital-based clinics)

Here are two examples that reduce specialty misses quickly:

• Oncology (Beacon infusions): A "My List" view filtered to infusion locations and oncology providers helps you catch drug waste, missing admin time, and same-day add-ons before they age into a research project.

• Surgery (OpTime supplies and implants): A view tied to surgical departments and key surgeons helps you spot late implant documentation, missing device detail, and supply charges that did not route correctly.

The real win is repetition. Use the same "My List" views daily, then only adjust when the build changes or your service line shifts. Consistent views reduce rework because you stop re-learning where work is hiding, and you start recognizing patterns (the same location, the same provider, the same missing field) before they turn into denials.

Bridge Clinical Care to Billable Charges: Your Chart Review Checklist Inside the Epic EMR Workflow

Charge review is not about "adding codes." It's about validating what actually happened and making sure the EpicCare record supports what dropped (or should have dropped) to charges. In facility-outpatient billing, small mismatches cause big problems because payers compare your claim lines to timestamps, locations, and clinical proof.

Your safest mindset is simple: orders, results, and documentation must tell the same story. When they don't, you either fix the record (if appropriate and within policy) or you fix the charge path before the claim leaves. This is the part of an epic ehr workflow where accuracy beats speed, because one preventable denial can take longer than ten clean reviews.

If you can't point to where the service happened, who did it, and when it occurred, you don't have a strong billable story, even if the charge exists.

Confirm the encounter story: note, orders, results, and where the patient actually was

Denials often start with a simple contradiction. The claim says a procedure happened in one department, but the chart shows the patient never arrived there. Or an order exists, yet there is no completion evidence. The payer reads that as "not performed" or "not supported," and you inherit the rework.

Start by confirming the encounter foundation in EpicCare. You want a single, coherent timeline across the clinical note, order activity, results, and nursing documentation. Then you want that timeline to match the charge's service department and place of service.

1. Encounter details match the visit type: Verify the correct account, date of service, and encounter type (ED, clinic, hospital outpatient, observation-linked outpatient, etc.).

2. Patient location history supports the department billed: Check event management and location history so the patient's movement (arrival, transfers, discharge) lines up with the department tied to the charge.

3. Orders show the right status: Look for performed, completed, administered, resulted, or canceled. An "ordered" item without completion proof is a denial magnet.

4. Clinical documentation supports medical necessity and performance: Confirm the provider note or procedure note describes what was done, why it was done, and who did it.

5. Results back up the work: Imaging results, lab results, monitoring strips, or interpretation notes should exist when the service requires them.

6. Charge department matches where care occurred: If the patient was in ED but the charge is tied to a clinic department, you can trigger a mismatch edit or a payer rejection.

Three high-frequency mismatch patterns to watch for:

• Procedure ordered but not performed: You see an order for a test, but it was canceled, no-showed, or never completed. If a charge dropped anyway, it's exposed.

• Procedure performed but not documented: Nursing notes hint it happened ("tolerated well"), but the procedure note is missing. You may need documentation completion before you can support the charge.

• Performed in a different location than charged: This is common with imaging, bedside procedures, and shared spaces. The patient might be physically in one unit, while the performing department is another. If the service department does not reflect how your facility bills, edits and denials follow.

When you spot a mismatch, treat it like a broken chain. Don't jump straight to "remove the charge" or "add the charge." Instead, confirm what the record can defensibly support, then correct the routing or department mapping if that is the real issue. Industry summaries of frequent breakdowns match what you see every week, especially around missed steps and inconsistent documentation (common charge capture errors and fixes).

Spot missing charges in high-cost areas: supplies, implants, pharmacy, and bedside procedures

High-cost areas are where charge capture problems hurt the most, and they are also where clinical logs often tell you more than the billing view. If you only look at what dropped to the charge router, you can miss expensive items that never made it out of the clinical workflow.

Your goal is to compare two worlds:

• Clinical proof (procedure notes, implant logs, medication administration, nursing documentation)

• Charging output (what routed, what held, what failed edits, what never generated)

That keeps you from scanning everything and confirming nothing.

Here are common "quiet misses" you can catch fast:

• Implants documented in OpTime but absent in charges: The implant log shows device name, lot/serial, laterality, and quantity, but the charge router has no matching item, or it routed to the wrong revenue code. This can happen when preference cards change, items are substituted, or the item master mapping breaks.

• High-cost meds administered in Beacon but not billed: Look for administered doses, start/stop times, and waste documentation. Then confirm the drug charge and the admin charge both dropped. Missing waste documentation, mismatched NDC mapping, or incomplete MAR events can block the bill.

• Bedside ultrasound performed and documented, but no technical charge: The provider note may describe a point-of-care ultrasound (POCUS) with findings. If your facility bills technical components for certain bedside imaging, confirm that the performing department, equipment workflow, and result pathway support the charge.

• Stress tests and monitoring services missing interpretation linkage: You might see the test performed, but the interpretation note (or final report) is not in place. Some builds hold charging until a result posts, so a missing final can look like "no charge," when it's really "charge waiting."

To keep your review tight, use a quick three-point reconciliation for expensive items:

1. Find the clinical log: implant log, MAR, procedure note, or device documentation.

2. Match it to a charge line: same date, correct quantity, expected department, and appropriate status (not stuck in pending).

3. Confirm it hit the right route: if it dropped, verify it didn't land in the wrong service department or on the wrong account.

When this comparison becomes routine, you stop chasing rumors like "the system didn't charge." Instead, you can name the failure point (documentation, routing, department build, or status). If you want consistent language for these problems when you message clinical teams or analysts, a shared glossary helps, especially for terms like charge router, hard stops, and late charges (charge capture terms guide).

For more on EPIC charge capture visit our Epic home page

Also stop by our IV Infusion homepage