top of page

Understanding Epic's Medication Administration Record (MAR) for Billing and Coding

  • Writer: Alexis Wilkinson CPC
    Alexis Wilkinson CPC
  • Jan 9
  • 7 min read

Updated: Apr 1

What is the Epic Mar?

The Epic Medication Administration Record (MAR) is a real-time clinical document that tracks every medication, fluid, and dose administered to a patient within the EMR. For medical coders, it serves as the essential evidence for charge capture, providing the start times, stop times, and administration routes required to assign accurate CPT codes.

A document that is frequently misunderstood by revenue cycle professionals.


This guide provides medical coders with a strategic, defensible framework for reviewing the Epic MAR not as a billing sheet, but as clinical evidence that must be analyzed, validated, and translated into compliant CPT codes.

To do that effectively, coders must first understand what the MAR was designed to do and what it was not.


The MAR Is a Clinical Tool, Not a Billing Sheet

What is thew MAR in Epic

The MAR exists to support patient safety and clinical workflow, not billing convenience. Epic’s medication workflows especially those integrated with IV smart pumps are designed to reduce medication errors, improve clinical outcomes, and streamline nursing documentation.

The presence of medication safety integration nurses and clinical informatics teams proves that the MAR is built by clinicians for clinicians, prioritizing patient safety over billing convenience.


This means that the people who design and manage the MAR. specialized nurses and clinical IT experts are focused on preventing medication errors and streamlining nursing workflows. Not on making sure a bill is generated.


Because the MAR is a clinical "safety net" created by healthcare providers rather than the finance department, medical coders must treat it as a clinical record that requires careful translation into billing codes, rather than a simple automated receipt.


Billing is a secondary downstream function, not the MAR’s primary purpose. This disconnect is the root cause of many potential billing issues seen when the MAR is treated as a standalone charge document. The key mindset shift for coders is this: the MAR supports billing, but it does not replace critical documentation review and analysis.

This becomes especially important when automated documentation is involved.


Automated vs. Manual Documentation

Epic leverages bidirectional IV smart pump interoperability, This "mess" on the MAR is a direct result of bidirectional auto-documentation. Because the IV pump and Epic are talking to each other in real-time, every technical change at the bedside becomes a permanent data point in the medical record.



Here is how that process creates a "mess" for medical coders:


  1. Technical Stops vs. Clinical Stops

    When a patient moves their arm and causes an "occlusion" (a kink in the tubing), the smart pump detects that fluid has stopped moving and sends a "Stopped" signal to Epic. Even if the nurse fixes it 30 seconds later, the MAR now has a hard "Stop" and a new "Start" time. To a coder, this looks like the infusion ended and a new one began, even though the clinical intent was one continuous service.

  2. Fragmentation of Data

    Instead of seeing a clean "Start: 0800, Stop: 1200" for a 4-hour infusion, the auto-documentation might create 10 or 15 different segments if the patient was restless, the pump was paused for a bathroom break, or the tubing was adjusted. This fragments the documentation into "micro-segments" that the coder must manually add together to reach the total billable time.


  3. The "Acceptance" Workflow

    In Epic, these auto-documented times often sit in a "pending" state (sometimes called the Pump Rate Verify tool) until a nurse clicks "Accept." If a nurse is busy and accepts 10 different pump pauses all at once at the end of their shift, the MAR becomes a wall of timestamps that are technically accurate but clinically cluttered.



Why this is a "Mess" for Coding:

  • Duration Calculation: Coders have to play "math detective," subtracting the gaps between every stop and restart to see if the patient actually hit the 31-minute threshold for an initial hour or the 61-minute threshold for an additional hour.

  • Audit Risk: If an auditor sees 10 stop/starts but only one "initial" charge, they may question if the infusion was actually "interrupted" rather than "continuous."

  • Visual Noise: The MAR becomes so long that it is easy to miss a real clinical stop (where the medication was actually discontinued) because it’s buried under dozens of technical "pauses."


  • Finding the Right MAR View in Epic

Before analyzing charges, coders must ensure they are viewing the correct MAR display. This is typically accessed under Chart Review through Flowsheets or under Medications by selecting the MAR in Doc Review tab.

Coders should avoid summary “given/not given” views and instead use detailed options such as MAR with Details, MAR Timeline, or the IV Summary. Required display elements include start and stop times, infusion rate, volume infused or remaining, and route and method such as IV push, IV piggyback, or IV infusion. Without these elements, compliant IV coding is not possible.


Why the MAR Is Never Enough


