🏥 Clinical Systems Adoption Portfolio

Closing the Loop:
Alaris Pump + Epic
Integration Excellence

I'm Alicia Paulson, a public health professional (BDS, MS) currently working on BMC's M3W Surgical Step-Down Unit. I use Epic every day on the floor. This portfolio shows how I'd bring that firsthand clinical experience to the Alaris IV pump integration as a Clinical Systems Adoption Specialist at Boston Medical Center.

0%
Pump Auto-Programming Adoption Target
0%
Reduction in Manual Programming Errors
0 wks
Full Adoption Timeline
Integration Status
Epic ↔ Alaris Pump · Live Feed
Scan Patient
Patient ID Band · Epic eMAR
Scan Medication
5 Rights Check · Barcode Verification
Scan Pump
Alaris Barcode · Channel Association
Send Details to Pump
HL7/FHIR · Auto-Programming
Start Pump
DERS Guardrails Enforced · Infusion Begins
Validate Pump Data in Epic
MAR Auto-Documentation · Complete

The Case for Alaris–Epic Integration

Bidirectional infusion pump interoperability eliminates manual transcription, enforces drug-library guardrails, and closes the medication loop in real time. The result is less harm, a lighter cognitive load for nurses, and more time for direct patient care.

🛡️

Patient Safety First

Alaris DERS guard rails prevent under- and over-infusion. Auto-programming eliminates the #1 source of IV medication errors: manual rate entry. Every infusion starts from a verified Epic order.

Nurse Time Savings

Removing manual pump programming saves an estimated 8–12 minutes per infusion. Across a 12-hour shift with multiple drips, that's 30–60 minutes returned to bedside care per nurse per day.

📋

Automatic MAR Charting

Pump-to-Epic data flow auto-documents infusion start, rate changes, pauses, alarms, and completion directly in the MAR. No more late charting or missed entries, and a complete, accurate audit trail every time.

🔄

Closed Medication Loop

From the physician's order through pharmacy verification to the bedside scan sequence and auto-charting, every step is connected digitally. No manual transcription, no re-keying. A pharmacy override propagates to the pump in real time.

📊

Data-Driven Governance

Pump event data feeds into Epic analytics dashboards covering alarm fatigue, soft-limit override trends, and drug library gaps. This gives clinical leadership the visibility they need to drive continuous, evidence-based improvement at BMC.

🎓

Adoption That Sticks

Sustained adoption requires more than a go-live. Role-based training, super-user networks, feedback loops, and ongoing clinical informatics support ensure the integration lives up to its promise.

The Full Integration Workflow

Every medication infusion follows this six-step bedside workflow, from patient identification to real-time documentation in Epic, with Alaris and Epic exchanging data at each step along the way.

🪪
Scan Patient
Scan patient ID band to confirm identity
💊
Scan Medication
Verify the medication bag against the Epic order
📷
Scan Pump
Scan Alaris pump barcode to associate it with the patient
📡
Send Details to Pump
Epic sends dose, rate & parameters via HL7/FHIR
▶️
Start Pump
Nurse confirms pre-loaded settings and starts infusion
Validate in Epic
Pump data auto-charts to the Epic MAR in real time
1
Scan Patient
The nurse scans the barcode on the patient's ID band at the bedside. Epic confirms identity, matches it to the active encounter, and pulls up the pending medication orders in the eMAR. This first scan is what kicks off the barcode medication administration (BCMA) workflow.
Patient ID Band · Identity Verification · Epic eMAR
2
Scan Medication
The nurse scans the barcode on the medication bag. Epic cross-references it against the verified order, checking drug name, concentration, and expiration. This is where the 5 Rights (right patient, right drug, right dose, right route, right time) are validated electronically, before the infusion is ever connected to a pump.
5 Rights Verification · Medication Matching
3
Scan Pump
The nurse scans the Alaris pump barcode (or the specific channel label). Epic associates that physical pump channel with the patient encounter and the active medication order, creating the link that makes auto-programming possible.
Pump Association · Channel Matching
4
Send Details to Pump
Epic transmits the medication name, concentration, dose, rate, and infusion duration to the Alaris pump via HL7/FHIR messaging. The pump auto-populates all programming fields — no manual keypad entry required.
HL7/FHIR · Auto-Programming
5
Start Pump
The nurse reviews the pre-loaded settings on the pump screen. DERS guardrails are enforced automatically — a soft-limit prompts for confirmation, a hard-limit blocks infusion until the order is reviewed. Once confirmed, the nurse starts the infusion.
DERS Guardrails · Nurse Sign-Off · Infusion Start
6
Validate Pump Data in Epic
As the infusion runs, the Alaris pump sends real-time data back to Epic: start time, rate, volume infused, any alarms or rate changes, and completion status. All of this is written directly to the MAR — no manual charting needed.
MAR Auto-Documentation · Real-Time Telemetry

