No products in the cart.
MODULE 23: VENDOR-SPECIFIC LAB – MEDITECH EXPANSE
Section 23.3: eMAR and Bedside Verification (BCMA)
Focus on the point of administration. We’ll explore the configuration of the electronic MAR, nursing documentation workflows, and the technical setup for Barcode Medication Administration within the Expanse platform.
SECTION 23.3
eMAR and Bedside Verification (BCMA)
Engineering the Last Five Feet of Medication Safety.
23.3.1 The “Why”: The Final, Unforgiving Checkpoint
In your pharmacy career, you have served as a critical node of safety. You have caught ambiguous orders, incorrect doses, and critical drug interactions, all before the medication ever left the pharmacy. This cognitive, clinical verification is an indispensable part of the medication use process. However, studies have consistently and sobering shown that despite our best efforts, a significant percentage of medication errors do not occur at the point of prescribing or dispensing; they occur at the point of administration. The wrong patient grabbing the wrong medication from a nursing station counter. A miscalculation of a liquid dose drawn up in a hurry. A simple mix-up between two patients in a semi-private room. These are the errors that happen in the “last five feet”—the physical space between the nurse and the patient.
Before the widespread adoption of EHRs, the Medication Administration Record (MAR) was a paper document, often riddled with transcription errors from the original order. The only check at the bedside was the nurse’s own vigilance. This placed an immense and unfair cognitive burden on the nursing staff, asking them to be perfect 100% of the time in a high-stress, interruption-prone environment. It was a system destined to fail.
The Electronic Medication Administration Record (eMAR) and Barcode Medication Administration (BCMA) were created to solve this specific problem. Together, they form a powerful, technology-enabled safety net designed to make it easy to do the right thing and hard to do the wrong thing at the patient’s bedside. The eMAR provides a clear, real-time, unambiguous list of what is due for the patient, eliminating transcription errors. BCMA then acts as the physical enforcer of the “Five Rights,” using barcodes to electronically confirm that the right drug is being given to the right patient at the right dose and right time via the right route.
As a Pharmacy Informatics Analyst, your work on the preceding stages—building the formulary and designing the CPOE process—all culminates here. This is the final expression of all your careful build. If the foundation is flawed, the BCMA system will either fail to work or, worse, create new, unforeseen safety gaps. You are not just building a system for nurses to click buttons; you are architecting a high-reliability safety process. You must become an absolute expert in the nursing medication administration workflow. You need to understand their challenges, anticipate their needs, and build a system that is not a barrier to care, but a seamless, intuitive, and trusted partner in ensuring patient safety.
Pharmacist Analogy: The Airline Boarding Gate
Imagine you are the systems architect for a major airline. You’ve already done the backend work: you’ve defined every airplane in your fleet (the PHA Drug Dictionary), you’ve created the customer-facing website for booking flights (the CPOE Catalog), and you’ve issued tickets to passengers (the Verified Pharmacy Order). Now, you must design the process for the most critical moment of truth: getting the right passengers onto the right plane.
The Passenger Manifest (The eMAR): The gate agent has a computer screen that shows a list of every passenger scheduled for Flight 123 to Denver. This is the eMAR. It’s a real-time list of all the “medications” (passengers) due to be “administered” (boarded) for this “patient” (flight). It’s clear, unambiguous, and directly linked to the tickets you issued.
The Boarding Pass (The Medication Barcode): Each passenger holds a boarding pass with a unique barcode. This is the medication barcode (NDC). It contains specific information: this is John Doe, Seat 14B, Flight 123.
The Passenger’s ID (The Patient Wristband): To board an international flight, you need to show your passport. This is the patient’s wristband barcode. It confirms, irrefutably, the identity of the person holding the ticket.
The Gate Agent’s Scanner (The Nurse’s Scanner & BCMA Logic): The gate agent (the Nurse) is the final checkpoint. They perform a series of scans:
- They scan the passenger’s passport (patient wristband). The system confirms this is John Doe.
- They scan the passenger’s boarding pass (medication barcode). The system then performs a series of checks against the manifest (eMAR):
- Is John Doe on the list for this flight? (Right Patient?) – YES.
- Is this boarding pass for Flight 123 to Denver? (Right Drug?) – YES.
- Is the flight boarding now? (Right Time?) – YES.
If all checks pass, the scanner beeps green: MATCH. The passenger boards. But what if there’s an error?
- A passenger for Flight 456 to Chicago tries to board. The scanner beeps red: FAIL – WRONG MEDICATION.
- A passenger for the same flight to Denver, but scheduled for tomorrow, tries to board. The scanner beeps red: FAIL – WRONG TIME.
The system doesn’t rely on the gate agent to remember every passenger’s face. It enforces the rules. As the analyst, you built this entire system. You linked the tickets to the manifest, you designed the barcode format, and you programmed the logic into the scanner. Your work is what prevents a passenger from ending up in the wrong city, just as it prevents a patient from receiving the wrong medication.
23.3.2 Deconstructing the eMAR: The Nurse’s Digital Command Center
The eMAR is far more than a simple list. It is a dynamic, interactive dashboard that serves as the central hub for the nurse’s medication-related tasks. It synthesizes data from pharmacy, laboratory, and provider orders into a single, actionable view. As an analyst, you have significant control over how this information is presented. A well-configured eMAR is clean, intuitive, and prioritizes information effectively. A poorly configured eMAR is cluttered, confusing, and can hide critical information in plain sight.
The goal of eMAR design is cognitive offloading. You want the system to handle the organizational tasks—sorting by time, flagging what’s overdue, showing related lab values—so the nurse can focus their mental energy on clinical assessment and patient care, not on administrative bookkeeping.
Masterclass Table: Key Configuration Areas of the MEDITECH eMAR
| Configuration Area | Description & Purpose | Key Analyst Decisions & Clinical Impact |
|---|---|---|
| Medication Sorting & Grouping | This determines the default order in which medications are displayed. Common options include sorting by scheduled time, by drug name, or by drug class. Meds can also be grouped into categories like “Scheduled,” “PRN,” and “Continuous.” |
Decision: Should the primary sort be by Time or Drug Name?
Impact: Sorting by time is the universal standard and safest approach. It creates a clear, chronological to-do list for the nurse (e.g., “Here are all my 09:00 meds”). Sorting alphabetically might seem logical but can cause nurses to miss doses if they don’t scroll through the entire list for each time slot. |
| Display Columns | You can choose what data points are displayed as columns on the main eMAR screen. This includes basics like Drug, Dose, Route, and Frequency, but can be expanded to include many others. |
Decision: Should we add a column for “Last Administered Time” or “Associated Lab Value”?
Impact: Adding “Last Admin Time” is critical for PRNs to prevent re-dosing too early. Adding a column for “Last INR” next to the Warfarin order, or “Last K+” next to a potassium replacement order, provides vital context directly in the workflow, preventing the nurse from having to hunt for it elsewhere in the chart. This is a powerful safety enhancement. |
| Status Indicators & Color Coding | The eMAR uses visual cues to communicate the status of a dose. You can configure the colors and icons used to represent “Due,” “Overdue,” “Given,” “Held,” or “Refused.” |
Decision: What color should an overdue medication be? How long after its due time should it turn that color?
Impact: A bright, unmissable color (like red or orange) for overdue meds is essential for patient safety. Setting the “overdue” trigger time requires balancing clinical urgency with operational reality. Setting it too short (e.g., 5 minutes past due) will create constant “red flags” for nurses who are simply busy, leading to alert fatigue. A more reasonable window (e.g., 61 minutes for a scheduled med) is standard. |
| Required Documentation Fields | For certain medications or routes, you can build rules that require the nurse to document specific information. |
Decision: For all PRN pain medications, should we require the nurse to document a pain score (1-10) before and after administration? For insulin, should we require documentation of the injection site?
Impact: This enforces best practices and captures critical clinical data. Requiring a pain score ensures proper assessment of medication efficacy. Requiring injection site documentation for insulin helps promote site rotation and prevent lipohypertrophy. |
23.3.3 The Engine of Safety: Barcode Medication Administration (BCMA) Workflow
BCMA is the active, enforcing component of the system. While the eMAR is the plan, BCMA is the execution and verification. The workflow is deceptively simple in concept but requires a tremendous amount of backend build to function flawlessly. The entire process is a series of database lookups happening in milliseconds, comparing the data encoded in three physical barcodes against the verified pharmacy order stored in the patient’s profile.
The BCMA Closed Loop Medication Process
1. Scan Nurse Badge
System authenticates the user.
2. Scan Patient Wristband
System opens the correct eMAR.
3. Scan Medication
System looks up the NDC.
MEDITECH System Logic Check
Does the scanned NDC link to a PHA drug that matches an active, verified order on this patient’s eMAR that is due within the allowed time window?
YES: Success
System allows nurse to proceed to documentation and administration.
NO: Error
System generates a specific alert (Wrong Drug, Wrong Time, etc.) and HALTS the process.
23.3.4 The Analyst’s Critical Role in BCMA Configuration
The BCMA process appears simple to the end-user, but this simplicity is the result of intensely detailed and careful configuration work by the informatics team. Your build decisions in the background directly determine whether the process is safe and efficient or cumbersome and prone to workarounds. Every click saved for a nurse, multiplied by thousands of administrations per day, adds up to a significant return in time spent on direct patient care.
The First Rule of BCMA Build: Go to the Gemba
In manufacturing, “Gemba” is the principle of going to the actual place where work is done to see the process for yourself. This is the most important, non-negotiable rule for a pharmacy informaticist. You cannot effectively build the eMAR and BCMA workflows by sitting at your desk. You must shadow nurses on different units during their medication administration rounds. Watch their process. Where do they struggle? What takes them the most time? What workarounds are they using? Seeing a nurse have to walk back to the nursing station to get a different scanner because the one in the room is broken, or watching them struggle with a medication that won’t scan, will teach you more about what needs to be fixed than any meeting or report ever could.
Masterclass Table: Advanced BCMA Configuration Scenarios
| Scenario | The Clinical Challenge | The Analyst’s Build Solution |
|---|---|---|
| Titratable IV Infusions | A patient is on a Heparin drip ordered to be titrated to a target aPTT. The nurse needs to adjust the rate frequently based on lab results. How does the system handle this without requiring a new pharmacy order for every rate change? | This requires a special build. You create an IV record that is flagged as “Titratable.” In the order, you define the starting rate, but also the allowed min/max rate and the titration parameters (e.g., “Increase/decrease rate by 2 mL/hr to keep aPTT between 60-80”). This empowers the nurse to make rate changes within the protocol’s guardrails, with each change documented on the eMAR, without needing a new order each time. |
| Multi-Dose Vials / Oral Syringes | A nurse needs to administer 7.5 mL of a liquid antibiotic from a 100 mL stock bottle. The stock bottle has one barcode. How does the system know that only 7.5 mL was given and not the whole bottle? | The PHA record for the liquid is built with a flag indicating it is not a “unit dose.” When the nurse scans the bottle, the BCMA system will prompt them: “Enter Volume to be Administered.” The nurse must then manually enter “7.5”. The system will validate if this volume calculates to a reasonable dose. This creates the necessary documentation and inventory tracking for non-unit dose items. |
| Medication Waste | A patient is ordered Morphine 2 mg IV. The pharmacy dispenses a 4 mg vial. The nurse must administer 2 mg and waste 2 mg. This waste must be documented and, for controlled substances, witnessed by another licensed professional. | This is a complex workflow build. After the nurse documents the 2mg administration, the system will trigger a required “Waste” documentation screen. The nurse enters the amount wasted (2 mg). The system then prompts for a second user’s credentials (username/password or badge scan) to electronically “co-sign” and witness the waste. All of this is logged in a non-editable audit trail. |
| BCMA Downtime | The hospital network goes down. BCMA is unavailable, but medications must still be given safely. What is the plan? | This is a critical operational and informatics responsibility. You must help design and maintain the BCMA downtime procedure. This typically involves printing a real-time “Downtime MAR” for each patient from the system just before the planned outage (or as soon as an unplanned one occurs). Nurses then revert to paper documentation. Your role is to ensure these downtime reports are accurate, readable, and that a process exists for back-entering the administrations into the eMAR once the system is restored. |
23.3.5 The Double-Edged Sword: Override Management and Reporting
No system can account for every possible clinical scenario. In a true, life-threatening emergency—a patient coding, a rapid sequence intubation—a nurse cannot be expected to wait for a pharmacy order to be entered and verified before administering a life-saving drug from a crash cart. For this reason, the BCMA system must have an override function. This allows a nurse to bypass the standard BCMA checks, document the administration, and move on. However, this is the most powerful and potentially most dangerous feature of the system.
An override essentially removes all the electronic safety checks you have so carefully built. It is a necessary evil. When used appropriately, it saves lives. When used inappropriately—as a workaround for a missing pharmacy order, a faulty scanner, or a drug that wasn’t delivered on time—it systematically undermines the entire culture of safety that BCMA is meant to create. Your role as an analyst is to manage this delicate balance: enable emergency access while discouraging and monitoring inappropriate use.
The Normalization of Deviance
The single greatest threat to a successful BCMA implementation is the “normalization of deviance.” This happens when workarounds, like overusing the override feature, become so common that they are seen as the normal way of doing things. A nurse might think, “It’s faster to just override this saline flush than to wait for pharmacy to enter the order.” One person does it, then another, and soon the entire unit is routinely bypassing a key safety check. This is why your role in monitoring override data is not just a technical task; it is a critical patient safety function. You are the system’s watchdog, responsible for identifying these trends before they become entrenched and lead to a preventable error.
The Analyst’s Override Management Playbook
- Build a Thoughtful Override Reason List: When a nurse overrides, they must select a reason from a pre-defined list. You will build this list. It should include legitimate reasons (“Code Blue,” “Procedural Sedation,” “Patient Deteriorating”) but should avoid ambiguous options like “Other” or “Pharmacist instructed.” The goal is to collect structured, actionable data.
- Configure High-Risk Drug Restrictions: Certain medications are so dangerous that they should never be administered without the full scrutiny of the CPOE-Pharmacy-BCMA loop. You can and should configure the system to make certain drugs, like chemotherapy, TPN, or IV insulin, non-overridable.
- Develop and Monitor Override Reports: This is your most powerful tool. You must build and regularly run reports that show every single override event in the hospital. This report is your diagnostic tool for the health of your medication safety culture.
- Analyze the Data and Ask “Why?”: Look for trends in the report. Is one nurse overriding far more than others? Is one specific drug constantly being overridden on a particular unit? This data tells a story. An individual may need re-education. A drug being constantly overridden may indicate a flaw in the pharmacy’s delivery workflow or a broken CPOE order that needs to be fixed. Don’t just report the numbers; investigate the root cause. Your analysis is what turns raw data into meaningful quality improvement.