Orders establish provider intent and must align with MAR administration. Flowsheets often contain critical data such as vitals, titration changes, and infusion adjustments that are not visible on the MAR. Clinical notes from nurses and providers explain the clinical rationale, patient response, complications, or early discontinuation. A high-cost medication appearing on the MAR without narrative support elsewhere represents a significant compliance risk.

Pro-Tip: Orders Must Align with the MAR

Never bill based on the MAR alone if the duration contradicts the provider’s intent. For example, if a physician orders 1,000 mL of Lactated Ringers to run at 999 mL/hr, the clinical intent is a one-hour infusion. If the MAR shows a stop time four hours later, it is often because the nurse forgot to "stop" the pump in Epic, not because the patient received four hours of hydration. You cannot bill for the extra three hours just because the nurse didn't click "stop"—you must code for the one hour that was actually ordered and delivered.


The 5-Step MAR Dissection Process for IV Charge Capture

Once the correct MAR view is confirmed and corroborating documentation is identified, coders should apply a consistent analysis process to every IV medication and fluid.


Step 1: Identify True Billable Administrations

Focus on IV pushes, IV piggybacks, IV infusions, and IM or subcutaneous injections. Exclude oral, topical, inhaled medications, flushes, reconstituting agents, and PRN medications that are not linked to a procedure or billable service.


Step 2: Determine the Drug and Actual Dose Given

Coders must bill what was administered, not what was ordered. More on how to tell the difference For example, if Vancomycin 1 gram in mL 125 was ordered but only 125 mL was infused, only 500 mg was given.


Step 3: Determine Route, Method, and Duration

Duration drives infusion coding. Coders must confirm whether the medication was given as an IV push, piggyback, or infusion and identify start and stop times. If a stop time is missing, the rate and volume may allow duration calculation. If duration cannot be verified, assumptions are not permitted and a query is required per facility protocol.


All IV services must be placed on a timeline. There is no one way to create the timelinE. Personal I brake it up into groups of administration and then by day. To get a complete visual of how I break it down check out "The MAR" on our webpage.


Step 5: Final Medical Necessity and Payer Review

Services must be reviewed against diagnosis and payer-specific rules. Emergency department hydration may be billable for intoxication, magnesium sulfate is billable for pre-eclampsia, and IV fluids during routine labor may be bundled. Medical necessity must always be defensible.


High-Risk MAR Scenarios That Demand Extra Scrutiny

Certain medication scenarios require heightened attention, including titratable infusions with undocumented rate changes, early discontinuation due to reactions or infiltrations, automated MAR entries without supporting clinical notes, and encounters flagged for manual review by autonomous coding systems. If automation identifies a case as non-standard, it warrants careful human analysis.

Accurate documentation in the Epic Medication Administration Record (MAR) is critical for patient safety, compliance, and reimbursement accuracy. As we’ve discussed above, capturing the right details including time, route, dose, and clinician verification helps reduce clinical and coding errors in infusion and medication administration workflows.


For further clinical context on safe medication administration practices and evidence-based standards, you may find this resource helpful: https://pmc.ncbi.nlm.nih.gov/articles/PMC10757236/


FAQ


1. What is the Medication Administration Record (MAR) in Epic?

The Medication Administration Record (MAR) in Epic is the primary source for tracking medication administration details, including drug name, dose, route, and exact administration times. For medical coders, the MAR is essential for validating infusion, IV push, and hydration services.

2. Why is the MAR important for medical coding?The MAR directly supports charge capture by providing:

The MAR directly supports charge capture by providing:

  • Start and stop times for infusions

  • Medication routes (IV, IV push, oral, etc.)

  • Administration sequence

Without accurate MAR documentation, coders cannot assign the correct CPT codes.


3. Can coders rely on the MAR alone for coding?

No coders must use the MAR in combination with provider documentation.The MAR confirms what was done and when, while the provider note confirms why it was done (medical necessity).

To learn more about medical necessity go here.

4. Where do you find infusion start and stop times in Epic MAR?

In the Epic MAR, start and stop times are captured as discrete timestamps within the medication administration details. These data points are the regulatory "anchor" for infusion coding, as they provide the objective evidence required to calculate:

  • Total Infusion Duration: The exact number of minutes the medication was flowing, which is used to meet the CPT® "greater than 30 minutes" threshold for an initial hour.

  • Initial vs. Additional Hour Codes: Verification of whether the service crossed the 61-minute, 121-minute, or subsequent hour marks.

  • Sequential vs. Concurrent Timing: The relationship between multiple infusions, allowing coders to determine if drugs were administered one after another or simultaneously.

 Without these precise timestamps, a coder cannot legally substantiate a time-based claim, and the service must typically be downcoded to an IV push or queried for clarification.






bottom of page