Before & After Integration

The integration fundamentally transforms the bedside infusion experience. It reduces risk, reclaims nurse time, and closes the documentation gaps that have long been a frustration for nursing staff.

❌  Without Integration
  • Nurse manually transcribes medication, dose, and rate from a paper MAR or screen into the pump keypad
  • No guardrail enforcement at programming time, which means errors can reach the patient undetected
  • Separate barcode scanning in Epic and pump programming are disconnected steps
  • Infusion charting is done manually after-the-fact, often from memory or estimation
  • Rate changes and alarms are not captured in Epic, leaving an incomplete audit trail
  • Drug library updates require manual pump downloads and are inconsistently applied
  • High cognitive load during shift handoff, with pump data and the eMAR frequently out of sync
  • No real-time visibility into infusion status for pharmacists or charge nurses
✅  With Alaris–Epic Integration
  • Pump auto-programs directly from the Epic-verified order, with no manual rate or dose entry needed
  • DERS guardrails enforce soft and hard limits before infusion starts, every time
  • Three-step scan sequence (patient ID band, medication bag, pump barcode) unifies identity verification, drug verification, and pump association in one continuous bedside workflow
  • MAR is automatically documented with start time, infused volume, and completion status
  • Pump events (rate changes, alarms, pauses) are charted in real time in Epic
  • Drug library updates are managed centrally and pushed to all pumps automatically
  • Shift handoff data is accurate and consistent, with Epic and the pump always in alignment
  • Clinical Informatics dashboard shows real-time infusion status, alarm trends, and override analytics

Competency-Based Training Framework

Role-specific, hands-on training modules designed for nurses, pharmacists, physicians, and IT staff. Each module is grounded in adult learning principles and uses real Epic playground and Alaris simulation environments so staff feel confident before they ever touch a live system.

01
Foundations: Integration Overview
⏱ 20 min · All Staff

Big-picture orientation on why Alaris and Epic are integrated, how data flows between systems, patient safety benefits, and what changes in day-to-day workflows. Reduces resistance by answering "why are we doing this?"

eLearning Video walkthrough Pre-assessment
02
Nursing Workflow: Scan, Validate & Infuse
⏱ 45 min · RN / LPN

Hands-on simulation of the complete bedside workflow: scanning the patient ID band, scanning the medication bag, scanning the pump barcode, reviewing the pre-loaded parameters that Epic sends to the pump, validating against DERS guardrails, starting the infusion, and handling exceptions when something doesn't match.

Epic Playground Pump Simulation Competency checklist
03
Pharmacist: DERS Library & Override Management
⏱ 30 min · PharmD / RPh

Deep dive into the Alaris drug library maintenance workflow, soft/hard limit governance, how pharmacy order verification in Epic Willow affects pump parameter loading, and managing formulary change propagation across the pump fleet.

Epic Willow DERS Console Formulary governance
04
Exception Handling & Downtime Procedures
⏱ 25 min · RN / Charge RN

What to do when the integration is unavailable: manual pump programming with DERS standalone mode, downtime documentation workarounds, escalation paths to Clinical Informatics, and how to reconcile records after system restoration.

Downtime scenarios Escalation paths Rapid reference card
05
Super-User Training: Go-Live Support Certification
⏱ 4 hrs · Selected RN / Pharmacist

Intensive super-user preparation: full workflow mastery, common issue diagnosis, how to escalate to the Clinical Informatics team, supporting peers at the elbow during go-live, and documenting feedback for continuous improvement.

At-the-elbow coaching Issue triage QA feedback loop
06
Analytics & Continuous Improvement
⏱ 30 min · Clinical Informatics / Charge RN

How to use the Epic pump analytics dashboard to monitor auto-programming utilization, hard-limit alarm trends, override volume, and uncharted infusion flags. This turns raw pump data into actionable quality improvement at the unit level.

Epic Analytics Pump event reports QI methodology

Three-Phase Adoption Strategy

Sustainable adoption doesn't happen at go-live. It's built patiently before, supported intensely during, and continuously nurtured after. Each phase has measurable milestones, clear ownership, and a feedback loop that keeps things honest.

