Epic Beacon Oncology: Chemotherapy Treatment Plans, Order Sets, and Implementation

Epic Beacon is the most patient safety-sensitive Epic module to implement. Chemotherapy dosing errors kill people – and most Beacon implementation failures are not clinical mistakes but build configuration errors made by analysts who did not understand how treatment plans, cycle logic, and BSA-based dosing interact in Epic’s build architecture. This article gives oncology IT analysts, build specialists, and implementation leaders the depth needed to configure Beacon correctly across treatment plan build, chemotherapy order sets, cycle management, REMS compliance, and go-live validation.

What Is Epic Beacon?

Epic Beacon is Epic Systems’ oncology module. It manages the complete oncology care workflow – from cancer diagnosis and staging through treatment plan selection, chemotherapy order set build, cycle scheduling, drug administration, laboratory monitoring, and survivorship care. Beacon is used in outpatient infusion centers, inpatient oncology units, and integrated oncology programs that span both settings.

The module’s defining feature – and its defining implementation risk – is its treatment plan architecture. Beacon treatment plans are structured protocols that define every aspect of a patient’s chemotherapy regimen: the drugs, the doses, the dosing algorithms (BSA-based, weight-based, AUC-based, or fixed), the administration schedules, the cycle count, the laboratory monitoring requirements, and the pre-medication and supportive care orders. Every element of a treatment plan is a build decision made by the implementation team in collaboration with oncology clinicians.

Getting Beacon treatment plans wrong is not an abstract technical failure. A build error in a chemotherapy dosing formula can cause a patient to receive an overdose or underdose of a cytotoxic agent. That is why Beacon implementation carries clinical oversight requirements that most other Epic modules do not – a licensed oncology pharmacist or physician must review and sign off on every treatment plan before it goes live. This is not just good practice. Many health systems treat it as an institutional patient safety policy, and some treat it as analogous to a medication formulary approval. Understanding the full Epic module architecture is the starting point in the Epic EHR Learning Hub.

Beacon Chemotherapy Treatment Plans: Architecture and Build

A Beacon treatment plan (TP) is a structured, reusable protocol that defines a complete chemotherapy regimen. Treatment plans are built in Epic’s Treatment Plan (TP) master file. They are not order sets in the traditional sense – they carry cycle logic, dosing algorithms, scheduling constraints, and laboratory monitoring requirements that order sets do not. A physician selects a treatment plan for a patient, and Beacon generates the cycle-specific orders based on the patient’s current weight, BSA, renal function, and other dosing parameters at the time of each cycle.

Treatment Plan Components

Every Beacon treatment plan contains a defined set of components. The regimen name and protocol reference identifies the clinical protocol driving the treatment plan – FOLFOX, R-CHOP, AC-T, carboplatin/pemetrexed. The cycle definition specifies how many days are in each cycle and how many cycles are planned. The drug records define each chemotherapy agent, its dosing algorithm, administration route, infusion duration, and the timing within the cycle. The laboratory monitoring requirements define which labs must be checked before each cycle and what threshold results hold treatment.

Treatment plan build requires alignment with the organization’s adopted clinical protocols. Most oncology programs use nationally recognized protocol sources – NCCN (National Comprehensive Cancer Network) guidelines, cooperative group protocols (SWOG, ECOG, Alliance), or published clinical trial regimens. Build analysts must map the clinical protocol to Beacon’s build objects exactly – not approximately. A treatment plan that is “close” to the protocol is not compliant with the protocol.

Treatment Plan Library Governance

Most oncology programs implement 50 to 200+ treatment plans at go-live, depending on the service lines they support. Each treatment plan requires clinical review before activation. Build analysts must establish a treatment plan library governance process before build begins – defining which protocols are in scope, who reviews each plan, what the review and approval workflow looks like, and how updates are managed when NCCN guidelines change.

NCCN updates its guidelines multiple times per year. When a guideline changes a dosing recommendation or adds a new preferred regimen, the corresponding Beacon treatment plan must be updated before the new guideline becomes effective at your institution. A treatment plan update process that requires a 6-week review cycle creates a compliance gap between when the institution adopts the new guideline and when the Beacon build reflects it. Build analysts must design the update workflow with that timeline constraint in mind from the start.

