All articlesIndustry

Head and Neck Cancer Surgery-to-Chemo Toxicity Data Gaps

When head and neck cancer patients move from surgery to adjuvant chemotherapy, structured toxicity data routinely fails to follow. This article examines the three failure points that create the gap and what clinic operators should demand from platform software.

Head and Neck Cancer Surgery-to-Chemo Toxicity Data Gaps

Head and neck cancer surgery often takes weeks of recovery before adjuvant chemotherapy can begin. That interval - recovery, staging review, wound assessment - should also be the window where toxicity data moves from the surgical team to the medical oncology team. In most clinics, it doesn't.

The result is a medical oncologist who starts chemotherapy planning with an incomplete baseline. Swallowing function scores from the surgical record sit in a separate system. Nutritional markers from the inpatient stay don't get pulled forward. Baseline renal function - critical before platinum-based regimens - has to be re-ordered because the surgical labs live in a different module or a different facility's system. This is not rare. It's structural.

The shape of the transition

Head and neck squamous cell carcinoma frequently presents at locally advanced stages, where surgical resection is followed by adjuvant chemoradiotherapy for patients with high-risk pathological features such as extracapsular nodal extension or positive surgical margins. A 2024 systematic review and meta-analysis confirmed that postoperative chemoradiotherapy remains the standard adjuvant approach for these patients, with cisplatin-based regimens demonstrating advantages in locoregional control.

That means the surgery-to-chemo handoff is not an edge case. For a substantial proportion of patients who undergo primary surgical resection for locally advanced head and neck cancer, adjuvant systemic therapy follows within weeks. Each one of those transitions is a moment where structured toxicity data needs to cross from one clinical team to another. In clinics without a unified platform, that crossing is usually incomplete.

What toxicity data is at stake

Toxicity data in this context means more than a list of postoperative complaints. It includes:

  • Baseline Common Terminology Criteria for Adverse Events (CTCAE) grades for swallowing dysfunction, mucositis, and peripheral neuropathy, recorded before any systemic therapy begins
  • Nutritional status indicators - weight trend, serum albumin, and whether a feeding tube was placed during surgical recovery
  • Renal function labs from the inpatient stay, which determine eligibility and appropriate dosing for platinum-based regimens
  • Pain scores and analgesic burden from the surgical admission, which indicate baseline functional and performance status
  • Wound healing status and any surgical complications documented before the patient transfers to outpatient medical oncology

Each of these data points should inform how the chemotherapy team calibrates the first cycle. When those data points are missing, clinicians either delay the start of therapy while gathering information or proceed with assumptions. Both outcomes carry clinical and operational cost.

Three failure points in the handoff

A recent scoping review of care transitions in head and neck cancer found a specific evidence gap: transitions during active treatment - the phase between surgical discharge and the start of adjuvant therapy - remain poorly studied compared to pre-treatment or post-treatment transitions. The authors noted that patients and clinicians face challenges related to care coordination, multiple electronic health records, and extensive follow-up requirements across the full treatment arc.

Three structural failure points drive this gap.

Separate teams, separate workflows. Surgical oncology and medical oncology use different systems for notes and orders. Even within a single hospital system, the surgeon's postoperative notes are meant to support surgical decisions, not to provide a baseline for chemotherapy. The medical oncologist gets a narrative note instead of structured data.

Free-text documentation of graded toxicity. CTCAE grading works best when it's structured and searchable. In practice, swallowing grade and mucositis severity often show up as prose in a clinic note instead of as a field the next clinician can filter or track across visits. This forces re-grading from scratch, or relying on memory from a tumor board meeting weeks before chemotherapy starts.

System boundaries at facility handoffs. When a patient moves from an inpatient surgical unit to an outpatient infusion center - or from a surgical center to a separate cancer center - the data problem gets bigger. A study in JCO Oncology Practice found that ineffective handoffs between oncology settings contribute to care gaps and medication errors, and that treatment information ends up scattered across order-entry systems, free-text reports, and specialized chemotherapy management software with no common structure.

What the data shows about downstream consequences

The effects of handoff failures are visible in surveillance adherence figures. Research on head and neck cancer care at a safety-net hospital, published via PMC, found that adherence to posttreatment visits dropped from 69% in year one to 47% by year five. The same study documented confusion among care providers about who is responsible for surveillance testing once a patient transitions between teams.

That ambiguity does not begin at survivorship. It begins at the first major handoff - surgery to adjuvant chemotherapy - where no standard process says what toxicity data should move and who must confirm receipt before the planning appointment is scheduled.

The practical result: medical oncologists sometimes re-order baseline labs not because the initial values were abnormal, but because they cannot find or trust the values from surgery. For renally-dosed agents, that delay is measurable in days. For a patient whose nutrition status was borderline at surgical discharge, the missing data at the chemo planning appointment often means a delayed cycle while nutrition support is reassessed from the start.

The documentation infrastructure problem

Research on oncology EHR systems has shown that care coordination suffers from scattered information. A survey of oncologists published in JCO Clinical Cancer Informatics found that clinicians say scattered data gets in the way of care coordination across provider transitions. Toxicity grading and lab baselines were the fields clinicians most often cited as hard to find from previous visits.

For head and neck cancer, where the treatment sequence routinely crosses from a surgical oncologist to a radiation oncologist to a medical oncologist, the problem gets worse with each handoff. Each transition is another chance for a structured toxicity score to get buried in a PDF, a scanned document, or a note in a system the receiving clinician can't access.

This is a workflow problem before it is a technology problem. The workflow answer is a treatment record that follows the patient across modality boundaries rather than resetting at each one. When a platform tracks swallowing grade from the surgical encounter forward - without requiring manual re-entry by the receiving team - the medical oncologist opens the planning visit with a pre-populated toxicity baseline rather than a blank field. That is the difference between a 10-minute chart review and a 40-minute re-evaluation.

For oncology clinic operators evaluating how their platform handles this, the key question is not whether the system stores prior notes. It is whether the platform surfaces prior toxicity grades as structured, sortable data at the point of care for the next team. For more information on how continuous treatment timelines carry this context across care phases, read about why oncology clinics need treatment timelines, not just calendars.

The same continuity challenge appears across cancer types wherever multimodal therapy crosses team boundaries. Read about closing colorectal cancer surveillance gaps after surgery, which covers a related failure pattern in the post-surgical follow-up phase. And for a closer look at how lab data from previous encounters becomes useful information for the receiving clinician, see how AI lab extraction changes clinical routine.

What platform buyers should ask

Clinic operators evaluating oncology software for head and neck cancer programs should bring three questions to any vendor demo.

  • Does the platform carry CTCAE-graded toxicity scores as structured, queryable fields across surgical and systemic therapy encounters, or does that data live only inside free-text notes?
  • Can the medical oncology team view surgical labs from the inpatient stay without requesting a manual export or logging into a separate system?
  • Does the scheduling module flag when a toxicity baseline field has not been completed before a chemotherapy planning visit is booked?

These are not advanced feature requests. These are baseline requirements for any platform that supports multimodal cancer care. In head and neck cancer, where treatment routinely moves between specialists, a platform that treats each specialty as separate will cause the same data loss that exists in paper-based workflows and legacy EHR systems.

Book a demo to see how treatment timelines and lab intelligence modules handle surgical-to-systemic toxicity handoffs.

See Rucja on your own hospital data.

Demos take 30 minutes. We'll walk you through the bits of this article in your live workflow.

Book a demo