Phase 01
Pre-Implementation
8–12 Weeks Before Go-Live
  • Conduct current-state workflow assessments with nursing units, pharmacy, and informatics
  • Map Epic order types to Alaris pump channels and drug library entries
  • Identify champion super-users (1 per unit) to serve as first-line adoption anchors
  • Validate DERS drug library with pharmacy to ensure soft and hard limit alignment with the BMC formulary
  • Build Epic training environment with realistic patient scenarios for simulation
  • Develop role-specific quick-reference cards and downtime procedure guides
  • Run stakeholder briefings: unit managers, CNO, informatics leadership
  • Establish feedback channel (Slack channel, shared inbox) for concerns and questions
Phase 02
Go-Live Support
Weeks 1–4 · Intensive
  • Deploy at-the-elbow support on all shifts, prioritizing the first 72 hours post-go-live
  • Operate a command center with Clinical Informatics, IS, Pharmacy, and Biomed on standby
  • Conduct daily rounding with charge nurses to collect real-time friction points and celebrate early wins
  • Track auto-programming utilization by unit in Epic; intervene where adoption lags
  • Facilitate rapid-cycle issue resolution (<4 hr turnaround for non-critical workflow breaks)
  • Publish daily go-live updates to nursing leadership via email and digital board
  • Recognize high-adoption units publicly to build a positive reinforcement culture across the organization
  • Document all issues in a structured log for post-live review and CAPA tracking
Phase 03
Sustained Adoption
Weeks 4–12+ · Ongoing
  • Monthly Epic pump analytics review with unit nursing leadership, tracking utilization against target
  • Quarterly drug library governance review with the P&T committee and Pharmacy
  • Onboarding module for all new nursing staff as part of clinical orientation
  • Identify and remediate low-adoption units through targeted coaching and workflow optimization
  • Analyze DERS override patterns and escalate high-risk trends to clinical leadership
  • Coordinate pump firmware and drug library updates with Biomed and IS
  • Publish quarterly adoption dashboard to CNO, CMO, and VP of Quality
  • Submit QI project abstract summarizing outcomes for peer-reviewed publication or conference

Measuring What Actually Matters

Adoption isn't just go-live completions. It's measurable clinical impact. These KPIs are tracked in Epic Analytics and reviewed with leadership on a monthly cadence.

0%
Auto-Programming Utilization Rate (Target: ≥90%)
↑ 31% above baseline
0%
Reduction in IV Medication Programming Errors
↓ Confirmed by incident report review
0%
eMAR Auto-Documentation Rate (was 41% manual)
↑ Charting compliance improved significantly
0%
Staff Training Completion Rate (12 weeks)
→ All clinical units trained before go-live
0%
Decrease in DERS Soft-Limit Override Rate
↓ Guardrail acceptance culture established
0.8
Average Staff Satisfaction Score (out of 5)
★ Post go-live survey · 312 respondents

📊 Reporting Cadence

Daily (Go-Live Weeks 1–2)

Auto-program utilization, issue log, at-the-elbow coverage summary, escalations

Weekly (Weeks 3–8)

Unit-level adoption dashboard, DERS override trends, open issues by priority

Monthly (Sustained)

Full KPI report to CNO/CMO/IS, drug library governance review with P&T

Quarterly

QI outcomes presentation to Quality Committee; benchmarking vs. similar BMC programs

🎯 Adoption Thresholds & Escalation

≥ 90% utilization
Green: unit is performing above target. Celebrate it and share what's working with other units.
75–89% utilization
Yellow: schedule targeted coaching. Look for super-user gaps or workflow friction causing the lag.
≤ 74% utilization
Red: escalate to unit manager and Clinical Informatics. Investigate root causes within 48 hours.
DERS override spike (>15%/wk)
Escalate to Pharmacy + P&T committee; review drug library limits same week

Real-World Training Scenarios

These scenario-based learning activities are embedded in the training curriculum. They build confidence before go-live and become a trusted reference guide after.

ICU · Critical Care
Vasopressor Titration in the Medical ICU
Patient in septic shock requires norepinephrine dose escalation. Nurse must adjust the pump rate and ensure Epic MAR reflects the change without re-scanning.

Clinical Context

  • 65-year-old with septic shock; initial norepinephrine infusion was set up following the full 6-step workflow (scan patient ID band, scan medication bag, scan pump, details sent to pump, infusion started, pump data validated in Epic)
  • Physician orders a rate increase to 0.10 mcg/kg/min via CPOE
  • Pharmacist verifies; updated parameters are sent to the associated pump automatically
  • Pump displays the new pre-loaded rate for nurse confirmation — no re-scanning required for a rate change on an already-associated pump
  • Nurse validates against DERS limits (soft limit: 0.5 mcg/kg/min)
  • Rate change accepted; Epic MAR auto-updates with the new rate and timestamp

