Hypereosinophilic Syndrome and a Fusion Gene Result That Hasn't Come Back Yet
A single patient with eosinophil counts and organ findings that fit one diagnosis strongly, confirmed by nothing yet. The disagreement is whether to treat the pattern now or wait a week for the test that would actually name it.
Devon R. runs a landscaping business he built from a single mower fifteen years ago, and until three weeks ago the only thing slowing him down was a knee from an old fall off a ladder. Progressive shortness of breath climbing the steps of his own truck brought him in, and what looked at first like it might be cardiac sent the workup somewhere else entirely: an eosinophil count of 18,400 per microliter, sustained on repeat, an elevated serum tryptase, a palpable spleen, and an echocardiogram showing early endocardial thickening at the apex — the kind of finding that, left alone, tends toward endomyocardial fibrosis rather than away from it. Taken together, the triad of marked eosinophilia, elevated tryptase, and splenomegaly is the pattern most closely associated with the myeloproliferative variant of hypereosinophilic syndrome, the one driven by the FIP1L1-PDGFRA fusion gene — but the actual FISH test that would confirm or exclude it won't result for about a week.
That week is the entire disagreement. FIP1L1-PDGFRA-positive disease responds to imatinib with a reliability that borders on the absolute, though the paper usually cited for it doesn't quite say so: Cools and colleagues' 2003 description treated eleven unselected hypereosinophilic-syndrome patients and saw nine respond, but the fusion gene was confirmed in only five of those nine — the near-universal response rate belongs to the later series that enrolled fusion-positive patients specifically, at low doses that would be considered subtherapeutic in BCR-ABL-driven disease. The strong claim attaches to a population Devon hasn't yet been shown to be in. But imatinib does nothing for FIP1L1-PDGFRA-negative HES, and a real, separate concern named plainly in the literature is that structural cardiac damage — unlike the eosinophil count itself — doesn't reliably reverse once treatment starts, whichever drug ends up being the right one. Devon's echo already shows early changes. The team is deciding how much weight a still-pending test should carry against a heart that may not be waiting for it.
One more detail bears directly on how the week ahead should be spent: Devon has already told the team he can't simply stop working while he waits, since the business has no one else to run it and two crews depend on him for their paychecks. That isn't a reason to change the medical plan, but it does shape how closely he can actually be watched for the coming week — daily labs and a repeat echo are easy to order and much harder for him to show up for if he's out running equipment on job sites most of the day, a real logistical constraint the team has to plan around rather than assume away.
Waiting on FISH, with an echo that already shows early change
I'd start imatinib now. This triad — tryptase, splenomegaly, this degree of eosinophilia — is about as suggestive of fusion-positive disease as it gets short of the test itself, and the fusion-positive series published since Cools's original description put the response rate in that population close to universal, at low doses that are well tolerated. I'd concede Cools's own eleven patients weren't selected for the fusion — it's the later fusion-positive cohorts carrying that number, not the 2003 paper by itself.
Structural cardiac damage doesn’t reliably reverse once it’s underway, whatever we eventually treat it with — that’s the part making me reluctant to wait out a confirmatory result on a heart that’s already showing early changes.I take the myocardial risk seriously, which is exactly why I don't want to give him a drug that does nothing if he turns out fusion-negative. Corticosteroids act broadly across essentially every HES variant and would start working on the eosinophil-mediated injury today, not in a week.
Your response-rate number is real, but it’s conditional on a diagnosis we don’t have yet. I’d rather start the drug that helps regardless of which variant this turns out to be, and add the targeted one once we actually know.
I don't think this has to be either drug alone. Start corticosteroids today — that addresses the acute process safely no matter which variant this is — and hold imatinib specifically until FISH returns, which by the lab's own estimate is about a week away, not an open-ended wait.
That sequencing doesn't concede either of your positions is wrong. It just treats 'start something now' and 'confirm before committing the targeted drug' as compatible instructions rather than opposing ones, given how short the actual delay is.
Agreed: start prednisone today as an immediate, variant-agnostic bridge, with cardiology following his echocardiographic findings closely, and imatinib started the moment FISH confirms fusion-positive disease.
Not agreed, and left explicit rather than resolved by the sequencing compromise:
The hematologist-oncologist would still argue, in retrospect, that starting imatinib on the day of presentation would have given his myocardium a week's head start on treatment it turned out to need.
The cardiologist would consider the sequencing decision fully vindicated — a week of imatinib in a fusion-negative patient would have delayed nothing and helped nothing.
Both outcomes are named in advance rather than argued out today. Whichever way FISH comes back, the team agreed the sequencing itself won't be revisited as a mistake — only as a bet that either paid off or didn't.