It's two in the morning and the platelet count didn't move. You gave a full adult dose, ABO-compatible, straight off the agitator, room temperature the whole way, and the post-transfusion count looks almost identical to the pre-transfusion count. The reflex is to order more platelets. Sometimes that's right. Often it isn't, and knowing the difference is the entire point of this post. You cannot adjudicate refractoriness without a post-transfusion count This sounds obvious written down, and it is routinely skipped anyway. Teams give the platelets, move on to the next task, and never draw the count that would actually tell them whether the transfusion worked. Without a post-transfusion increment, "the patient seems refractory" is a clinical impression, not a diagnosis, and it's an impression you can't act on. If refractoriness is even on your differential, the single most important order you can write is the post-transfusion count itself, timed appropriately, before you order anything else. What actually counts as refractoriness A single low increment isn't refractoriness either. It's a data point. The corrected count increment, or CCI, standardizes the response for body size and dose, so you're comparing apples to apples across patients: CCI = (platelet increment) × (body surface area in m²) / (platelets transfused, ×10¹¹) The TRAP study, the trial that anchors most of our modern definitions, called a patient refractory when the 1-hour CCI was under 5,000 on two sequential ABO-identical, fresh platelet transfusions [1]. Most clinical references use a slightly more generous cutoff, treating a 1-hour CCI under 7,500 to 10,000 as an inadequate response [2][3]. Either way, the key word is sequential. One bad number after one transfusion tells you almost nothing, and you need that number in the first place. Two bad numbers in a row is when you start believing it. Timing matters as much as the number itself. A low 1-hour CCI points toward immune-mediated destruction, the antibody-coated platelets are being cleared almost as fast as they go in. A 1-hour count that looks fine, followed by a 24-hour count that's collapsed, points away from immune causes and toward ongoing consumption instead [2]. Non-immune causes come first, and they're the majority This is the part that gets skipped in the rush to order an antibody workup. Sixty to eighty percent of refractory cases are non-immune [2]. Fever, sepsis, active bleeding, DIC, splenomegaly, and drugs like amphotericin B are all consuming or sequestering platelets faster than transfusion can replace them, and no amount of specially selected product will fix a problem that isn't immunological. Even in patients who do have alloimmunization, non-immune factors are frequently present alongside it, muddying the picture further [2]. Practically: before you reach for an antibody workup, ask whether the patient is febrile, septic, bleeding, DIC'ing, or splenomegalic. If the answer is yes to any of those, you may already have your explanation, and the next step is treating that, not chasing platelets. HLA and HPA are separate workups, not one workup with two names Once non-immune causes have been reasonably excluded, the two immune mechanisms get worked up differently, and they're often conflated when they shouldn't be. HLA alloimmunization is, by a wide margin, the most common immune cause of platelet refractoriness. HPA alloimmunization is considerably rarer, but it stays on the differential, because it won't show up on an HLA workup and a rare cause you didn't test for is still a cause you missed. For HLA: start with an HLA antibody screen. If antibodies are detected, the next step is calculating the panel reactive antibody, or PRA, which estimates the percentage of the general donor population the patient would be incompatible with. A PRA above 20% is generally the threshold for pursuing selected platelet support; below that, enough of the standard donor pool remains compatible that special selection usually isn't worth the delay. For HPA: this is a separate antibody, against platelet-specific antigens rather than HLA, and it requires its own test, a platelet antibody screen, distinct from the HLA workup entirely. If HLA testing comes back unrevealing and immune refractoriness is still suspected, the platelet antibody screen is the next step, not a repeat of the HLA testing. Management, and the terminology that actually matters Once HLA antibodies are confirmed and PRA clears that 20% threshold, the product you're ordering is HLA-compatible platelets, not HLA-matched. The distinction is real: HLA-matched means finding a donor whose HLA type mirrors the patient's, antigen for antigen, which is a narrow and often impractical ask. HLA-compatible means selecting donors who lack the specific antigens the patient has already formed antibodies against, which is a much larger and more workable donor pool. In practice, compatible is what gets ordered and what's actually achievable; matched is closer to a theoretical ideal than a standing option. Even HLA-compatible platelets don't guarantee a good response. Compatibility improves the odds; it doesn't promise them, and suboptimal increments still happen on selected product, which brings you right back to needing a post-transfusion count to know whether this round worked either. ABO-matched, fresh (under 48 hours) platelets tend to survive better even before you get to HLA selection, which is a low-cost first move worth trying regardless of suspected mechanism. Beyond that, options like IVIG or splenectomy get mentioned in the refractoriness conversation, but the evidence supporting either as a reliable fix for platelet-specific alloimmune refractoriness is thin, and neither should be reached for as a first-line answer. The actual point When the count doesn't move, or seems like it doesn't, the reflexive answer is "more platelets." But you don't actually know it didn't move unless someone drew the count. Once you have that number, often the correct next answer is "not platelets at all, fix the fever," and sometimes it's "differently selected platelets." The CCI, and knowing which antibody workup you're actually running, is how you figure out which question you're answering. References Trial to Reduce Alloimmunization to Platelets Study Group. Leukocyte reduction and ultraviolet B irradiation of platelets to prevent alloimmunization and refractoriness to platelet transfusions. N Engl J Med. 1997;337(26):1861-1869. Platelet Refractoriness. Transfusion Medicine. PathologyOutlines.com. Accessed September 2026. Evaluation of Platelet Refractoriness. UW Hematology. University of Wisconsin School of Medicine and Public Health. Accessed September 2026.