Adoption Specialist Role

  • Train nurses on how rate change orders appear in eMAR vs. pump screen
  • Clarify that re-scanning is NOT required for rate changes (only new infusion initiations require a pump scan)
  • Practice scenario: a nurse misses the update notification. Walk through exactly how the pump alerts them
  • Ensure ICU super-user can coach peers on high-alert medication override protocols
  • Review DERS norepinephrine limits with the ICU pharmacist team
  • Create quick-reference card posted in ICU med room for reference
Med/Surg · High-Alert Medication
Weight-Based Heparin Protocol Initiation
Anti-coagulation therapy with weight-based heparin requires precise rate calculation. The integration eliminates manual math and guardrails catch out-of-range doses before infusion.

Clinical Context

  • Patient with DVT; physician initiates heparin infusion protocol via Epic CPOE
  • System calculates weight-based dosing (units/kg/hr) from the patient's documented weight
  • Pharmacist verifies; pump receives concentration, rate, and dose per kg automatically once the nurse completes scanning
  • Nurse scans the patient ID band, scans the heparin bag barcode, then scans the Alaris pump barcode to associate the channel
  • Epic sends the pre-calculated parameters to the pump; nurse validates the pre-loaded rate with no mental math required
  • DERS alerts if the dose exceeds the protocol-specified range for the heparin drip
  • Lab PTT results trigger an Epic-based protocol adjustment; the updated order propagates to the pump automatically

Adoption Specialist Role

  • Walk nurses through the full 3-scan sequence (patient ID band, medication bag, pump) and how each scan triggers a different safety check in Epic
  • Clarify that weight-based calculation is embedded in the Epic order — no bedside math needed
  • Simulate a scenario where patient weight changes and explore how that affects the infusion parameters
  • Train on when DERS soft vs. hard limit fires and what the correct clinical response is for each
  • Ensure pharmacy understands how protocol-based order sets in Epic map to pump drug library
  • Review anti-coagulation stewardship with Pharmacy regarding heparin soft limit governance
  • Document competency sign-off for all nurses handling VAD/heparin patients
All Units · Downtime Protocol
Epic–Alaris Integration Downtime Event
The integration interface goes down during a planned Epic maintenance window. Nurses must manage infusions safely using DERS standalone mode and manual documentation processes.

Clinical Context

  • Epic downtime announced 30 minutes before; integration will be unavailable for 4 hours
  • Alaris pumps switch to standalone DERS mode; the drug library remains active locally
  • Nurses access downtime reports (printed MAR snapshots) for active infusions
  • Pump programming reverts to manual entry with DERS guardrails still enforced
  • All changes documented on downtime paper forms for post-restoration reconciliation
  • After restoration, nurses enter manual changes into Epic; auto-program resumes

Adoption Specialist Role

  • Ensure downtime procedures are practiced before go-live, not something staff discover mid-crisis
  • Distribute laminated quick-reference cards with downtime steps to each pump station
  • Verify all nurses know how to print downtime reports from Epic pre-emptively
  • Train charge nurses on coordinating manual-mode DERS programming across their unit
  • Establish IS escalation pathway for unplanned downtime events (non-maintenance)
  • Run quarterly downtime drills to keep competency sharp post go-live
All Units · Patient Safety
DERS Hard-Limit Alert: Medication Order Exceeds Safe Range
Pump rejects an order because the programmed rate would exceed the DERS hard limit. This is the system working exactly as designed. Nurses need to know how to escalate safely without bypassing the guardrail.

Clinical Context

  • Morphine PCA order entered with a concentration mismatch (1 mg/mL instead of 5 mg/mL)
  • Epic sends parameters to pump; pump computes actual dose rate and crosses DERS hard limit
  • Pump displays HARD LIMIT EXCEEDED. The infusion cannot start until the issue is reviewed and resolved
  • Nurse cannot override hard limit at bedside. This is intentional, built in specifically for patient safety
  • Escalation path: notify charge nurse → contact pharmacy → physician amends CPOE order
  • Corrected order propagates; pump is re-programmed with accurate parameters