BSA-Based Dosing and Chemotherapy Dose Calculation in Beacon

Body surface area (BSA) is the primary dosing basis for most chemotherapy agents. Beacon calculates BSA automatically from the patient’s current height and weight using a configured BSA formula – Mosteller, DuBois, or other formulae depending on the protocol and institution preference. The calculated BSA is then applied to the dose per m² specified in the treatment plan to generate the patient’s individualized dose.

Dosing Algorithm Types in Beacon

Not all chemotherapy agents use BSA-based dosing. Beacon supports multiple dosing algorithm types, and build analysts must configure the correct algorithm for each drug in each treatment plan. Using the wrong algorithm type is a high-severity build error.

Carboplatin AUC Dosing: The Most Complex Build in Beacon

Carboplatin dosing using the Calvert formula is the most complex dosing algorithm in Beacon. The Calvert formula calculates carboplatin dose as: Dose (mg) = AUC target x (GFR + 25). The GFR must be sourced from a renal function test – measured GFR or estimated GFR (eGFR) using CKD-EPI, MDRD, or Cockcroft-Gault. Each GFR estimation method produces different values, and the choice matters for dose calculation.

The FDA and ASCO issued guidance in 2010 and subsequently updated in 2023 recommending that carboplatin dosing cap GFR at 125 mL/min to prevent overdosing in patients with very high GFR values – particularly patients with high muscle mass where Cockcroft-Gault may overestimate renal function. Build analysts must configure the GFR source, the GFR estimation method, and the GFR capping rule in each treatment plan that includes carboplatin. Missing the GFR cap is one of the most common carboplatin dosing build errors.

Dose Capping and Obese Patient Dosing

Obese patient dosing is a documented area of clinical uncertainty in oncology. ASCO guidelines (2012, reaffirmed) recommend using actual body weight for BSA calculation in most chemotherapy regimens rather than ideal or adjusted body weight – contrary to the dose-capping conventions used in some institutions. Build analysts must understand the institution’s adopted dosing policy for obese patients and ensure that BSA calculation in Beacon reflects that policy – not a default setting that may differ from institutional practice.

Maximum dose caps – ceiling doses set to prevent extreme outlier doses in patients with very high BSA – must be entered in the treatment plan for every agent that has a protocol-defined cap. Build analysts should not create dose caps based on clinical judgment. Every cap value must come from the protocol document or the oncology pharmacist’s explicit instruction and must be documented in the treatment plan review record.

Cycle Management: Scheduling, Holds, and Dose Modifications

Cycle management in Beacon governs how treatment cycles are scheduled, monitored, held for toxicity, and modified over the course of a patient’s treatment. A patient on a 6-cycle regimen is not simply scheduled for 6 appointments. Each cycle requires laboratory review, a clinical assessment, a treatment decision (proceed, hold, or modify), and the generation of that cycle’s individualized orders based on current patient parameters.

Pre-Cycle Laboratory Hold Rules

Every chemotherapy treatment plan must define the laboratory values that hold treatment. A CBC showing ANC below 1,000/mm³ holds myelosuppressive chemotherapy. A creatinine above protocol-defined threshold holds nephrotoxic agents. A total bilirubin above the protocol limit holds hepatically metabolized drugs. Build analysts configure these hold thresholds in the treatment plan’s laboratory monitoring section.

The hold threshold values must match the protocol exactly. A threshold of ANC <1,000 is not the same as ANC <1,500 – the choice is clinically driven. Hold logic in Beacon generates an alert when the patient’s most recent lab value crosses the threshold before treatment is released. The build must ensure that Beacon pulls the correct lab result at the correct timing relative to treatment – typically within 14 days for most agents and within 24-48 hours for ANC-sensitive regimens.

Dose Modification Tables and CTCAE Grading

Most chemotherapy protocols include dose modification tables that specify how much to reduce a drug’s dose when the patient experiences toxicity of defined severity. The Common Terminology Criteria for Adverse Events (CTCAE) is the standard toxicity grading system used in oncology. A protocol may specify: Grade 3 peripheral neuropathy – reduce oxaliplatin by 25%. Grade 4 hematologic toxicity – hold and reassess.