Somewhere in this patient's chart, someone typed "IgA deficient." That's it. No level, no antibody status, no history of a reaction. Just the label. And because the label exists, an order goes in for washed red cells and IgA-deficient plasma, every time, for the rest of this person's transfusion history, because that's what you do when someone is IgA deficient. Except I'm not sure any of us fully know what we're protecting against. What actually counts as IgA deficient, for us Immunology's threshold for selective IgA deficiency is a serum IgA under 7 mg/dL with normal IgG and IgM. That's common. Estimates range from roughly 1 in 300 to 1 in 1,000 people in Western populations, depending on the study and the assay [1][2]. This is not a zebra. Most of these people are asymptomatic and will never know they have it. Transfusion medicine uses a stricter cutoff: less than 0.05 mg/dL, confirmed by a specialized assay currently available only as a send-out through the American Red Cross. A result below that threshold reflexes automatically to anti-IgA antibody testing. So the actual transfusion-relevant workup is a two-step process, hard to access, testing for a rarer and more severe deficiency than the general immunology definition implies. And then, once you have both pieces, severe deficiency confirmed and anti-IgA detected, you still don't have an answer to the question that actually matters: will this person react. Anti-IgA is common, and its presence doesn't tell you much Roughly 20 to 40% of IgA-deficient patients develop anti-IgA antibodies [2][3]. If presence of the antibody reliably predicted anaphylaxis, that would be a lot of predictable anaphylaxis. It isn't, and it doesn't. The most direct evidence against pathogenicity comes from Robitaille et al., who compared transfusion outcomes from IgA-deficient donors with and without anti-IgA and found no increased rate of allergic reactions in recipients of anti-IgA-containing components [4]. A separate study of apheresis platelets from anti-IgA-positive, IgA-deficient donors found the same thing: no meaningful increase in reactions compared to standard donors [5]. People are, apparently, routinely receiving anti-IgA passively and tolerating it without incident. The literature on the other side isn't clean either. Case series and reviews describe patients with anti-IgA and no reactions, and patients with reactions and no detectable anti-IgA, with no consistent relationship between antibody titer and reaction severity [6][7]. Some patients who reacted once to one product subsequently tolerated other IgA-containing products without issue. If anti-IgA were the mechanism, that inconsistency shouldn't exist. The numbers, put together Transfusion-related anaphylaxis overall happens in roughly 1 in 20,000 to 1 in 47,000 transfusions [2][8]. Of anaphylactic transfusion reactions specifically, anti-IgA is estimated to account for somewhere around 1 to 5% in Caucasian populations [8], and at least one estimate puts anti-IgA-attributable anaphylaxis at under 1 in 500,000 components transfused [8]. So: a rare event overall, a small fraction of that rare event plausibly attributable to anti-IgA, and even within that fraction, an antibody whose presence doesn't reliably distinguish who reacts from who doesn't. What guidelines actually say, versus what charts actually say This is where it gets interesting, because the professional guidance is more conservative than routine practice. Canadian Blood Services recommends anti-IgA testing only after a documented anaphylactic reaction or two severe allergic reactions, not as a prophylactic screen [8]. Pathology references summarizing current practice are blunter still: IgA-deficient patients should be worked up appropriately and do not require washed products unless a documented severe reaction has already occurred [9]. That is not what "IgA deficient" typically triggers in practice. In practice, the label alone, often without a confirmed level, without antibody testing, and without any reaction history, is enough to generate a standing order for washed cellular products and IgA-deficient plasma indefinitely. Where I land I think we overtreat this. Not recklessly, and not without a defensible history behind why the practice exists. But the evidence base for "anti-IgA in the absence of a prior reaction requires special products" is thinner than the reflexiveness of the ordering pattern suggests. The one group where the caution is clearly earned is the subset with severe deficiency by the strict cutoff, confirmed anti-IgA, and a documented prior reaction. Everyone else on this spectrum, and it's a wide spectrum given how common IgA deficiency actually is, may be getting a more restrictive product than the data justify. I don't think this is a case of the evidence being ignored so much as the evidence never quite catching up to the caution that got built into practice decades ago, and nobody circling back to ask whether the caution still fits what we now know. Washing red cells and sourcing IgA-deficient plasma isn't free. It costs time, it costs product availability, and for a rare-antigen patient already competing for limited units, it can mean the difference between finding compatible blood in an hour versus a day. So the next time "IgA deficient" shows up in a chart with no further detail, I think the right question isn't "did we wash the cells." It's "do we actually know this patient needs that." References Fernandez J, Mandell BF. Selective IgA Deficiency. MSD Manual Professional Edition. Reviewed/Revised October 2024. Selective IgA Deficiency. StatPearls [Internet]. NCBI Bookshelf. NBK538205. Updated June 26, 2023. Transfusion Selective IgA Deficiency. StatPearls [Internet]. NCBI Bookshelf. NBK564340. Updated February 24, 2025. Robitaille N, Delage G, Long A, Thibault L, Robillard P. Allergic transfusion reactions from blood components donated by IgA-deficient donors with and without anti-IgA: a comparative retrospective study. Vox Sang. 2010;99(2):136-141. Winters JL, et al. Transfusion of apheresis PLTs from IgA-deficient donors with anti-IgA is not associated with an increase in transfusion reactions. Transfusion. 2004;44(3):382-389. Collet A, de Chambure DP, Moitrot E, et al. Non-allergic Hypersensitivity Reactions to Immunoglobulin Preparations in Antibody Deficiencies: What Role for Anti-IgA IgG and Complement Activation? Clin Rev Allergy Immunol. 2024. Odineal DD, Gershwin ME. The Epidemiology and Clinical Manifestations of Autoimmunity in Selective IgA Deficiency. Clin Rev Allergy Immunol. 2020. Anaphylactic transfusion reactions and IgA deficiency. Canadian Blood Services Professional Education. Accessed 2026. Allergic / anaphylactic. Transfusion medicine. PathologyOutlines.com. Accessed September 2026.

The blood supply is short again. It's short often enough that "short" undersells it, this is closer to a chronic condition than an emergency. So the question comes up, reasonably, from patients, from colleagues outside the field, sometimes from residents who assume someone must have solved this by now: why can't we just make blood? The honest answer is that people have been trying for over a century, and it's worth being clear-eyed about why before getting excited about where things stand now. The part that didn't work Hemoglobin-based oxygen carriers, cell-free hemoglobin packaged to carry oxygen the way red cells do, looked like the obvious answer for decades. Several made it deep into clinical development: HemAssist, PolyHeme, Hemolink, Hemospan. All were eventually discontinued. Free hemoglobin outside a red cell membrane scavenges nitric oxide, which is the molecule that keeps blood vessels relaxed, and the resulting vasoconstriction was linked to safety concerns, including cardiac events, serious enough that none of these products gained lasting traction. There's genuine debate about how solid that signal actually was, I've written elsewhere about the meta-analysis that's often credited with sinking the field, and I won't relitigate it here, but the practical upshot for the field was the same either way: the products didn't make it to market, and momentum stalled. That history matters as context for what follows, because the newer approaches aren't ignoring that failure. They're built directly in response to it. ErythroMer: the encapsulation fix ErythroMer, developed by KaloCyte, takes a different structural approach: instead of free hemoglobin in solution, the hemoglobin is encapsulated in a lipid-peptide nanoparticle designed to limit exactly the nitric oxide interaction that caused trouble before. It's also freeze-dried, meaning it can be stored stable and reconstituted when needed, which is a meaningfully different profile than a product requiring refrigeration and a short shelf life. The Defense Advanced Research Projects Agency backed this approach with a $46 million grant aimed at a field-deployable, shelf-stable blood substitute, with ErythroMer as the core technology. This is still in development, not in routine clinical use, but the engineering logic is a direct answer to the specific mechanism that sank the earlier generation. RESTORE: blood grown in a lab A different approach entirely: growing actual red blood cells from donor stem cells in the lab, then transfusing them. The RESTORE trial, run by NHS Blood and Transplant and the University of Bristol, became the first in the world to transfuse laboratory-grown red cells into another person. Volunteers receive mini-transfusions of both lab-grown and standard donated cells from the same source donor, allowing a direct comparison of how long each population survives in circulation. The important caveat, and the researchers have been explicit about this: the goal isn't replacing blood donation at scale. It's aimed at patients who are hard to transfuse safely through the conventional donor pool, people with rare blood phenotypes or significant alloimmunization, where finding compatible units the usual way is already a struggle. This is a precision tool for a specific hard problem, not a fix for Tuesday's shortage. Platelets are getting their own version of this Red cells aren't the only shortage. Freeze-dried platelet substitutes like Thrombosomes are in parallel development, aimed less at routine platelet support and more at hemostatic emergencies, trauma, austere environments, situations where getting a normal platelet unit to the bedside in time isn't realistic. It's a quieter research track than the red cell substitutes, but it's answering a real and distinct gap. What's actually reached a patient Of everything in this space, Hemopure is the one product that's actually in clinical use anywhere, and it's worth being specific about what it is. Hemopure (HBOC-201) is itself one of the original generation of hemoglobin-based oxygen carriers, the same era as HemAssist, PolyHeme, and Hemolink, but built differently. Where PolyHeme used human hemoglobin with pyridoxylation and glutaraldehyde polymerization, and Hemolink used human hemoglobin crosslinked with o-raffinose into a smaller oligomer, Hemopure uses bovine hemoglobin polymerized with glutaraldehyde into a notably larger molecule, averaging around 250 kDa. That different chemistry and different molecular weight profile is generally credited as part of why it's the one product from that generation still standing. It's approved in South Africa and available in the US under FDA expanded access for specific situations. That's a meaningfully lower bar than "solved," but it's real-world use, not just a promising abstract, and it's worth naming as the one concrete data point that artifiical blood products can reach a patient at all. Where that leaves us None of this fixes this month's shortage. ErythroMer is still in development. RESTORE is aimed at a narrow, difficult patient population, not the general supply problem. Hemopure's footprint is small and geographically limited. If you're standing in a blood bank today trying to find units for a patient, none of this helps you yet. But "not yet" is a genuinely different sentence than "never," and that's the honest distinction worth holding onto. The current generation of approaches is responding directly to the specific failure modes of the last one, which is not something the field could always say. It's also not close enough to change how any of us practice this year, or probably this decade. Optimistic, in this field, has to mean optimistic about the trajectory. It can't yet mean optimistic about the timeline.

