Medical supply chains in the field: blood products and cold chain

A packed red blood cell unit collected at a blood establishment travels a chain of cold storage, transport containers, forward handoffs, and bedside issue before it reaches a casualty in a Role 2 surgical facility. Every link in that chain is a potential failure point – a door left open too long, a generator that ran out of fuel, a transfer that was never recorded. When the chain breaks, the blood product may be unusable. When the break goes undetected, the consequence is a transfused unit that should have been discarded. Military medical supply chains for blood products represent the highest-stakes version of the cold chain logistics problem: margin for error is measured in minutes and millilitres, not percentages or cost variances. This article examines how purpose-built cold chain management software addresses temperature tracking, expiry control, inventory management, and resupply across the Role 1 to Role 3 echelon structure.

The blood product cold chain: what makes it distinct from general supply

Blood products are unlike any other military supply category. They are perishable on timescales of hours to weeks. They are biologically complex – the same product type (packed red blood cells, fresh frozen plasma, platelets, whole blood) can have meaningfully different efficacy depending on storage duration and temperature history. They require specific storage conditions that differ by product: red cells at 1°C–6°C, platelets at 20°C–24°C with constant gentle agitation, fresh frozen plasma at or below -18°C. And they carry a direct chain-of-custody requirement – every unit must be traceable from donor to final disposition (transfused, returned, or destroyed) for haemovigilance and adverse event investigation.

These constraints combine to create a logistics problem that standard military supply chain software cannot solve. A general-purpose asset tracking system records that a pallet moved from a depot to a forward staging area. It does not record that the refrigerated container carrying blood products was at 8.2°C for 47 minutes during loading – a fact that would require a medical officer to assess whether the products are still safe to transfuse. A purpose-built blood management system maintains a continuous, auditable temperature record alongside the custody and inventory records, and it surfaces temperature excursions in real time so they can be acted upon before a compromised unit reaches a patient.

Product categories and their storage requirements

The four primary blood product categories in military field use each impose distinct cold chain requirements that must be enforced separately:

Packed red blood cells (pRBC) require storage at 1°C–6°C in an approved blood refrigerator. Shelf life is 35–42 days from donation depending on the anticoagulant-preservative solution used (CPD-SAGM extends to 42 days). The maximum acceptable storage temperature is 6°C; temperatures above this accelerate haemolysis and reduce post-transfusion red cell survival.

Fresh frozen plasma (FFP) must be maintained at or below -18°C throughout the chain. Shelf life is 12–24 months frozen; once thawed (a 30-minute process at 37°C in a regulated water bath), it must be used within 4 hours or within 24 hours if thawed at 1°C–6°C. In a high-tempo Role 2, thaw-on-demand capability is operationally essential – waiting 30 minutes for FFP during damage control resuscitation is not clinically acceptable, which drives some facilities to thaw FFP in advance based on predicted demand, creating a second time-bounded inventory that the software must track separately.

Platelets require room temperature storage (20°C–24°C) with continuous gentle agitation to prevent clumping. Shelf life is only 5 days. Because of the short shelf life, low-echelon forward field hospitals rarely maintain platelet inventories; Role 3 facilities may hold small stocks. The agitation requirement makes platelets impossible to transport in standard refrigerated containers used for red cells.

Low-titer group O whole blood (LTOWB) is increasingly used in military damage control resuscitation because it delivers red cells, plasma, and platelets simultaneously in their physiological ratios. Storage requirements mirror pRBC (1°C–6°C) but shelf life is shorter – 21 days. Walking blood bank (WBB) whole blood, drawn from pre-screened donors within the unit, has an even shorter shelf life of 24 hours and requires immediate cold chain management from the moment of collection.

Inventory management across the echelon structure

Military medical echelons define both the capability level of the facility and its expected blood product inventory profile. Understanding the echelon structure is necessary to design software that fits the logistics reality at each level.

Role 1 – the combat medic and battalion aid station – typically carries no blood bank capability. Some advanced Role 1 setups carry 2–4 units of LTOWB in a portable field blood refrigerator (PBFR) for immediate resuscitation before MEDEVAC. The software requirement here is minimal: a mobile app that can register a unit, display its expiry, and record a transfusion event offline, syncing to the Role 2 when connectivity is available.

Role 2 – the forward surgical element or medical company – maintains a forward blood bank with a small inventory of pRBC and FFP (typically 10–20 units each) and, increasingly, LTOWB. The Role 2 blood bank is managed by a blood bank officer with limited laboratory capability. Blood grouping and crossmatching are usually not possible; the facility relies on pre-typed group O products. Software at this level must support inventory receipt, custody transfer, FEFO (first-expired, first-out) issue, temperature log review, and resupply requests – all from a ruggedized tablet running an offline-capable application. See the broader discussion of military medical logistics for the wider context of Role 2 supply management.

Role 3 – the field hospital – operates a full blood bank information system (BBIS) with laboratory capability. It can perform ABO/Rh typing, antibody screening, and compatibility testing. It holds the broadest product range and serves as the regional resupply node for Role 2 facilities in its sector. The Role 3 BBIS must integrate with the army medical information system for patient tracking and post-transfusion outcome recording. It must also produce the haemovigilance reports required by national regulations and NATO STANAG 2128 standards.

Role 4 – the definitive care hospital, usually in the home nation – maintains a civilian-standard blood bank. The field-to-Role-4 chain must support transfer of patient blood records, transfusion histories, and adverse event reports in a format compatible with national haemovigilance systems.

Temperature monitoring: sensors, gateways, and excursion management

