Epic Willow Pharmacy: Inpatient vs Ambulatory Configuration, Workflow, and Go-Live
Epic Willow is one of the most implementation-heavy pharmacy modules in any EHR system. Teams that treat it as a simple configuration exercise hit problems fast – usually at go-live. This article breaks down how Willow Inpatient and Willow Ambulatory differ in architecture, workflow logic, build requirements, and testing strategy. It is written for analysts, build specialists, and IT project leads who already know the basics and need to work smarter on real implementations.
- What Is Epic Willow?
- Inpatient vs Ambulatory: Core Differences
- Willow Inpatient: Build and Workflow Deep Dive
- Willow Ambulatory: Build and Workflow Deep Dive
- Integration Architecture and HL7 FHIR
- Testing Strategy: QA and BAT for Willow
- Go-Live Planning and Risk Mitigation
- Roles, Certifications, and Career Path
- Downloads: Checklists and Templates
What Is Epic Willow?
Epic Willow is Epic Systems’ pharmacy management module. It handles the full medication lifecycle – from order verification and clinical decision support to dispensing, administration reconciliation, and regulatory reporting. Willow is not a standalone product. It runs within the Epic ecosystem and shares the same patient record, ordering backbone, and CPOE framework used across all Epic clinical applications.
Willow comes in two distinct modules. Willow Inpatient manages medication workflows inside the hospital – think ICU, med-surg, oncology infusion, and OR pharmacy. Willow Ambulatory handles outpatient dispensing – retail pharmacy operations, specialty pharmacy, and prescription management tied to clinic visits. Each module has its own build dictionary, workflow logic, and integration touchpoints. They share some infrastructure but behave very differently in practice.
Understanding which module drives which workflow is the first competency a Willow analyst needs. Conflating the two is a common mistake on first implementations. It produces build errors, workflow gaps, and testing failures that are expensive to fix post-go-live. The Epic EHR Learning Hub covers the broader Epic module landscape if you need that foundational context first.
Willow Inpatient vs Ambulatory: Core Differences
The functional difference runs deeper than setting. Inpatient pharmacy operates in a closed-loop medication administration model. Every order flows from CPOE through verification, dispensing, and finally nurse-administered documentation in eMAR. Ambulatory pharmacy operates on a prescription-fill model. The pharmacist verifies, fills, and counsels. The patient leaves with the medication.
| Dimension | Willow Inpatient | Willow Ambulatory |
|---|---|---|
| Primary user | Hospital pharmacist, pharmacy tech, nurse (via eMAR) | Retail/outpatient pharmacist, pharmacy tech, patient |
| Order source | CPOE – physician/provider orders in Epic | e-Prescribe, fax, phone-in, walk-in prescription |
| Dispensing model | Unit dose, IV admixture, automated dispensing cabinets (ADC) | Retail fill, specialty fill, mail order integration |
| Administration verification | Closed-loop via barcode medication administration (BCMA) | Patient self-administration – no closed-loop |
| Regulatory drivers | USP 795/797/800, Joint Commission, CMS Conditions of Participation | State board of pharmacy, DEA (controlled substances), PBM contracts |
| Key integrations | ADC (Pyxis, Omnicell), IV robotics, lab interfaces | Surescripts, PBM adjudication, patient portal, specialty hub |
| Build complexity | High – formulary, order sets, clinical decision support rules | High – PBM logic, benefit adjudication, counsel workflows |
| Go-live risk profile | Patient safety-critical – errors have immediate clinical impact | Revenue-cycle-critical – adjudication failures affect reimbursement |
Both modules require Epic certification for build analysts. Both carry significant risk if misconfigured. The difference is where that risk surfaces – Inpatient errors tend to hit clinical safety, Ambulatory errors tend to hit revenue and patient satisfaction.
Willow Inpatient: Build and Workflow Deep Dive
Formulary and Drug Database Build
Willow Inpatient runs on the Epic drug database (ERX/NDC records) mapped to your organization’s formulary. Build analysts configure medication records in the Drug (ERX) master file. Every medication needs a dispense form, route, strength, and formulary status. That sounds simple. In practice, a mid-size hospital formulary has 1,500 to 3,000+ active medication records. Managing duplicates, formulary exceptions, and non-formulary request workflows is a significant build effort on its own.
First DataBank (FDB) or Multum provides the underlying drug interaction and clinical decision support content. Your build team configures which alerts fire, at what severity, and for which patient populations. Alert fatigue is a documented patient safety problem. Build analysts must work with pharmacists and clinical informaticists to tune alert thresholds. Too many low-value alerts and clinicians start clicking through everything without reading.
Order Sets and CPOE Integration
Willow Inpatient is tightly coupled to Epic’s CPOE framework. When a physician places a medication order, it routes to the pharmacy queue based on medication type, patient location, and order priority. Build analysts configure routing rules in the Pharmacy Order Routing (POR) master file. This tells the system which pharmacy department fills which order – inpatient central pharmacy, satellite pharmacy, oncology pharmacy, or OR pharmacy.
Order sets are a major build deliverable. A 400-bed hospital might have 200-600 order sets covering admission orders, surgical protocols, sepsis bundles, and specialty-specific medication panels. Each order set must be built, clinically reviewed, and tested. Analysts who have worked with Epic EHR Orders and CPOE workflows understand that order set quality directly affects pharmacy workload and medication safety downstream.
During a Willow Inpatient implementation at a 600-bed academic medical center, the build team configured IV admixture routing to the central pharmacy. Oncology nursing reported during integrated testing that chemotherapy orders were routing to central pharmacy instead of the dedicated oncology satellite – a safety and regulatory gap under USP 797 compounding standards. Root cause: the routing rule used patient location codes, but oncology infusion patients sometimes held a med-surg bed code on admission day. The fix required adding a department-specific override rule and updating the order routing logic. This was caught in cycle 2 testing, not go-live – which is exactly the point of structured testing cycles.
Automated Dispensing Cabinet Integration
Most hospitals use automated dispensing cabinets (ADCs) – Pyxis from BD or Omnicell are the dominant vendors. Willow Inpatient interfaces with ADC systems via HL7 messaging to synchronize medication charges, patient assignments, and cabinet inventory. Build analysts configure the ADC interface in Epic’s Interface Engine (Bridges).
The common failure points are patient ADT (Admission, Discharge, Transfer) message timing and medication charge reconciliation. When a patient transfers units and the ADT message lags, the ADC may not reflect the patient’s current location. Nurses pull medications from the wrong cabinet. This is not a hypothetical edge case – it happens on implementations that skip thorough ADT timing validation during testing.
Barcode Medication Administration (BCMA)
BCMA is the closed-loop safety mechanism that connects Willow dispensing to nursing eMAR documentation. The nurse scans the patient wristband and the medication barcode before administration. Epic verifies the right patient, right drug, right dose, right route, and right time. Willow build must ensure NDC barcodes are mapped correctly in the drug record. Missing NDC maps produce “medication not found” scanner errors at the bedside.
NDC mapping validation is one of the highest-priority test scripts in a Willow Inpatient go-live. Every high-alert medication – insulin, heparin, concentrated electrolytes, chemotherapy – needs manual barcode verification before go-live, not just spot-checking.
Willow Ambulatory: Build and Workflow Deep Dive
Prescription Workflow and e-Prescribing
Willow Ambulatory receives prescriptions through three channels: e-prescribing via Surescripts, internal Epic orders routed to the ambulatory pharmacy, and manual entry from paper or phone-in prescriptions. Build analysts configure the Surescripts connection through Epic’s Bridges interface engine. The Surescripts certification process requires specific testing with Epic’s national pharmacy network – this is a prerequisite step that takes 4-8 weeks and cannot be rushed.
The prescription fill workflow in Willow Ambulatory follows a pharmacist-centered queue model. Prescriptions enter an incoming queue, are verified by a pharmacist, filled by a tech, and checked by the pharmacist before dispensing. Each step is tracked with timestamps. Build analysts configure the workflow stages, escalation rules, and patient notification triggers (automated calls, MyChart alerts, text messages).
PBM Adjudication and Insurance Verification
Pharmacy Benefit Manager (PBM) adjudication is the revenue engine of ambulatory pharmacy. When a prescription is filled, Willow submits an NCPDP D.0 transaction to the patient’s PBM (Express Scripts, CVS Caremark, OptumRx, etc.) for real-time insurance verification and reimbursement calculation. Build analysts configure PBM plans, bin/PCN/group codes, and rejection code handling.
Rejection handling is where ambulatory implementations most often struggle. PBM rejection codes are not standardized in the same way HL7 errors are. A “70 – product/service not covered” rejection might require a prior authorization. A “75 – prior authorization required” needs a PA workflow built in Epic. Build analysts must work with the organization’s pharmacy revenue cycle team to map rejection codes to workflow actions – not just acknowledge that rejections happen.
A health system launching an in-house specialty pharmacy built Willow Ambulatory to handle oncology oral medications – a high-cost, compliance-intensive drug class. During integrated testing, the team discovered that manufacturer copay cards (used to reduce patient out-of-pocket costs) were not adjudicating correctly through the PBM coordination-of-benefits logic. The workaround required a manual step that added 8-12 minutes per prescription fill. The fix involved configuring a secondary payer plan record in Epic and coordinating with three manufacturer hub programs to update their BIN/PCN routing. This was not on the original build scope – it surfaced during UAT when the specialty pharmacists ran through actual patient scenarios.
Specialty Pharmacy and Hub Integration
Specialty pharmacy adds another layer of complexity. High-cost medications – biologics, oncology agents, multiple sclerosis drugs – require prior authorization, REMS (Risk Evaluation and Mitigation Strategy) compliance, and in some cases cold-chain dispensing documentation. Willow Ambulatory supports specialty workflows through the Specialty Pharmacy module add-on.
Build analysts configure specialty medication records with REMS flags, required documentation triggers, and restricted distribution settings. Some REMS programs require pharmacist certification before dispensing – the build must enforce this through workflow validation, not just rely on pharmacist knowledge.
Epic Willow Integration Architecture and HL7 FHIR
Willow does not operate in isolation. Both modules depend on interfaces to function correctly. Understanding the integration architecture is not optional for analysts or QA teams. Interface failures are the most common source of go-live issues in pharmacy implementations.
Key Inpatient Integrations
Willow Inpatient connects to ADC systems (Pyxis, Omnicell) via HL7 v2 messaging through Epic Bridges. ADT messages (A01 admit, A02 transfer, A03 discharge) drive cabinet synchronization. Pharmacy dispense events generate charge messages that flow to the hospital billing system. IV robotics systems (Baxter DoseEdge, BD Intelliport) connect via HL7 for IV workflow management.
Laboratory interfaces matter too. Vancomycin and aminoglycoside dosing in Epic’s clinical pharmacokinetics tool pulls live lab values (serum creatinine, drug levels) from the laboratory system. If the lab interface has a lag or a mapping error, the pharmacokinetic dosing recommendations are based on stale data. This is a patient safety risk that build and QA teams must test explicitly.
HL7 FHIR in Pharmacy Workflows
HL7 FHIR R4 is increasingly relevant to Willow implementations, particularly for external pharmacy integrations and patient-facing medication data. The MedicationRequest, MedicationDispense, and MedicationAdministration FHIR resources map directly to Willow’s core workflow objects. External applications – patient portals, medication adherence apps, payer medication management tools – access medication data through Epic’s FHIR API.
| Integration | Module | Standard | Common Failure Point |
|---|---|---|---|
| ADC (Pyxis/Omnicell) | Inpatient | HL7 v2 ADT/RDS | ADT timing lag on transfer |
| Laboratory System | Inpatient | HL7 v2 ORU | Result mapping errors |
| IV Robotics | Inpatient | HL7 v2 / Proprietary | Order format mismatch |
| Surescripts | Ambulatory | NCPDP SCRIPT 10.6 | Certification delays |
| PBM Adjudication | Ambulatory | NCPDP D.0 | Rejection code gaps |
| Patient Portal (MyChart) | Both | HL7 FHIR R4 | Medication list reconciliation |
| 340B Program | Both | Proprietary / HL7 | Eligibility determination errors |
The 340B Drug Pricing Program deserves specific attention. Qualifying health systems use 340B pricing to purchase outpatient drugs at significant discounts. Willow has a 340B module that flags eligible patients and tracks dispensing. Misconfiguration here creates compliance exposure under HRSA audit – not just financial loss. Build analysts must understand 340B eligibility rules before touching that configuration.
Testing Strategy for Epic Willow Pharmacy
Willow testing is not standard software QA. Medication errors are patient safety events. The testing strategy must reflect that. Epic implementations typically run three testing cycles before go-live: unit testing, integrated testing (IT), and parallel/dress rehearsal. Each cycle has a distinct scope and sign-off requirement.
Test Script Structure for Pharmacy
Pharmacy test scripts must cover the full medication lifecycle, not just the pharmacy queue. A test script for an inpatient IV antibiotic order should trace the order from physician CPOE entry through pharmacist verification, IV prep documentation, cabinet dispensing, nurse BCMA scan, and eMAR documentation. If any link in that chain breaks, the script fails – even if the pharmacy queue looked fine in isolation.
High-alert medication test scripts require a pharmacist or clinical informaticist to co-sign the expected results. This is not bureaucracy – it is a documented QA checkpoint. Analysts who have worked through BAT vs UAT methodology will recognize that pharmacy testing blends both – business process validation and clinical workflow acceptance in a single test cycle.
Interface Testing Requirements
Interface testing for Willow requires dedicated test scenarios for each connected system. For ADC testing, analysts simulate admit, transfer, and discharge events and confirm cabinet synchronization within expected time windows. For PBM adjudication, test scripts use real test payer credentials or a PBM test environment to submit claim transactions and verify response handling.
HL7 message validation requires the integration analyst and QA analyst to work together. QA validates the clinical outcome (did the ADC update correctly?). Integration validates the message payload (did the correct HL7 segments fire with the right values?). These are different tests and both are necessary. The clinical documentation workflow connects closely to pharmacy – teams who have reviewed the EpicCare Inpatient ClinDoc guide will already know how tightly nursing documentation ties into the medication administration record.
Dress Rehearsal and Parallel Testing
Willow Inpatient implementations typically run a parallel period where the pharmacy operates both the legacy system and Epic simultaneously for 24-72 hours before full cutover. This is expensive in pharmacist labor but catches data integrity issues that test environments cannot replicate. Legacy system dispense records must reconcile against Epic’s eMAR before cutover is confirmed safe.
Dress rehearsal is a full simulation of go-live day activities – data conversion validation, interface activation sequence, user login verification, and escalation chain testing. It is not optional. Organizations that skip dress rehearsal in favor of saving a weekend of labor routinely pay more in go-live downtime and post-live remediation.
Go-Live Planning and Risk Mitigation for Willow
Pharmacy go-live carries patient safety risk that most other Epic module go-lives do not. A misconfigured CPOE order or a broken interface on day one does not just create workflow friction – it creates potential for medication errors. Go-live planning for Willow must account for this reality, not treat it as a standard IT project cutover.
Go-Live Readiness Criteria
Before pharmacy go-live approval, the following must be confirmed – not “mostly done.” Every high-alert medication barcode must be validated. Every interface must pass a 48-hour stability test in the production-like environment. All critical order sets must have clinical sign-off. Downtime procedures must be documented, printed, and distributed to all pharmacy locations. Super-users must be identified for every shift and every pharmacy department.
The go-live command center must include a pharmacist or clinical informaticist with Willow build access. Issues surfaced on go-live day often require immediate configuration changes – not just workarounds. Having build access and clinical authority in the same room shortens resolution time significantly. The Epic EHR Go-Live Support framework covers the command center structure and escalation model in detail.
| Risk | Module | Impact | Mitigation |
|---|---|---|---|
| ADC sync failure | Inpatient | High – patient safety | Manual cabinet override procedure, 24hr monitoring |
| BCMA barcode miss | Inpatient | High – patient safety | Pre-go-live NDC validation sprint |
| CDS alert fatigue | Inpatient | Medium – safety/UX | Alert tuning session with P&T committee pre-go-live |
| PBM adjudication failure | Ambulatory | High – revenue | Manual billing fallback, PBM hotline on speed dial |
| Surescripts downtime | Ambulatory | Medium – workflow | Paper/fax fallback procedure documented |
| Controlled substance DEA audit trail | Both | High – regulatory | Pre-go-live EPCS certification, DEA workflow validation |
Electronic Prescribing for Controlled Substances (EPCS)
EPCS is a federally regulated workflow under DEA 21 CFR Part 1311. Epic’s EPCS solution requires prescriber identity proofing (in-person or remote) and two-factor authentication at the point of prescribing. For Willow Ambulatory, pharmacists must validate the EPCS-signed prescription audit trail before dispensing.
EPCS go-live requires DEA-mandated logical access controls, audit logs, and application security certification from an accredited third-party auditor. This process takes 60-90 days from initiation. It cannot be compressed. Teams that start EPCS certification late are the ones who go live with paper controlled substance prescriptions while the rest of the system goes digital – a workflow inconsistency that creates compliance risk and pharmacist frustration.
Roles, Certifications, and Career Path for Willow Specialists
Willow certification is one of the more selective Epic credentials. Employer sponsorship is required. You cannot self-study and sit a public exam. The certification process involves Epic-delivered training at Verona, Wisconsin or through Epic’s virtual training program, followed by proficiency exams and project completion requirements.
Certification Paths
| Certification | Focus | Typical Background | Salary Range (2026) |
|---|---|---|---|
| Willow Inpatient | Hospital pharmacy build, BCMA, ADC | PharmD or IT analyst with pharmacy ops experience | $90,000 – $140,000 |
| Willow Ambulatory | Retail/specialty pharmacy, PBM, Surescripts | Retail pharmacist or revenue cycle analyst | $85,000 – $130,000 |
| Willow Inpatient + Ambulatory | Dual module specialist | Senior analyst with full implementation history | $120,000 – $160,000+ |
| Willow Consulting (Contract) | Implementation support, optimization | Certified analyst, 2+ full implementations | $75 – $120+/hr |
Dual Willow certification (Inpatient + Ambulatory) is the highest-value credential in the Epic pharmacy space. Health systems launching integrated pharmacy programs – hospital-owned retail pharmacies, specialty pharmacy programs, or 340B operations – need analysts who understand both sides. The supply of dual-certified Willow analysts is genuinely constrained, which explains the premium compensation.
Willow analysts with HIPAA compliance knowledge and experience with Medicare Part D or Medicaid billing add further value. The intersection of pharmacy operations, clinical workflow, and regulatory compliance is rare. It commands attention from health systems and Epic consulting firms alike. If you are building your Epic career, Willow is one of the modules worth pursuing intentionally – not just accepting because it was available. Browse the full Epic EHR Learning Hub for module-by-module career guidance across the Epic ecosystem.
What Willow Analysts Need Beyond the Certification
Epic certification gets you in the door. What makes a Willow analyst effective on a real project is different. You need enough pharmacy operations knowledge to challenge a workflow design when it does not match how a pharmacist actually works. You need enough HL7 understanding to read a message and identify where a field is wrong. You need enough SQL or reporting knowledge to validate that what the database contains matches what the screen shows.
Project management discipline matters too. Willow implementations run parallel workstreams – build, training, interface testing, data conversion, super-user preparation – all converging at go-live. Analysts who can manage their own build tasks, track open items, and communicate blockers early are far more valuable than those who wait to be told what to do next. Six Sigma process thinking applies directly to pharmacy workflow optimization and post-go-live continuous improvement work.
Willow Inpatient and Willow Ambulatory are related but distinct implementations. Treating them as variations of the same build is the mistake that drives most Willow go-live problems. Know which module you are working on, build the interfaces with the same rigor you bring to the clinical workflows, and test the full medication lifecycle – not just the pharmacy queue. The analysts who do that consistently are the ones who get called back for the next implementation.
Authoritative References
- HL7 FHIR R4 – MedicationRequest, MedicationDispense, MedicationAdministration Resources
- DEA – Electronic Prescriptions for Controlled Substances (EPCS) Regulations, 21 CFR Part 1311