TL;DR
- Willow is Epic’s pharmacy software: Willow Inpatient for hospital dispensing, Willow Ambulatory for outpatient and specialty pharmacies, and Willow Inventory for stock and purchasing.
- Epic’s pharmacy interface catalog lists Willow’s connections to dispensing cabinets and robots, automated fill systems, wholesalers (X12 850, 810, 855 and 856, plus EPCIS for drug tracing) and e-prescribing networks (NCPDP SCRIPT). Benefit checks, prior authorization and claims sit on the same page but belong to Epic’s prescriber and payer applications.
- Outside apps read medication data through Epic’s FHIR APIs (Fast Healthcare Interoperability Resources), which list read and search for medication resources; anything that writes goes through interfaces the health system builds.
- HHS’s adoption of NCPDP SCRIPT version 2017071 expires on January 1, 2028, leaving version 2023011 as the e-prescribing standard.
Until this spring, one specialty prescription at Stanford Health Care’s specialty pharmacy moved through at least four separate systems: one for dispensing and claims, one for clinical reviews, a spreadsheet for referrals, and Epic for chart notes and labs. On March 30 the pharmacy went live on Epic’s Willow Ambulatory and Epic Specialty Pharmacy modules, with inventory and 340B tracking added (Stanford Medicine, June 4, 2026). The pharmacy supports 24 clinics, and Stanford’s IT lead called it “one of the most complex undertakings we’ve ever taken on.”
If you build software pharmacies use, or run pharmacy IT at a health system on Epic, that complexity lands on the interfaces around Willow. This guide maps them from Epic’s own catalog.
What Is Epic Willow?
Epic Willow is Epic’s pharmacy software for health systems that run their own inpatient and outpatient pharmacies on Epic. Epic’s interface catalog splits it into three applications (open.epic, Ancillary Systems: Pharmacy, checked October 2026):
| Application | What it covers | Typical connections |
|---|---|---|
| Willow Inpatient | Pharmacist verification and hospital dispensing | Dispensing cabinets, robots, carousels, TPN systems |
| Willow Ambulatory | Outpatient, retail and specialty pharmacy fills | Automated fill systems, e-prescribing networks |
| Willow Inventory | Drug stock, pricing and purchasing | Wholesalers and suppliers (purchase orders, invoices, shipments) |
Stanford’s specialty pharmacy went live on Epic Specialty Pharmacy alongside Willow Ambulatory. Willow sits next to the rest of Epic’s ordering and charting; our Epic modules overview shows where, and our Epic Ambulatory guide covers the outpatient side.
What Epic Lists as Willow Integrations
Epic publishes its pharmacy interfaces on open.epic, one entry per interface, each with a direction, a purpose, the vendors and organizations it shows as integrations, and, for many entries, a link to Epic’s technical specification. Grouped by job, this is what the page lists, and which side of Epic each entry belongs to:
| Group | What Epic lists | Standard named by Epic | Epic side |
|---|---|---|---|
| Dispensing (Willow Inpatient) | Verified orders out to cabinet, robotic, TPN or carousel systems · dispenses, returns and waste back in · formulary updates out to the dispensing system · stock transfer requests to robots and carousels · pharmacist-queue notifications | in Epic’s linked technical specs | Willow Inpatient |
| Automated fill (Willow Ambulatory) | Verified fills out to automated prescription fill systems · fill status and load/unload back in | not named | Willow Ambulatory |
| Wholesalers and inventory (Willow Inventory) | Purchase orders · invoices · order acknowledgements · shipment notices · price catalogs · drug supply chain events | X12 850 (or GS1), X12 810, X12 855, X12 856 (or GS1), EPCIS (GS1) | Willow Inventory |
| E-prescribing | New prescriptions, renewals and cancels in and out of the pharmacy · pharmacy settings updates to the e-prescribing network | NCPDP SCRIPT 10.6, 2017071, 2023011 | Willow Ambulatory (pharmacy side); the prescriber side is Epic’s ordering |
| Prescriber tools | Pharmacy benefit eligibility · real-time prescription benefit checks · prior authorization · formulary files · dispense history · cash price checks | X12 270/271 · NCPDP subset · NCPDP Formulary & Benefit · NCPDP SCRIPT | Epic as the prescriber |
| Claims | Paid pharmacy claims from external payers | NCPDP Post-Adjudication | Epic Payer Platform or Tapestry |
Three details matter when you scope a connection:
- Separate interfaces for cabinets and robots: For verified orders leaving Willow Inpatient, Epic recommends separate interfaces for cabinets and for robots.
- Drug tracing: The supply chain event interface “uses the Electronic Product Code Information Service (EPCIS) GS1 standard,” which is how package-level tracing under the Drug Supply Chain Security Act (DSCSA) reaches Willow Inventory.
- Conversions: Some interfaces exist only to move data in during a switch to Willow, such as prescriptions from a legacy pharmacy system. Plan those as one-time loads.
If you make dispensing or fill hardware, check whether your category is already on the list. As of October 2026, Epic’s entry for dispenses coming into Willow Inpatient lists Omnicell, BD, Swisslog, ARxIUM and others, and its entry for verified fills going out to automated fill systems from Willow Ambulatory lists Parata, ScriptPro, RxSafe, Kirby Lester, Omnicell and others. A name on the list means Epic shows the integration exists; each health system still decides which ones it turns on.
Where a row doesn’t name a message standard, the format is in Epic’s technical specification for that entry, which the health system’s interface team works from. The health system builds its side of these connections in Epic Bridges, the toolset hospitals use for HL7 and other interfaces.
Improve Pharmacy Workflows with Epic Integration
E-Prescribing and Surescripts Around Willow Ambulatory
Willow Ambulatory is the pharmacy end of e-prescribing: it receives new prescriptions, renewal responses and cancel requests from outside prescribers, and sends renewal requests and cancel responses back (open.epic, NCPDP interfaces, checked October 2026). Epic lists NCPDP SCRIPT 10.6, 2017071 and 2023011 on these interfaces, and Surescripts appears as an integration on every one of them.
The prescriber side of the same exchange is a separate topic: the clinician’s e-prescribing tool, EPCS for controlled substances, PDMP checks and the medication dispense history query, which Epic describes as e-prescribing functionality “when Epic is the prescriber.” Our e-prescribing software guide covers it, and our NCPDP integration page covers building to the standard. If your product prescribes through a partner network, see how we build on DoseSpot.
Building Around Willow: Medication Data for Outside Apps
Many products need Willow’s data without being a pharmacy system: specialty pharmacy hubs, adherence and refill apps, prior authorization tools, 340B and inventory analytics, or a device maker’s dispensing hardware. They connect in one of two ways.
Reading through Epic’s FHIR APIs. Epic’s FHIR R4 capability statement (sandbox metadata, August 2026 release, checked October 2026) lists these with read and search:
| What your app needs | FHIR resource | Listed interactions |
|---|---|---|
| The drug itself | Medication | read, search |
| What was prescribed | MedicationRequest | read, search |
| What the pharmacy dispensed | MedicationDispense | read, search |
| What was given to the patient | MedicationAdministration | read, search |
| What the patient reports taking | MedicationStatement | read, search |
| Insurance on file | Coverage | read, search |
None of the medication resources lists create or update, so an outside app can read what was ordered, dispensed and given but shouldn’t plan to record a dispense through FHIR. Check in Epic’s API documentation which dispenses MedicationDispense returns, the health system’s own fills or outside fill history, before an adherence feature depends on it. The list above comes from Epic’s sandbox capability statement, so confirm each resource in production too. A capability statement describes what the server supports; your app’s access is set in its Epic app registration and switched on by each health system. Our Epic FHIR API guide walks through the details.
Exchanging through interfaces the hospital builds. Anything that writes into Willow, such as a fill status, a dispense from a cabinet or an invoice, goes through one of the catalog interfaces above, set up by the health system’s Epic and interface teams in HL7, NCPDP or X12.
If your product isn’t on Epic’s list yet. The connection starts with a health system that wants it: their pharmacy and interface teams sponsor the interface, build the Epic side from Epic’s specification and test it with you. Your FHIR app also needs its own Epic registration, activated by each health system. If you plan to list the app for other Epic customers, our Epic Showroom guide covers that route.
We built the integration for a financial-assistance technology company that connects to EMR, pharmacy and practice-management systems over HL7 and FHIR, including Epic, cutting its manual data entry by 90%. Prior authorization is a common neighbor of this work; see our prior authorization services.
There are two ways to work with us:
- Mindbowser builds it: We build pharmacy-technology integrations around Epic over FHIR, HL7, NCPDP and X12. We integrate with Surescripts and DoseSpot, and we build to Surescripts’ and DEA’s EPCS requirements; your product holds the certifications. See our Epic integration work.
- You run ConnectHealth: ConnectHealth is our EHR integration product: HL7 v2, FHIR and X12 in, one consistent format out (REST, FHIR or webhook), with real-time eligibility (X12 270/271) via Stedi. ConnectHealth doesn’t remove vendor registration or the hospital’s approval chain.
What to Settle Before Connecting to Willow
Settle these with the health system before you build:
- Which catalog interface you’re using (owner: your team, with the hospital’s pharmacy analysts): Name the open.epic entry, its direction and which Willow application it touches.
- The standard and version (owner: the hospital’s interface team): For e-prescribing that’s NCPDP SCRIPT; HHS’s adoption of version 2017071 “expires on January 1, 2028” under 45 CFR 170.205(b), so plan for 2023011. For wholesalers, confirm X12 or GS1.
- Who builds the Epic side (owner: the hospital’s Epic and Bridges teams): Willow’s configuration and its interfaces belong to the health system; your build ends at your system and the agreed message.
- Drug tracing, if you touch supply chain (owner: pharmacy operations): EPCIS events for DSCSA have their own trading-partner setup.
- Agreements and testing (owner: compliance and IT security): The business associate agreement, a nonproduction environment, test cases for fills, cancels and returns, and how acknowledgements and retries work.
- FHIR reads (owner: your team, with the hospital’s Epic team): Your app’s registration with Epic, the medication scopes you request, and activation at each health system.
Two things are moving at once: health systems such as Stanford are bringing more pharmacy work into Epic, and the e-prescribing standard moves to SCRIPT 2023011 by 2028. Start from the entry in Epic’s catalog that your product needs, settle the six points above, and the health system’s interface team has what it needs to schedule the work.
Next read
- Epic Ambulatory guide: the outpatient workflows Willow Ambulatory serves.
- E-prescribing software features: the prescriber side of the exchange.
- Epic Bridges: how hospitals build Epic interfaces.
Where to go next
- Have us build it: Epic integration
- Run it yourself: ConnectHealth
- Prior authorization: Prior authorization services
- Talk to us: Start a Conversation








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