Beacon supports dose modification documentation through the treatment plan’s dose level system. Build analysts configure the dose levels (100%, 75%, 50%, etc.) and the CTCAE-based criteria that drive dose level selection. The oncologist selects the dose level at each cycle based on toxicity assessment, and Beacon calculates the modified dose automatically. The build must include all dose levels specified in the protocol – not just common reduction levels.

Chemotherapy Order Sets and SmartSets in Beacon

Beacon uses two mechanisms for chemotherapy ordering: treatment plan-generated orders (the primary mechanism for ongoing chemotherapy cycles) and standalone SmartSets (used for supportive care, single-agent orders outside a treatment plan, and rescue medications). Understanding which mechanism applies to which clinical scenario is one of the first workflow design decisions in a Beacon implementation.

Treatment plan-generated orders carry all the dosing algorithm logic, cycle sequencing, and monitoring requirements of the parent treatment plan. They are the correct mechanism for all multi-agent chemotherapy regimens given on a defined cycle schedule. Standalone SmartSets are appropriate for single-agent infusions given outside a formal cycle structure, colony-stimulating factors given independently, or anti-nausea medications ordered between infusion visits. Using a SmartSet for a multi-agent regimen that should be on a treatment plan removes all the safety guardrails that the treatment plan provides.

Build analysts need to understand how Beacon’s CPOE framework integrates with treatment plan ordering. The treatment plan-based order entry workflow is distinct from standard CPOE order entry. Providers select a treatment plan, confirm the cycle, review the generated orders with the BSA-calculated doses, and sign. The CPOE integration is tightly coupled – analysts who work with Epic EHR Orders and CPOE workflows will find the treatment plan-to-order generation path unfamiliar and must learn it specifically for Beacon.

REMS Compliance and High-Alert Medication Workflows in Beacon

Risk Evaluation and Mitigation Strategies (REMS) are FDA-mandated safety programs for drugs with serious or life-threatening risks. In oncology, multiple high-use agents require REMS enrollment – thalidomide and lenalidomide (THALOMID/REVLIMID REMS), certain immunotherapy agents with REMS requirements, and newer targeted agents as they enter the market. Beacon must enforce REMS requirements before allowing ordering, dispensing, or administration.

Thalidomide / Lenalidomide REMS: The Most Complex Oncology REMS Build

The THALOMID REMS and REVLIMID REMS (now combined under the Celgene REMS program, managed by Bristol Myers Squibb) require patient enrollment, prescriber certification, pharmacy certification, pregnancy testing for female patients of reproductive potential, contraception counseling, and periodic attestation from both the patient and prescriber. Beacon’s REMS workflow enforces these requirements at order entry – a prescriber who is not certified in the REMS cannot complete the order. A patient who has not completed the required monthly pregnancy test cannot receive the next prescription.

Build analysts configure REMS requirements in Beacon’s drug record and treatment plan. The configuration must define which certifications are required, what documentation is needed, and what the system response is when requirements are not met. The REMS configuration must be reviewed and approved by the oncology pharmacy team before go-live – this is a regulatory compliance requirement, not just a build quality gate.

High-Alert Medication Safeguards in Beacon

Beyond REMS, all chemotherapy agents are classified as high-alert medications under ISMP (Institute for Safe Medication Practices) guidelines. High-alert medication safeguards in Beacon include dual pharmacist verification requirements, independent dose calculation checks, hard-stop alerts for doses that exceed protocol-defined maximums, and nursing administration verification at the point of infusion. Build analysts configure these safeguards in coordination with the pharmacy and nursing leadership teams.

Intrathecal chemotherapy requires special workflow configuration. Methotrexate and cytarabine administered intrathecally have caused patient deaths when confused with intravenous preparations. Beacon must be configured to prevent intrathecal medications from appearing in intravenous order lists and vice versa. This is a patient safety critical build requirement – the Joint Commission and ISMP both have specific guidelines on intrathecal medication safety that Beacon build must reflect.

