What does a head-impact sensor actually tell us?
Modern head-impact sensors can record remarkably detailed information. A small inertial measurement unit may sample three-dimensional linear acceleration and angular velocity hundreds or thousands of times per second, producing a multichannel time history of an impact.
Yet what is recorded, what is reported, and what is ultimately claimed are three different things. Much of the apparent simplicity — or apparent sophistication — of head-impact monitoring is created after the measurement has already taken place.
A six-degree-of-freedom inertial sensor does not inherently measure a "20 g impact" or a "high-risk hit." It records changing acceleration and angular motion over time. Those time-varying signals can subsequently be represented in many ways.
The simplest approach retains one or a few extrema — peak linear acceleration, peak angular acceleration, peak angular velocity. Other systems add direction, duration, counts, thresholds, cumulative exposure, or proprietary load and severity scores. This reduction is often useful: a few numbers are far easier to display, compare, and interpret than several hundred measurements across multiple channels. But reduction also discards information.
Two impacts can have similar peak acceleration while differing substantially in duration, waveform shape, directional evolution, rotational behaviour, temporal sequencing, or the relationship between translational and rotational motion. Once an event has been reduced to a handful of scalar values, those differences cannot necessarily be reconstructed. This is therefore not primarily a question of sensor sophistication — several commercial systems acquire rich multiaxial time series internally. It's a question of representation: what's routinely delivered to users remains predominantly peaks, counts, thresholds, and a small number of derived or proprietary scalar metrics.
A measurement can be inaccurate because the sensor doesn't follow the skull faithfully — skin or helmet motion, insufficient coupling, filtering, sampling limitations, sensor saturation. These are technical problems with the reading itself.
Even a perfectly measured peak acceleration still describes only one aspect of the event. Whether that quantity adequately represents the mechanics relevant to the question being asked is a separate issue entirely.
Improving sensor attachment may yield a more accurate peak value without making that peak a more complete description of the event. Conversely, retaining more of the waveform doesn't automatically make the underlying measurement accurate. Rich data and accurate data are related — but they are not synonymous.
Sensor measurements are frequently transformed into increasingly distant interpretations. A useful conceptual hierarchy:
Quantities actually observed by the sensor: acceleration, angular velocity, pressure, position, or similar physical signals.
Quantities calculated from the measurements — head-centre-of-gravity acceleration, angular acceleration, impact direction. May be valid physical estimates, but depend on calibration, geometry, coupling assumptions, and mathematical transformation.
Estimates such as brain strain, tissue loading, injury criteria, "brain load," or injury probability. Not measurements — outputs of models whose validity depends on assumptions, training data, validation population, and endpoint.
Statements about neurological condition, concussion, consciousness, treatment need, or clinically actionable classification. These require independent clinical validation and cannot become measurements merely because software produces them automatically.
The distance between the measured signal and the language used to describe it can become substantial.
This distance can be thought of as inference inflation. It doesn't necessarily mean a derived quantity is wrong — mechanical reconstruction, computational modelling, and predictive algorithms are essential scientific tools. The problem occurs when the distinction between measurement and inference becomes blurred:
The commercial head-impact market provides many examples across this spectrum — and, importantly, counterexamples: systems that collect sophisticated data while making relatively restrained claims. The amount of information measured and the distance of the subsequent inference are largely independent properties. A useful way to evaluate any system is to ask two separate questions: how much of the mechanical event is preserved, and how far does the interpretation move beyond what was actually measured? A system can perform well on one dimension and poorly on the other.
IFS addresses primarily the first of those two questions. Instead of immediately compressing an event into a small number of extrema, it derives a larger collection of descriptors from the measured time history — temporal structure, translational and rotational behaviour, their relationships, waveform morphology, and other mechanically distinguishable properties.
The purpose is not to convert the sensor into a direct measurement of brain tissue response. It's to preserve more of the information contained in the mechanical event. An IFS feature describing translational–rotational coupling is still a description of measured motion. A feature-space cluster is still a pattern among mechanical descriptors. Similarity between two events means they resemble one another in the selected feature representation — whether such patterns associate with particular tissue responses, symptoms, injuries, or outcomes is a separate empirical question.
This hierarchy allows a representation to become richer without requiring its biological interpretation to become more speculative.
IFS can describe an event as having a particular mechanical trajectory, coupling structure, temporal phenotype, or feature-space similarity — without calling that pattern brain injury, tissue strain, or concussion risk. That separation between measurement, representation, and inference is fundamental to the way Impact Feature Space is intended to be used.
Why the brain doesn't simply follow the skull — the viscoelastic transfer problem.