Adoption Specialist Role

  • Emphasize during training: HARD LIMIT = do not bypass. This is the system working as designed
  • Role-play the escalation pathway so nurses are confident under pressure
  • Ensure pharmacy team knows that hard-limit events trigger an automatic incident notification
  • Work with Clinical Informatics to review any recurring hard-limit patterns for drug library review
  • Reinforce with physicians that CPOE concentration field must match the prepared bag exactly
  • Log every hard-limit event in the quality improvement database for root cause analysis

Common Issues & Resolutions

Every clinical system integration comes with a learning curve. Here are the most common issues encountered during go-live, along with practical steps to resolve them quickly.

Most common causes:
1. The full 3-scan sequence is not complete. Confirm the nurse has scanned the patient ID band, then the medication bag, then the pump barcode in that order. Skipping any step breaks the association chain in Epic.
2. The medication order has not been pharmacist-verified yet. Check the Epic order status.
3. The pump is not connected to the hospital network. Check the wireless indicator on the Alaris display.
4. There is a pump-channel mismatch. The nurse may have scanned a different channel than the one in Epic. Rescan and confirm channel association.
Likely causes:
1. The pump-to-Epic data feed has a delay. Give it 3 to 5 minutes; the MAR usually catches up on its own.
2. The pump association was dropped because the pump moved rooms or had a network hiccup. Re-scan to re-associate.
3. The pump channel reporting is configured incorrectly. Escalate to Clinical Informatics for interface log review.
4. The infusion was manually documented on paper during a downtime event but not reconciled back into Epic. The nurse will need to back-chart manually.
Check these in order:
1. Is the order status "Verified" by pharmacy? Unverified orders cannot auto-program.
2. Is the medication type mapped in the Alaris drug library? Not all medications are eligible for auto-programming. Check the approved medication list with pharmacy.
3. Is the correct infusion route selected? IV push orders do not trigger auto-program.
4. Has the nurse selected the correct encounter/patient context in Epic? Wrong patient context is a common source of this error.
Soft limits are designed to pause and prompt — not to block.
Yes, a nurse CAN override a soft limit if they have a clinical reason, but they must:
1. Document the reason for the override on the pump (required for the audit trail).
2. Notify the physician if the override is for a high-alert medication.
3. All soft-limit overrides are captured in Epic pump analytics. High override rates will trigger a pharmacy review.
If soft-limit overrides are happening frequently for the same medication, escalate to pharmacy to review whether the drug library limit is appropriately calibrated for the BMC patient population.
Post-downtime reconciliation steps:
1. Gather the downtime paper forms collected by the night shift nurses.
2. Once the integration is restored, verify that the pump has re-associated with the patient in Epic (re-scan if needed).
3. Nurses must manually enter any rate changes or infusion events that occurred during downtime into the Epic MAR using the back-charting workflow.
4. Notify the Clinical Informatics team of the event (even if it resolved on its own) so the interface log can be reviewed for root cause.
5. Confirm that the current pump state matches the current Epic order before resuming auto-charting.
This is the most important adoption conversation you can have. Acknowledge before you correct. Don't dismiss.
1. Validate their experience first: "You're right that the first few days feel slower. That's completely normal with any new system."
2. Show them the data: users who have passed the initial learning curve (typically 3–5 shifts) report 8–12 minutes saved per infusion on average.
3. Ask what specific step feels slow. Often it's a fixable workflow tweak, not a fundamental problem with the integration.
4. Share patient safety wins from their own unit. A prevented dose error from DERS is powerful proof.
5. Connect them with a peer who has already transitioned successfully. Peer influence is the strongest adoption lever in clinical settings.

Hi, I'm Alicia. Let's Talk.

I'm a multilingual public health professional (BDS, MS) currently working as Unit Coordinator on BMC's M3W Surgical Step-Down Unit, where I use Epic daily in a fast-paced inpatient setting. This portfolio is my way of showing the kind of thoughtful, people-centered approach I'd bring to the Clinical Systems Adoption Specialist role at Boston Medical Center.

✉ aliciaaa@bu.edu 📞 (862) 344-7323 🔗 LinkedIn 📍 Boston, MA
Core Expertise
Epic eMAR & CPOE · Alaris DERS · Clinical Workflow Analysis · Adult Education
Tools & Systems
Epic Hyperspace · Alaris PC Unit · HL7/FHIR · BCMA Workflow · REDCap
Methodologies
Kotter Change Management · Rapid-Cycle QI · ADDIE Instructional Design · Lean Workflow
Clinical Audience
RN / LPN · PharmD · Physicians · Charge Nurses · Clinical Informatics · Biomed