Supportive Care Orders and Antiemetic Protocols in Beacon

Supportive care orders are the medications and interventions given alongside chemotherapy to manage side effects and prevent complications. They include antiemetics for nausea prophylaxis, colony-stimulating factors (G-CSF, such as filgrastim or pegfilgrastim) for neutropenia prevention, corticosteroids as premedications and anti-inflammatory agents, hydration protocols, and tumor lysis prophylaxis for high-risk regimens.

Antiemetic Protocol Build

Chemotherapy agents are classified by their emetogenic risk – high, moderate, low, or minimal emetic risk per ASCO and NCCN antiemetic guidelines. The antiemetic protocol assigned in a Beacon treatment plan must match the emetogenic classification of the chemotherapy regimen. A highly emetogenic regimen (cisplatin, doxorubicin/cyclophosphamide AC) requires a three-drug antiemetic protocol: a 5-HT3 antagonist (ondansetron), an NK1 antagonist (aprepitant), and a corticosteroid (dexamethasone).

Build analysts configure antiemetic orders as part of the treatment plan’s supportive care section. The antiemetic orders must specify the pre-chemo, day-of, and post-chemo medication schedule – not just the day-of infusion dose. Patients who go home with inadequate antiemetic coverage after highly emetogenic chemotherapy are at high risk for dehydration, emergency department visits, and treatment delays. The antiemetic protocol build is reviewed by oncology pharmacy before go-live.

G-CSF and Growth Factor Configuration

Granulocyte colony-stimulating factors (G-CSF) are given after chemotherapy to stimulate white blood cell recovery and reduce the risk of febrile neutropenia. NCCN guidelines define G-CSF use based on the febrile neutropenia risk of the regimen – greater than 20% risk (high-risk) warrants prophylactic G-CSF with every cycle. Intermediate-risk regimens (10-20%) may warrant G-CSF based on patient-specific risk factors.

Build analysts configure G-CSF orders in the treatment plan starting day relative to chemotherapy – typically day 3 or 4 after the last chemotherapy dose, not on the day of chemotherapy. Pegfilgrastim (Neulasta) is given as a single dose 24 hours after the last chemotherapy dose. The timing configuration in Beacon must be precise – G-CSF given on the same day as chemotherapy or too early can mobilize hematopoietic progenitors that may be damaged by the concurrent cytotoxic therapy.

Beacon Integrations: Willow, Beaker, and HL7 FHIR

Beacon does not function as a standalone module. It depends on tight integration with Epic Willow (pharmacy), Epic Beaker (laboratory), and the Epic clinical documentation framework. It also exposes oncology data to external platforms through HL7 FHIR APIs.

Willow Pharmacy Integration

When a Beacon treatment plan order is signed, it routes to the oncology pharmacy’s Willow queue for verification. The pharmacist verifies the BSA calculation, reviews the generated dose against the treatment plan parameters, checks drug interactions, and releases the order for compounding. Build analysts must configure the oncology pharmacy routing rules in Willow to ensure that chemotherapy orders route to the correct oncology pharmacy queue – not to a general inpatient or outpatient pharmacy queue where the verifying pharmacist may not have oncology certification.

IV compounding workflow in Willow connects to the pharmacy robotics and IV preparation tracking. For oncology programs using IV preparation robotics (BD Pharmacy Connect, Omnicell IV compounding) or manual gravimetric verification systems, the Willow interface must be configured and tested to ensure chemotherapy compounding records link correctly to the Beacon treatment plan. This integration requires coordination between the Beacon build team, the Willow build team, and the pharmacy informatics team.

Beaker Laboratory Integration

Beacon pulls laboratory values from Beaker to drive pre-cycle lab hold logic and dose modification decisions. The CBC with differential (for ANC), comprehensive metabolic panel (for creatinine, bilirubin, and liver enzymes), and tumor markers are the most common lab types referenced in Beacon’s treatment plan monitoring configuration. Build analysts must ensure that the lab result components referenced in Beacon’s hold logic map correctly to the result component records in Beaker.