Continuous temperature monitoring across all storage and transport assets is the technical foundation of field blood chain management. The sensor architecture mirrors the general cold chain approach described in the article on cold chain management for military medical supplies, with blood-specific thresholds and audit requirements.

Each storage asset – blood refrigerator, transport container, PBFR – is fitted with a primary digital temperature sensor (RTD or thermistor) connected to the refrigerator's controller, plus one or more independent BLE temperature loggers as redundant monitors. The BLE logger transmits readings every 2–5 minutes to the facility's blood management gateway, which aggregates readings from all monitored assets and writes them to the time-series store with millisecond timestamps.

During transport between facilities, a portable BLE data logger travels inside the transport container alongside the blood products. The logger records temperature at 5-minute intervals. When the container arrives at the receiving facility, the logger's data is downloaded via BLE to the receiving tablet, and the blood management app processes the temperature record before accepting the transfer. Any excursion above 6°C (for red cells) or above -10°C (for FFP) during transport is flagged immediately. The receiving medic cannot mark the units as accepted until the flag has been reviewed by the duty medical officer or the system has confirmed the excursion was within the acceptable transient limit.

Excursion assessment and the 30-minute rule

Not every temperature deviation results in product discard. Military blood bank standards distinguish between transient excursions – typically caused by door opening, container lid removal, or a brief power interruption – and sustained excursions that compromise product integrity. The standard threshold for pRBC is: temperatures above 6°C for a cumulative period exceeding 30 minutes require a medical officer to assess whether the product should be used, held for further evaluation, or discarded. The blood management software calculates cumulative excursion time automatically from the temperature log and applies this rule to produce a disposition recommendation. The final decision remains with the qualified medical officer; the software provides the data to make that decision quickly and with complete temperature history available.

FEFO inventory control and expiry management

Blood product expiry is the most operationally consequential inventory management challenge in the field blood supply chain. A unit of pRBC that expires unused represents both a wasted resource and a logistics failure – it arrived at a facility that lacked the demand to consume it before expiry. Preventing avoidable wastage requires both accurate demand forecasting and active expiry management.

The FEFO discipline must be enforced at the point of issue. When a medic or nurse selects a blood product unit for a patient, the system should present the unit with the earliest expiry date that is compatible with the patient's blood group and the clinical requirement. This is not always what happens in practice – under pressure, clinicians reach for the nearest available unit, not the one closest to expiry. A well-designed blood management app places the FEFO-recommended unit at the top of the selection list and requires an explicit override action if the clinician selects a later-expiry unit. Override reasons are logged.

Near-expiry alerts are a critical feature. The system generates automatic alerts at configurable thresholds – typically 48 hours and 24 hours before expiry – for every unit in inventory across all facilities visible to the user. For a Role 3 blood bank officer overseeing multiple Role 2s in the sector, the dashboard must aggregate expiry status across all facilities and identify units at risk of wastage. Where a unit at near-expiry at one facility could be redistributed to a higher-tempo facility with more demand, the system generates a redistribution recommendation with the window available for the transfer before expiry.

Resupply workflow: from role 2 demand to role 3 dispatch

The resupply cycle for blood products at a forward Role 2 operates on a 24–72-hour cadence under normal operational conditions, shortening to immediate priority during a mass casualty event. The software must support both cadences without requiring different workflows – the difference is urgency classification and dispatch priority, not the process itself.

Automated resupply triggers fire when inventory levels cross commander-set thresholds. A Role 2 facility might configure: warning level at 10 units of pRBC (generate a planned resupply request, no immediate action required) and critical level at 6 units (generate an urgent request and alert the Role 3 blood bank officer immediately). The generated request is pre-filled with product type, quantity, blood group mix requested, the facility's current inventory, and the estimated consumption rate over the past 72 hours. The Role 3 blood bank officer reviews and approves the request, assigns units from inventory, creates a dispatch record, and initiates the temperature-monitored transport.

During a mass casualty event, the resupply trigger changes to a direct communication channel: the Role 2 medical officer sends a flash blood request through the blood management system, which generates an immediate alert at the Role 3 and at the theater medical logistics element. The system tracks the dispatch, transport, and receipt in real time, giving the theater medical logistics officer visibility of where every blood product is at every moment of the resupply cycle.

Walking blood bank: donor management and tracking

When the forward blood supply runs out – or when the demand from a mass casualty event outstrips the stocked inventory – the walking blood bank (WBB) converts pre-screened military personnel into emergency donors. The blood management software must support the WBB workflow as a first-class capability, not an afterthought.

Pre-deployment, potential WBB donors are screened for ABO/Rh type, selected infectious disease markers (HIV, HBV, HCV, syphilis), and haemoglobin level. Their records are entered into the blood management system and replicated to offline-capable devices at each formation's medical element. When a WBB draw is required, the medical officer queries the system for available donors of the required blood group within geographic range – typically using the last known GPS position of the donor's parent unit. The system generates a ranked list of candidates with donor ID, blood group, last TTI screen date, and last donation date (to enforce minimum inter-donation intervals).

When a donor presents, the draw is recorded in the system: donor ID, blood group confirmation, collection date, time, and location. The system assigns a 24-hour shelf life, generates a unique unit identifier compliant with ISBT 128 labelling, and links the unit to the donor record. The collected unit is managed identically to a stored unit from this point forward: temperature monitored, custody tracked, FEFO-issued, and final disposition recorded. The donor record is updated to reflect the draw date, preventing inadvertent re-use within the minimum inter-donation interval.