A patient is partway through a routine therapeutic plasma exchange. The replacement fluid has been albumin the whole way through, as it usually is. But as the procedure nears its end, the last exchange volume gets switched to 2 units of FFP to "finish" the procedure. Nothing about the patient's clinical picture changed in that last liter. The switch happens because ending an exchange on plasma feels safer than ending it on albumin, even though nothing about the math supports that feeling. I've started calling this the plasma chaser, and I think it's worth being honest about what it actually is. It isn't a treatment. It's a ritual. And rituals, unlike treatments, don't have to work to persist. What the chaser is supposed to do If you ask someone why the last unit or two gets switched to plasma, you'll usually get one of two answers: either they're worried about the coagulopathy the exchange is causing, or they're worried about oncotic pressure and albumin. Both are reasonable things to worry about. Neither is what finishing on 2 units of FFP actually addresses. The tell is that the switch rarely comes with a stated target. It's not "switching to plasma for the last liter to correct a specific factor deficit." It's just a reflex, a way of not ending the procedure on a note that feels too far from whole blood. That vagueness is the first sign we're dealing with superstition rather than a plan. The math doesn't work Here's what a plasma exchange actually does to clotting factors: removal and replacement with a non-plasma fluid drops circulating factor levels substantially, often by 60% or more from baseline by the time the procedure is winding down. That depletion happens across the whole exchange. It doesn't reset just because the last bag is plasma. A single unit of FFP raises any given factor level by roughly 2-3%. Finishing with 2 units buys back maybe 5-10 percentage points of factor activity. Against a 60% deficit built up over the entire procedure, that leaves the patient down by roughly half from where they started, essentially unchanged by the switch. The last 2 units don't correct the depletion the exchange caused; they barely register against it. If the actual goal is meaningful coagulation correction, the literature is clear that weight-based dosing, 10-15 mL/kg, meaning 4 or more units for a normal-sized adult, is what correlates with real change. Finishing on 2 units is a gesture that looks like it's addressing the depletion and does almost nothing to it. The oncotic math doesn't work either If the real concern is albumin or oncotic pressure rather than coagulation, FFP is an especially poor tool for the job. Plasma albumin concentration is only about 3.5-5 g/dL to begin with, and 2 units is roughly 500 mL, a trivial volume against total plasma volume. If oncotic support is genuinely the goal, the replacement fluid already running, whatever concentration of albumin was chosen for the procedure, is the tool built for that purpose. Switching the last liter to FFP doesn't add meaningful oncotic support; it just changes what's in the bag for no measurable benefit. The exposure is real even when the benefit isn't This is the part that should bother us more than it does. Every unit of FFP is a separate donor exposure, and every donor exposure carries its own small but nonzero risk: allergic or anaphylactoid reaction, TRALI, TACO, alloimmunization. None of that risk scales down just because the switch happens at the end of a procedure that was otherwise entirely non-plasma. So the actual trade being made by finishing on 2 units is this: real, if modest, risk, in exchange for a physiologic effect too small to touch what the exchange depleted. That's not a conservative choice. It's the illusion of one. A framework that isn't ritual There is a version of this that makes sense, and it isn't complicated. Before choosing what to run for any portion of the exchange, decide what you're actually treating: If there's no clinically significant coagulopathy anticipated or observed, run albumin for the entire procedure, start to finish. There's no reason for the last liter to be different from the rest. If the factor depletion is genuinely severe enough to warrant correction, replace with plasma at a volume that actually moves the deficit, not a token switch at the end. If there's a real but moderate concern, a deliberate proportion of plasma throughout the exchange, scaled to the actual depletion, is defensible. Switching to 2 units only because the procedure is ending is not. Each of those has a rationale you could say out loud in front of the patient. "Finishing on plasma, just in case" does not. Decide, and commit The plasma chaser survives because it feels like doing something without requiring you to answer the actual question: is this exchange causing a clinically significant factor deficit, or not? That question has an answer before the procedure even starts, and it doesn't change because the bag count is running low. Once you know the answer, the replacement fluid follows from it, start to finish, and the ritual has nothing left to justify. So decide what your replacement fluid is for before the procedure begins; not as a hedge, not as a way to end things on the "safer-feeling" bag, but as a stated clinical judgment. Then commit to that choice for the whole exchange. If you can't say what you're correcting, you're not treating the patient. You're just crossing yourself and hoping.