If the ANC result component in Beaker has a different internal name or ID than what Beacon’s treatment plan references, the hold logic will not fire when it should. This is a silent failure – the system does not generate an error. It simply does not evaluate the lab hold rule. Testing must explicitly verify that lab hold alerts fire when lab values cross the configured thresholds, using real or simulated lab results in the test environment.

HL7 FHIR and Oncology Data Exchange

Beacon treatment plan and administration data are increasingly accessed through Epic’s HL7 FHIR R4 API by external oncology platforms – cancer registries (NAACCR-compatible extracts), clinical trial management systems (CTMS), and real-world data platforms used for outcomes research. The HL7 FHIR MedicationRequest resource maps to Beacon chemotherapy orders. The HL7 FHIR CarePlan resource maps to Beacon treatment plans. The Condition resource maps to oncology diagnoses and staging data.

Build analysts implementing Beacon with external platform integrations must verify that the FHIR API returns the expected treatment plan and medication data – including BSA-calculated doses, cycle numbers, and administration dates. The documentation quality in Beacon directly affects what the FHIR API exposes. The EpicCare Inpatient ClinDoc guide covers how documentation completeness affects downstream data availability across Epic’s clinical modules.

Testing and Validation Strategy for Epic Beacon

Beacon testing has a clinical validation component that is as important as technical QA. The technical team validates that the system does what the build says. The clinical team validates that the build says the right thing. Both are required. Neither is sufficient alone.

Treatment Plan Clinical Review Process

Every treatment plan must undergo a structured clinical review before activation. The review process should include a pharmacist review of all dosing algorithms, dose caps, and administration parameters; an oncologist review of the cycle structure, hold thresholds, and dose modification tables; and a nursing review of the infusion sequence, pre-medication orders, and reaction management protocols. Each reviewer should use a structured checklist against the source protocol document – not a general impression review.

Teams familiar with BAT vs UAT methodology will recognize that Beacon treatment plan review is a form of clinical BAT – acceptance testing by the clinical users who will operate the system in production, validating that the clinical logic is correct, not just that the system functions.

Dosing Calculation Validation

Dosing calculation validation requires test patients with defined height, weight, and renal function parameters. The expected dose for each test patient should be manually calculated from the protocol formula before testing. The Beacon-generated dose should then be compared against the manually calculated dose. Any discrepancy above a defined tolerance (typically less than 1% for rounding) requires investigation before the treatment plan can be activated.

Test patients should include edge cases: a patient with very high BSA to test dose capping, a patient with low renal function to test GFR-dependent dosing, and a patient with normal values to confirm standard dosing. For carboplatin, test patients should include a case where the uncapped GFR exceeds 125 mL/min to verify the GFR cap activates correctly.

Lab Hold Alert Validation

Lab hold alert testing requires simulating lab results in the test environment that cross each configured threshold. For a treatment plan with an ANC hold at 1,000/mm³, test with an ANC of 999 (should hold), 1,000 (boundary – confirm which side the boundary lands on), and 1,001 (should not hold). For each hold threshold, document the expected system response and verify it matches. Hold alert validation is a non-negotiable step in Beacon testing – it cannot be skipped because lab hold failures are patient safety events.

Go-Live Planning and Common Beacon Implementation Failures

Beacon go-live carries the highest patient safety stakes of any Epic module. Chemotherapy errors are not forgiving. Go-live planning must include a period of supervised chemotherapy ordering where an oncology pharmacist reviews every treatment plan activation and dose calculation for the first week post-go-live, independent of the standard pharmacy verification workflow. This is not a permanent process – it is a safety net during the stabilization period. The Epic EHR Go-Live Support framework covers the command center model – for Beacon, add an oncology pharmacist with treatment plan build access as a required command center member.

Roles, Certifications, and Career Path for Beacon Specialists

Authoritative References

• NCCN – Clinical Practice Guidelines in Oncology: Antiemesis, Myeloid Growth Factors, and Disease-Specific Regimens
• FDA – Risk Evaluation and Mitigation Strategies (REMS): Current REMS Programs and Requirements

Downloads: Beacon Oncology Templates and Checklists