A patient shows up needing blood. Her antibody screen comes back positive for something rare, something we can find antigen-negative units for, but not easily, and not fast. The question on the table isn't "is this antibody there." It clearly is. The question is: will it actually hurt her if we transfuse anyway? This is the part of transfusion medicine that doesn't make it into the textbooks as often as it should. We're very good at detecting alloantibodies. We are, frankly, less good at predicting what they'll do once red cells carrying the corresponding antigen show up in circulation. Some antibodies are clinically vicious. Others sit there, technically present, doing essentially nothing. Serology alone can't always tell you which kind you're dealing with. So instead of asking the antibody directly, we ask a different question: what will a monocyte do when it meets a red cell coated in this antibody? That's the monocyte monolayer assay, or MMA. What the assay actually does The setup is simpler than it sounds. You isolate monocytes from a normal donor and let them settle into a monolayer, a single sheet of cells, on a glass or plastic surface. You then take red cells sensitized with the patient's antibody (antigen-positive donor cells incubated with the patient's serum or plasma) and layer them on top. Then you wait, and you look. Monocytes have Fc receptors. If the antibody coating those red cells is one the monocyte's receptors recognize and respond to, the monocyte will do one of two things: engulf the red cell whole (phagocytosis) or grab onto it without fully swallowing it (adherence, sometimes called rosetting depending on the exact readout). Count how many red cells are being eaten or grabbed out of a set number of monocytes, and you get a percentage. That percentage is the assay's answer to the question serology couldn't fully address: is this antibody the kind that provokes extravascular destruction in vivo, or not. Higher phagocytic/adherence index, more concern for clinically significant hemolysis. Lower index, more reassurance that the antibody may be biologically quiet, at least as far as this in vitro proxy can tell you. Where it earns its keep The MMA isn't run casually. It shows up in specific, high-stakes scenarios: Deciding whether to transfuse antigen-positive units when antigen-negative units are scarce or unobtainable, particularly for high-prevalence antigens where "just find negative blood" isn't a real option Assessing antibodies of uncertain clinical significance, especially ones with a spotty or contradictory track record in the literature Supporting decisions in hemolytic disease of the fetus and newborn, where the stakes of both over- and under-intervention are considerable In all of these, the assay is functioning as a stand-in for a question we can't ethically or practically answer by simply transfusing and watching what happens. Where it stops being reassuring Here's the part I think about more than the mechanics. The MMA correlates reasonably well with clinical hemolysis for a number of antibody specificities, and that correlation is exactly why the assay gets used. But correlation built from case series and reference lab experience is not the same as a validated, universally reliable predictive test. Interlaboratory variability exists. Cutoffs for "significant" versus "not significant" differ by lab and by antibody specificity, sometimes for reasons of accumulated institutional experience rather than a single settled cutoff in the literature. And a normal donor's monocytes, doing their job in a dish, are still one step removed from what actually happens inside a specific patient's spleen, liver, and vasculature. So when a clinician calls asking whether the MMA result means it's "safe" to transfuse, the honest answer is more hedged than that word implies. A reassuring MMA lowers the estimated risk. It does not zero it out. We are still, in the end, making a probabilistic judgment call dressed up in a percentage. I don't think that's a flaw specific to this assay. It's the condition of most predictive testing in medicine: we build proxies because we can't ask the real question directly, and then we have to be honest with ourselves about how far the proxy actually gets us. The MMA gets transfusion medicine further than serology alone would. Whether it gets us far enough, in any individual case, is a judgment call every time. I'm not sure there's a version of this test, or maybe any test, that removes that part of the job.

In 1961, a blood bank in Melbourne ran a routine antenatal work up on an Aboriginal Australian woman and got a result that didn't make sense. Her red cells reacted with nothing. Not the anti-D, not the anti-C, not the anti-E; every reagent in the Rh panel came back negative, as though the entire Rh system had simply been left out of her blood. It had. She was the first documented case of Rh-null, the phenotype that would later earn the nickname "golden blood." Sixty-some years and fewer than 50 confirmed cases later, it still functions less like a blood type and more like a members-only club with brutal admission requirements and no way to quit. What Rh-null actually is The Rh system isn't the single antigen most people think of when they hear "Rh positive" or "Rh negative." It's a family of more than 50 antigens sitting on a protein complex that helps hold the red cell membrane together. Ordinary Rh-negative means you lack one antigen, D. Rh-null means you lack all of them: D, C, E, c, e, and the rest. It's a genetic accident, usually a mutation in the RHAG gene, inherited recessively, which is part of why it clusters in some families and shows up as a total surprise in others. Because Rh-null cells carry none of the antigens that trigger most transfusion reactions, they can go into almost anyone with a rare or complex Rh phenotype without incident. That's the "golden" part. The catch, and it's a serious one, is that the Rh protein complex isn't just a target for antibodies; it's structural. Losing it destabilizes the red cell membrane, and Rh-null patients often live with a mild chronic hemolytic anemia as a result. They need blood more than most people, and they can safely receive it from almost no one. Why you can't just stockpile it Standard red cell storage is liquid, refrigerated, and good for about 42 days. That timeline works fine when a population of donors is large enough to keep replenishing the shelf. It does not work for a phenotype with fewer than 50 known carriers worldwide and perhaps nine of them actively donating at any given time. So Rh-null units get frozen instead, glycerolized and held at specialized reference laboratories, extending shelf life to a decade or more at the cost of a labor-intensive thaw-and-deglycerolize process before the unit can actually be transfused. It's less a blood bank than a bank in the literal sense: assets held in reserve against a future you're trying not to think about too hard. The network for rare blood The infrastructure holding this together predates most of us. The International Rare Donor Panel has run out of the International Blood Group Reference Laboratory in Bristol since 1965, a joint effort of the World Health Organization and the International Society of Blood Transfusion, tracking rare-phenotype donors and frozen inventories across roughly 27 countries. The United States has its own parallel structure in the American Rare Donor Program. When a patient needs a unit, their clinical team doesn't call the regional blood supplier; they activate this network, which might mean locating a frozen unit at a reference laboratory on another continent, or it might mean someone, somewhere, picking up the phone to ask a known Rh-null donor if they're willing and able to give again. I want to sit with that for a second, because it's easy to read past it. There is no supply chain here in the ordinary sense. There is a short list of names. What it asks of the people on the list If you are one of those names, the practical advice you receive amounts to: take care of yourself, because there may be no one who can take care of you. Rh-null individuals are often counseled to bank their own blood autologously well in advance of any anticipated need, since waiting on the international network in a genuine emergency is a bad plan with worse alternatives. They're advised to carry medical identification, to stay in active contact with their local blood bank and the rare donor registries, and to think carefully before traveling somewhere without ready access to frozen rare stock or fast courier logistics. Elective surgery gets planned around blood availability, not the other way around. Pregnancy carries its own specific version of this calculus. None of this is unique to Rh-null; other rare phenotypes carry similar constraints. But the numbers here are small enough that the constraint stops being statistical and becomes personal. When there are nine active donors on the planet, every one of them matters in a way that's hard to fully translate into the language of population health. They are, functionally, on call for each other. Not through any formal duty, but because the alternative is a system with gaps that no one else can fill. What we owe the irreplaceable I keep circling back to the same question and not landing anywhere satisfying. We ask an enormous amount of people who happen to carry a phenotype the rest of us will never need to think about, and mostly what we offer them in return is gratitude and a spot in a database. Is that enough? I'm not sure "enough" is even the right frame when the thing being asked for can't be manufactured, purchased, or replaced. But it feels worth naming, at minimum, that the golden blood donor community isn't a supply. It's a small group of people who agreed, implicitly, to be each other's only option.

In the past two weeks I've published two blogs about stories that arose around blood type: the one piece of biology we all happen to know about ourselves. This got me thinking about why humans love stories so much, and led to this post. During the V-1 bombing campaign of 1944, Londoners became convinced the Germans were sparing certain neighborhoods. The bombs seemed to cluster, hitting some districts again and again while leaving others conspicuously untouched. The explanation people arrived at was that German sympathizers lived in the spared areas, feeding targeting information back across the Channel. Wealthy neighborhoods, poor neighborhoods, everyone had a theory about who was being protected and why. An actuary named R. D. Clarke ran the numbers. He divided south London into a grid of quarter-square-kilometer cells and counted how many bombs landed in each. If the strikes really were clustering, non-random, guided by something, the distribution should have looked lumpy: some cells hit repeatedly, others suspiciously empty. What he found instead was a close match to a Poisson distribution, the statistical signature of pure chance events scattered randomly across a fixed area. No clustering. No sparing. The bombs were falling exactly where randomness alone would put them, and the human brains living underneath that randomness were doing something brains cannot apparently help but do: finding a story in it anyway. That's the whole essay in miniature. Here's the slower version. The brain you have is a prediction engine, not a camera It's tempting to think of the brain as something like a recording device, taking in the world and producing an accurate internal copy of it. That's not what's happening. Your retina, skin, and cochlea are together delivering something on the order of eleven million bits of sensory information per second. Conscious awareness processes somewhere around forty to fifty. The gap between those two numbers isn't a rounding error; it's nearly the entire signal. Almost everything reaching your senses gets thrown away before you're ever aware of it. What survives isn't a copy of the world. It's a prediction, generated by an internal model that gets updated only when incoming data disagrees with it strongly enough to be worth correction. Consider your blind spot: there's a patch on each retina with no photoreceptors at all, roughly the width of your fist at arm's length, and you have never once seen a hole there, because the visual cortex fills the gap with a prediction drawn from the surrounding pattern rather than showing you nothing. Or consider phonemic restoration: erase a single sound from a recorded word, replace it with a burst of noise, and play it back. Listeners report hearing the missing sound clearly, correctly, with no sense that anything was ever removed. In both cases the brain isn't a passive receiver waiting for complete information. It's actively manufacturing the missing piece and presenting the manufactured version to you as though it were simply what's there. Researchers working in predictive processing, Karl Friston, Andy Clark, and Jakob Hohwy among the most influential, have spent the last couple of decades formalizing this: perception is mostly inference, corrected only at the margins by the world. The reason for this architecture is not mysterious. A brain that waited to react until it had fully perceived a threat would be a brain that reacted too late. Prediction is faster than perception. So evolution built brains that guess first and check the guess against reality only as needed, because the guessing is what keeps the animal alive long enough to guess again. Pattern-detection with no off switch Here's where it gets interesting. The machinery built to predict predators, weather, and the location of food doesn't come with a governor that shuts it off once survival needs are met. It's a general-purpose pattern detector, tuned by evolution for a specific set of adaptive problems, but with no way of distinguishing “a pattern that matters for staying alive” from “a pattern,” full stop. Once you have a system that scans constantly for structure and rewards you, neurochemically, for finding it, that system does not stay confined to its original job description. It runs on everything you point it at, including things with zero survival stakes. You can watch this same circuitry misfire on something with nothing at stake at all. Sit at a roulette table and watch black come up five times running, and something in you will insist red is “due.” The wheel has no memory. Each spin is independent of the last, governed by exactly the kind of process that produces Poisson-style clumping over the long run, the same statistical signature Clarke found in his bomb data. But a brain built to assume that streaks mean something, a predator is near, a food source is reliable, does not easily accept that five blacks in a row are simply what randomness looks like some of the time. A pattern-hungry brain looks at a clump, at a card table or anywhere else, and assigns it a cause, because assigning causes is the job, and the job doesn't come with a built-in check for whether a cause is actually there. Run that same overshoot through a slightly different circuit, one built for modeling other minds rather than physical events, and you get agency-detection: the reflex to assume a “who” behind an occurrence rather than a “what.” It's a useful reflex when the rustle in the grass really is a predator. It's a much less useful reflex when it's applied to a losing streak at a card table, a rustle that's just wind, or a universe that doesn't owe you a reason. But the circuit fires the same way regardless, because the circuit was never built to check whether firing was warranted. It was built to fire fast. What happens when the machinery overshoots Most of the time this overshoot is just noise, a superstition here, a false pattern there. But four of the more notable things humans do look a lot like this same machinery, run deliberately and at scale, on inputs where the stakes were never survival to begin with. Art is expectation, set up and then either satisfied or productively violated. A melody creates a prediction about the next note; the pleasure of hearing it resolve, or the deeper pleasure of hearing it almost resolve and then swerve, is the prediction engine registering its own model being tested. This is true even of art that refuses to resolve at all. A plotless novel, an atonal piece of music, a painting with no clear focal point, these aren't failures of pattern-making. They're a different kind of pattern, one where the recognizable shape is the absence of a shape, and the brain does the same sense-making work either way. It just makes the unresolved feeling the point. Comedy runs on the same clock, just tuned differently. A setup builds a prediction about where a sentence, or a situation, is headed. A punchline breaks that prediction and replaces it with a second interpretation that also, on half a second's reflection, makes sense of everything that came before. The laugh is what a violated-but-resolved prediction feels like from the inside, which is why the same joke told too slowly falls flat: the first model gets too much time to settle in, and the swerve reads as merely wrong rather than delightfully wrong, and why a joke told too fast doesn't land either, since there was never enough of a prediction built to violate in the first place. Timing isn't an aesthetic flourish sitting on top of comedy. Timing is the mechanism, precisely dosed. Conspiracy theories are the same causal hunger, unsupervised. This is, in miniature, exactly what happened over London: a real pattern of scattered, random events, and a population of brains reflexively assigning it a hidden intentional cause rather than accepting chance. Conspiracy theories run on that same logic at any scale, a cluster of events that feels too coordinated to be accidental, an agent posited to explain the coordination, a community that reinforces the pattern by trading confirming details back and forth until the story feels load-bearing. Agency-detection, the reflex to assume a “who” behind an occurrence, does a lot of the work here, and it costs the system almost nothing to overuse: assuming agency where there is none is cheap, while failing to notice agency where it actually exists can be fatal, so evolution built us to err generously toward “someone did this.” The reasoning isn't stupid. It's the ordinary causal-inference machinery, running exactly as designed, with no external check on whether the inferred cause is real. There's no separate gullible circuit sitting apart from the sensible one. There's one circuit, and it doesn't come pre-labeled with which of its outputs to trust. Science is the same hunting instinct, except with a leash on it. A hypothesis is a prediction like any other, generated by the same overactive pattern-finder that saw spies in a bombing grid. What makes science different isn't that scientists have quieter versions of this instinct. It's that the discipline built an external check the brain doesn't supply on its own: test the prediction against reality, and be willing to let reality win. Clarke's own paper is an act of this discipline turned back on the very phenomenon that produced it, using statistics to catch the brain in the act of pattern-hunting and correct it. Science is, in that sense, the prediction engine's most successful attempt to police itself. The part that doesn't resolve Here's the uncomfortable symmetry. The same system that produces a Beethoven symphony produces a conspiracy theory. The same system that let Clarke catch the brain in the act of pattern-hunting was doing the pattern-hunting in the first place. A cluster appears, therefore something must be causing the cluster, therefore let's find out what, or who. Sometimes that search turns up something real: a virus's mode of transmission, the actual cause of a bridge collapse, a genuine regularity in orbital motion. Sometimes it turns up a spy network that was never there. Most of the time, this machinery has no internal way of telling you in advance which search you're running. I don't think there's a tidy place to land on this. The pattern-detection that makes you capable of art, of asking unanswerable questions, of doing science at all, is the exact same machinery that will hand you a false spy network with total conviction if you don't build something external to check it against. We didn't get the beautiful, meaning-saturated version of human cognition and the paranoid, error-prone version as two separate features. We got one system, running exactly as designed, and it was never going to be able to tell the two apart on its own.

In Japan, it is entirely normal to be asked your blood type on a first date. Dating profiles list it next to height and occupation. Some employers have, at various points, sorted job candidates by it, on the theory that Type O makes a better leader and Type A makes a better accountant. There is a specific term for this: ketsuekigata, blood type personality theory. It has no biological mechanism, no supporting evidence at scale, and roughly fifty years of cultural staying power [1]. Where it started The theory traces to 1927, when Japanese psychologist Takeji Furukawa published a paper linking ABO type to temperament, describing Type A individuals as gentle and anxious, Type B as cheerful and self-centered, and so on [2,3]. Furukawa's data were thin, and his own academic community pushed back at the time [3]. The theory should have died there. It got a second wind in 1971, when journalist Masahiko Nomi, who had no medical or psychological training, published a book reviving and expanding it, adding claims that blood type predicted not just personality but disease susceptibility [1,3]. Nomi's work drew the same methodological criticism Furukawa's had. It didn't matter. By the 1980s, blood type personality theory was a fixture of Japanese popular culture, and it has stayed one since, with related belief systems taking hold in South Korea and Taiwan [4]. What the evidence shows Unlike the blood type diet, this one doesn't even offer a mechanism worth debunking. Nobody claims to know how an antigen expressed on the surface of a red blood cell would shape whether you're anxious or gregarious. There's no lectin story here, no agglutination metaphor. It's association without a proposed pathway, which makes it a cleaner test case for pattern-seeking on its own terms. And the pattern isn't there. Large-scale surveys using validated personality instruments, run in both Japan and the United States, have found no meaningful correlation between ABO type and standard personality traits [1]. This isn't a case of a single small study failing to find an effect. It's the specific finding, repeated across populations that supposedly believe in the theory most strongly, that belief and reality have parted ways. Why it took hold where it did The interesting question isn't whether ketsuekigata is true. It's why a country with excellent scientific infrastructure and health literacy adopted a folk taxonomy this thoroughly, while most of the world shrugged. Part of the answer is historical: Furukawa's early work was entangled with period ideas about national and ethnic character, giving the theory an early institutional foothold it didn't earn on data [3]. Part of it is more mundane. Once a categorization system is culturally legible, media reinforces it, and confirmation bias does the rest. If you're told Type B people are unpredictable, you notice the unpredictable things your Type B friend does and forget the rest. The Barnum effect, the same mechanism that makes horoscopes feel accurate, doesn't need a real correlation to feel like one. The diet's cousin If you read last week's post on the blood type diet, you'll notice the throughline: ABO type is one of the only pieces of biology most people can name about themselves, and that legibility makes it an appealing anchor for a story, regardless of whether the story holds up. The diet claims a mechanism and fails on evidence. The personality theory doesn't even bother with a mechanism, and fails just as completely. Both persist anyway. Maybe that's the actual finding here: mechanism was never the load-bearing part of either belief. The load-bearing part is wanting a story. References 1. Nawata K. No relationship between blood type and personality: evidence from large-scale surveys in Japan and the US. Jpn Psychol Res. 2014;56(2):163-173. 2. Furukawa T. A study of temperament and blood-groups. Psychol Res. 1927;2:612-634. 3. Cha J. Blood type and personality. Hektoen International. 2020. 4. Relationship between ABO blood type and personality in a large-scale survey. Int J Psychol Behav Sci. 2021;11(1).

A friend at a dinner party once turned down the bread basket because she was "type A, and grains don't agree with her blood." I nodded, passed the butter, and spent the rest of the meal thinking about lectins instead of listening to the conversation. Occupational hazard. The blood type diet has been around since 1996, when naturopath Peter D'Adamo published Eat Right 4 Your Type [1]. Its premise: your ABO blood type reflects your ancestors' diet, so eating in accordance with your type optimizes digestion and health. Type O, the "hunter," should eat like a caveman: high protein, minimal grains. Type A, the "agrarian," should go largely vegetarian. Type B gets dairy. Type AB gets a little of everything, marketed as the "enigma" for reasons that say more about branding than biology. The mechanism, as advertised The theory rests on lectins: proteins found throughout the plant kingdom, concentrated in legumes and grains, that bind to carbohydrate molecules. D'Adamo's claim is that dietary lectins interact with the antigens on your red blood cells the way incompatible blood interacts in a transfusion reaction, causing agglutination, clumping, and a cascade of downstream health problems specific to your type [2]. If you work in transfusion medicine, you already know where this goes wrong. What agglutination actually requires Agglutination in a clinically meaningful sense requires antibody binding to a compatible antigen, at a concentration and in an environment that supports crosslinking. It is not a generic hazard that any given protein produces on contact with blood. The lectin literature bears this out: a systematic review of blood type diet claims found no controlled evidence that dietary lectins clump blood cells inside the body in a type-specific way [3]. Most food lectins denature with cooking. Of the ones that survive digestion intact, the review found the overwhelming majority react with all ABO types indiscriminately, not selectively with one [3]. There is a small, real exception: raw legumes contain lectins with some blood-type-preferential agglutinating activity in vitro [4]. But "some lectin behaves selectively in a test tube" is a long way from "your dinner is attacking your blood type." What the trials actually show A few groups have tested the diet's health claims directly rather than the mechanism. The most-cited systematic review, Cusack et al. in the American Journal of Clinical Nutrition, found that while several of the individual "type" diets were associated with favorable changes in metabolic risk markers, the effect held regardless of the subject's actual blood type [3]. In other words: the Type O diet made people healthier whether or not they were Type O. The diets are, structurally, healthier eating patterns. Less processed food, more vegetables, controlled portions. People who follow any of them tend to do better than people who don't, and the ABO matching adds nothing measurable on top of that [3]. A separate analysis, Wang et al. in PLoS ONE, looked directly at ABO genotype against the diet's proposed cardiometabolic outcomes and found no interaction: type didn't predict which diet worked better for whom [5]. Why it persists anyway None of this has hurt sales. The obvious answer is that personalization sells better than generic advice, and blood type is one of the few pieces of biology most people can actually name about themselves. "Eat less processed food" is true and unsatisfying. "Eat less processed food because you are Type A" is a story, and stories are what people remember at dinner parties. There's a less cynical read too. We want our biology to explain us: why we feel good after some meals and sluggish after others, why one relative thrives on a diet that wrecks another. ABO type is legible in a way gut microbiome composition or polygenic metabolic risk isn't. It's one letter, drawn on a card in your wallet, and it feels like it should mean more than it does. It doesn't. Eat the vegetables. Skip the antigen mapping. References 1. D'Adamo P, Whitney C. Eat Right 4 Your Type. G.P. Putnam's Sons; 1996. 2. Nachbar MS, Oppenheim JD. Lectins in the United States diet: a survey of lectins in commonly consumed foods and a review of the literature. Am J Clin Nutr. 1980;33(11):2338-2345. 3. Cusack L, De Buck E, Compernolle V, Vandekerckhove P. Blood type diets lack supporting evidence: a systematic review. Am J Clin Nutr. 2013;98(1):99-104. 4. Sharon N, Lis H. History of lectins: from hemagglutinins to biological recognition molecules. Glycobiology. 2004;14(11):53R-62R. 5. Wang J, García-Bailo B, Nielsen DE, El-Sohemy A. ABO genotype, 'blood-type' diet and cardiometabolic risk factors. PLoS ONE. 2014;9(1):e84749.

The patient is a composite, built from enough cases to be nobody in particular: an elderly man admitted with a colonic obstruction, febrile, blood cultures eventually growing a gram-negative rod. His chart says A positive. It has said A positive for decades, through two prior admissions and one prior transfusion. The type-and-screen that comes back this time says otherwise. The forward type shows both A and a weak but unmistakable B reactivity. The reverse type, his own serum against reagent cells, still shows anti-B, exactly as it should for a lifelong group A patient. Forward and reverse disagree. Someone on the bench who has seen this before doesn't reach for a rare subgroup workup. They reach for the chart, note the fever and the bowel pathology, and write "acquired B" before the second tube has finished spinning. He is still, genetically, group A. Nothing about his ABO gene has changed. What's changed is what a bacterial enzyme has done to the surface of his red cells, and that distinction, between what your genes say and what your cells are currently showing, is the whole subject of this post. Genotype and phenotype, briefly Your ABO genotype is fixed at conception: the specific alleles you inherited, encoding glycosyltransferase enzymes that add either N-acetylgalactosamine (making A antigen) or galactose (making B antigen) onto a common precursor structure on the red cell surface. Your ABO phenotype is what a lab actually detects: the antigens expressed on your cells, tested by forward typing, and the antibodies circulating in your plasma against the antigens you lack, tested by reverse typing. In the overwhelming majority of people, genotype and phenotype agree completely, which is why we treat "blood type" as a fixed, inherited fact roughly on par with eye color. Most of the time it is. It's just not guaranteed to be, and the exceptions are where transfusion medicine gets interesting. How the mismatch happens Acquired B is the cleanest example because the mechanism is fully worked out. Certain gram-negative bacteria, often colonic flora that have gained access through a compromised gut wall from a tumor, obstruction, or infection, carry a deacetylase enzyme. That enzyme strips the acetyl group off the terminal sugar of the A antigen, N-acetylgalactosamine, converting it to galactosamine [1,2]. Galactosamine happens to be structurally close enough to galactose, the terminal sugar that defines the B antigen, that commercial anti-B reagent cross-reacts with it [1]. The cell hasn't started making B antigen. It's wearing a chemically modified version of its own A antigen that a reagent mistakes for B. Pull the source of bacterial exposure, whether by treating the sepsis or resecting the tumor, and the discrepancy resolves on its own, typically within weeks [3]. Genotype never moved. Phenotype took a temporary detour. Post-transplant chimerism works differently but lands in the same place. A patient who receives an ABO-mismatched hematopoietic stem cell transplant will, over the course of engraftment, gradually stop typing as their native blood type and start typing as their donor's. Eventually the genotype itself has changed, at least in the hematopoietic compartment: the red cells being produced are now genetically the donor's. This one isn't a transient artifact to be explained away. It's a real, durable shift, and it means "blood type" for a post-transplant patient has to be tracked as a moving target rather than looked up once and filed away [4]. A third category lives entirely on the genotype side: weak ABO subgroups, where an inherited variant allele produces a glycosyltransferase with reduced enzymatic activity. The antigen is present, just sparse enough that forward typing looks weak, ambiguous, or occasionally falls out as an apparent O in a person who is not, in fact, group O. No bacteria involved, no transplant involved. Just an inherited enzyme that's technically functional and practically underpowered. Why it matters beyond the interesting case report Every one of these scenarios is a reminder that "check the type" and "trust the historical type" are not the same instruction, and blood banks build entire policies around knowing when to prefer one over the other. A patient with a documented history of acquired B doesn't need a lifelong flag reclassifying their type; they need the discrepancy recognized as transient and resolved on the next clean sample. A post-transplant patient needs active tracking through engraftment, because giving blood matched to their pre-transplant genotype can become the wrong call partway through their course. A weak subgroup needs to be distinguished from acquired B and from genuine group O, because the transfusion consequences of getting that wrong are not symmetric. None of this is exotic. It's the ordinary, unglamorous discipline of not assuming a chart from three years ago is still telling you the truth. Where sequencing fits Serology answers what the cells are doing right now. It doesn't always answer why, and in ambiguous cases, that gap matters. Genotyping resolves the categories serology can't cleanly separate: distinguishing a weak subgroup from an acquired phenomenon from early mixed-field chimerism, in a single pass, without waiting for an infection to clear or a repeat sample to confirm a trend. That's the appeal of ABO genotyping as a clinical tool, and it's the part of this space I've been spending the most time in lately. More on that as the work develops. The identity question People treat blood type the way they treat a birthday: fixed, inherited, a fact about you that predates memory. Mostly that's fair. But "mostly" is doing real work in that sentence. Somewhere in a transfusion service right now, a phenotype is quietly disagreeing with a genotype, and the discrepancy is not a lab error to be explained away so much as a reminder that even the facts we consider most fixed about our own biology are, on some timescale, conditional. References 1. Blood Bank Guy Glossary. Acquired B Antigen. bbguy.org. 2. Judd WJ, Friedman BA. The acquired B antigen phenomenon. ASCP Check Sample Program, Immunohematology No. 1-82; 1975. 3. Campbell TA et al. Acquired B antigen: an ABO typing discrepancy successfully reversed by transfusion with type A red blood cells. Transfusion. 1980;20(3):345-348. 4. Resolution of an unexpected ABO typing discrepancy in a 9-month-old patient with juvenile myelomonocytic leukemia. Clin Case Rep. 2020.

Families who request directed donation from an “unvaccinated” donor believe they are choosing the safer option. The literature says the opposite. Directed donations, particularly from first time donors recruited specifically for the occasion, carry higher rates of infectious disease marker reactivity than units from repeat community donors. The donor pool people trust the most, because they know the person, is measurably less safe than the anonymous pool they're trying to avoid. That paradox sat quietly in the guidelines for years, cited in position statements and discouraged in policy language, without much data on what actually happens when a request like this proceeds anyway. A two year single center series out of Vanderbilt, published this year in Transfusion, gives us that data. It's worth sitting with. What They Found Between January 2024 and December 2025, the VUMC blood bank received 144,856 total blood product units. Of those, 48, or 0.03 percent, were directed donor units collected specifically because a patient or family refused standard inventory over concerns about vaccinated donors. Every single directed donation in the study period, with no exceptions for rare blood types or other medically recognized indications, was motivated by this concern. Those 48 units covered 15 patients. Median age was 17, ranging from 4 months to 73 years, and 60 percent were pediatric. The requests weren't rare and holding steady either. They climbed from 4 patients in 2024 to 11 in 2025. Thirteen of the 15 patients were transfused at least one directed unit. And 7 of the 15, nearly half, had at least one unit collected on their behalf that was never actually transfused to them. Those units didn't vanish. Most were released back into general inventory. Someone drew blood from a specific person, for a specific patient, under a specific belief about safety, and then that blood went to a stranger anyway. That's not a rare edge case in this series. It's closer to the norm. Where the System Broke Here is the finding that matters most to me as a transfusion medicine physician: of the 15 cases, only 1 had a documented ethics consultation. Only 1 had transfusion medicine notified before the directed unit arrived at the blood bank, and even that notification came after the perioperative service had already approved the request going forward. This isn't a story about families making an uninformed choice in a vacuum. It's a story about a workflow. Requests here were routed directly from a family or a primary clinical team to an external blood donor center's online form, entirely outside the consultation structure that exists precisely to handle requests this ethically and medically complicated. By the time anyone with transfusion medicine expertise heard about it, the decision had usually already been made. It didn't have to go this way. Mayo Clinic's Bloodless Medicine and Surgery Program uses structured shared decision making for exactly this kind of request, and most families end up accepting standard blood products through that process. Mayo has since restricted directed donation absent a genuine medical indication. Seattle Children's Hospital built a similar structured consultation model, pairing transfusion medicine with ethics, for pediatric cardiac surgery cases with vaccine related concerns, and it worked there too. The difference between those institutions and this series isn't the families. It's whether anyone with the right expertise was in the room before the blood was drawn. Harm in Both Directions The clinical consequences in this series are not abstract. One patient's hemoglobin fell to 5.9 g/dL with symptomatic anemia while transfusion was delayed awaiting arrival of directed units. That same patient later received a transfusion at a hemoglobin of 9.2, a clear deviation from institutional guidelines, because the clinical team didn't want the directed unit to go to waste after all that effort to obtain it. Sit with that sequence for a second. A patient was harmed by the delay. Then a guideline appropriate threshold was overridden to avoid wasting a unit that should never have been the deciding factor in the first place. The instinct to avoid waste, once the unit exists, quietly overrides the standard of care that exists to protect the patient. A second patient developed hemodynamic shock with a hemoglobin nadir of 3.6 while awaiting directed blood. Two additional patients had surgery delayed or cancelled entirely because of directed component logistics. Four of fifteen patients, more than a quarter of this small cohort, experienced a documented adverse clinical or operational event tied directly to this workflow. Outcome Patients Received at least one directed unit 15 Transfused at least one directed unit 13 (87%) Had at least one unit collected but never transfused to them 7 (47%) Clinical deterioration while awaiting directed units 2 (13%) Transfusion deviating from institutional guidelines 1 (7%) Surgical delay or cancellation 2 (13%) Ethics consultation documented 1 (7%) Transfusion medicine notified before unit arrival 1 (7%) The Weight Falls on Children Nine of the fifteen patients in this series were minors. Among pediatric patients, surrogate decision making applied in 100 percent of cases, compared to 17 percent of adult cases. These are children absorbing the downstream consequences, clinical and logistical, of a belief about vaccination status that they had no part in forming and no ability to consent around. The ethical weight of that imbalance is hard to overstate, and it's the piece of this paper I keep returning to. A Familiar Failure Mode I've written before about laboratory medicine as a kind of governance layer, the expert checkpoint that's supposed to sit between a high stakes request and its execution, whether that request involves an unvalidated algorithm or a unit of blood. This series is that same failure mode wearing a different face. An ethically loaded, medically consequential request bypassed the expert consultation layer almost entirely, not because the layer didn't exist, but because the workflow routed around it. Governance failures rarely look like a single bad decision. They look like a form that lets you skip the conversation. Where This Leaves Us The authors propose a fix that sounds almost too simple: mandatory transfusion medicine consultation for every directed donation request, before collection proceeds, replacing what is currently an optional and easily bypassed step. Mayo and Seattle Children's suggest that when this consultation happens, most families accept standard products anyway. That's an encouraging signal, but it doesn't fully resolve the harder tension underneath this paper, the one between respecting a family's autonomy to make decisions about their own care and preventing exactly the kind of harm this series documents. A mandatory consult can close the routing gap. It can't, by itself, tell us how to balance those two obligations when a family still says no after hearing everything transfusion medicine has to say.

I knew Wisconsin had hard water before we moved here — everyone warns you about the white crust that builds up on faucets, the way soap won't quite lather right, the kettle that needs descaling every few weeks whether you want to deal with it or not. What I didn't expect was how much I'd find myself thinking about it on a quiet Saturday afternoon, half-bored, half-curious, turning over a question I hadn't really asked before: does any of this actually do anything to me? Hard water, by definition, is just water carrying more dissolved calcium and magnesium than usual — picked up as it filters through limestone and rock on its way to your tap. And calcium is, of course, the mineral I spend a fair amount of my professional life thinking about, just usually in the context of a patient's blood draw rather than my own kitchen sink. So the question followed naturally: if I'm drinking measurably more calcium every day than I was in my old soft-water house, is more of it ending up in my blood? The Body Doesn't Work That Way The honest, slightly anticlimactic answer is no — and the reason is one of the more elegant pieces of human physiology. Serum calcium isn't a passive reflection of however much calcium you happen to eat or drink on a given day. It's tightly, almost stubbornly regulated by a feedback loop involving parathyroid hormone, vitamin D, and the kidneys, all working continuously to hold your blood calcium inside a narrow range regardless of what's coming in from your diet. Drink more, and your body simply absorbs and excretes accordingly, defending the same set point it always defends. This isn't just theoretical. A Swedish study comparing people living in hard-water and soft-water regions looked directly for a correlation between calcium and magnesium levels in drinking water and the corresponding levels in serum — and found none. The water mineral content moved. The blood mineral content didn't follow. Homeostasis, doing exactly what it's supposed to do. But "no change in serum calcium" doesn't mean nothing happens at all — it just means the action shifts somewhere else. A small trial gave healthy young men a single glass of calcium-rich mineral water and tracked their bloodwork over the next few hours. Serum calcium, predictably, barely budged. But parathyroid hormone dropped significantly, and a marker of bone resorption fell right along with it. The body didn't need to raise blood calcium because it had just gotten a supply from the gut — so it dialed back how much it was pulling out of bone to maintain the same number. One glass of water, one afternoon, and you can already see the lever moving. So if hard water isn't raising anyone's blood calcium, the question becomes: does it matter for anything else? Where the Real Signal Shows Up It turns out the more interesting story isn't in serum calcium at all — it's in bone, and specifically in fracture risk, measured over years rather than in a single blood draw. A 2026 ecological study out of England found that neighborhoods with harder water had meaningfully fewer hospitalizations for childhood fractures than neighborhoods with soft water, even after accounting for the usual sociodemographic confounders. Norwegian researchers, looking at hip fractures in older adults, found a related pattern: lower calcium and magnesium in municipal water tracked with lower bone mass density and higher fracture incidence. That's a real, if quiet, signal — and it makes some biological sense. If chronic, low-grade mineral intake nudges PTH down just slightly over years and decades, the downstream effect is less ongoing resorption from bone to maintain serum levels. Nobody's blood calcium moves. The skeleton just quietly gets to keep slightly more of what it already has. But It's Never Just Calcium Here's where the story gets messier, in the way real epidemiology usually does. Hard water isn't a single-ingredient exposure — it's calcium and magnesium, almost always together, in ratios that vary by region and geology. The same Norwegian research group that found the calcium-fracture association also found that it depended heavily on what else was in the water; once they accounted for other minerals, the calcium signal alone wasn't clean or independent. You can't pull calcium out of "hard water" and credit it alone for what the studies are finding. Whatever benefit exists is probably shared, tangled, and not easily assigned to one element over the other. Which raises a natural next question: if it's not clearly calcium doing the work, what happens when you study calcium supplementation directly? The Calcium Supplementation Letdown Not much, as it turns out — at least not in the way most people assume. Systematic reviews of calcium supplementation in adults have found, at best, modest gains in bone mineral density: low single-digit percentage improvements at the hip, spine, and forearm, even at fairly substantial daily doses. One major review concluded there was no clear evidence that increasing dietary calcium intake actually lowers fracture risk at all. The mineral that seemed like the obvious hero of bone health, taken as a standalone pill in adulthood, just doesn't move the needle the way the supplement aisle would have you believe. That's a genuinely useful correction to a very widespread assumption — but it also means the hard-water fracture data probably isn't a calcium story either. Magnesium's More Promising, Less Finished Story So I went looking at magnesium on its own, and found a more encouraging — if still unfinished — picture. A 2021 systematic review found that higher magnesium intake was associated with increased bone mineral density specifically at the hip and femoral neck. Small clinical trials back up a plausible mechanism: magnesium supplementation in postmenopausal women has been shown to lower parathyroid hormone, raise markers of bone formation, and lower markers of bone resorption — the same hormonal lever that chronic mineral exposure from water seems to be quietly pulling. What's missing is the big, definitive trial: a large, long-term, fracture-outcome study in older adults that could say, with real confidence, "magnesium supplementation prevents fractures." That trial doesn't exist yet. What exists is a coherent mechanism and some encouraging early biomarker data — promising, but not proven. Two Different Stories, One Word So "hard water" turns out to be two separate stories wearing the same name. The calcium half looks like it matters most early — in childhood and adolescence, when bone is actively being built and every bit of mineral exposure has more to work with. That window is the one with the clearest evidence, and it's also the one I've already missed; I moved to Wisconsin at 41 and a half, well past peak bone accrual, with whatever skeleton I'd already built. The magnesium half tells a different, more open-ended story — one that may still have something to offer people my age and older, as the supplementation evidence slowly matures. I won't get the childhood benefit of this water. I might still get something from what's dissolved in it now, if the early signals hold up. Mostly, though, what stays with me is the bigger and slightly strange realization underneath all of it: something as ordinary as where you happen to live — the geology under your house, the minerals leaching into your tap water — has been quietly shaping human skeletons for as long as people have been drinking from the ground. I only thought to ask about it because I moved somewhere new and noticed the kettle scale. Most people never think to ask at all.