Reading Injury as Open-Source Code When the Medical File Is Empty

At 10:17 p.m. on a Tuesday, my editor called. Eight hundred words on an athletics international's injury, filed before nine the next morning. I opened the folder marked "Injury files" on my hard drive — six seasons, more than four thousand hand-entered rows: minutes played, load cycles, muscle mass indices, recurrence traces by position. I typed the athlete's name. No results.

Three phone calls followed. A strength coach said "I heard something." A doctor who once worked with the youth setup said "I'm not authorised to speak." A federation official sent back a twenty-four-word statement: no expected return date, no imaging, no treatment protocol. I replied to my editor with a single sentence: not enough data to conclude. He sent back a question mark.

My entire trade lives inside that question mark.

Every press conference holds two stories: one that gets read aloud, and one you have to find yourself. But some press conferences have no second story, and the reason is not concealment. The reason is that nobody ever wrote anything down.

In 2026, aged twenty-four, I was the only reporter assigned to a V-League club in Binh Duong. At the pre-match press conference against Hanoi, I asked the head coach about the fitness of his centre-back, who had just been shifted into an unfamiliar role. A male colleague beside me smirked: "What would a girl know about a sweeper?" I did not argue. I wrote down everything, went home, and rebuilt that player's load table across the previous four rounds. Three weeks later he suffered a hamstring recurrence and missed three matches. My analysis ran on the club's official page, identifying a flaw in the treatment protocol.

I retell that not to win an old argument. I retell it because it shows what I lacked back then was not data — it was a place for data to survive.

In Europe, that problem was solved long ago at the infrastructure level. FIFA runs its own medical network for major tournaments. UEFA's cohort studies track thousands of match hours each season and publish periodic injury reports detailed enough for another club to read and adjust its training plan. World Athletics sets technical rules down to the millimetre: track shoe sole thickness capped at twenty millimetres, road shoes at forty, in force since 2026. Those numbers exist because someone is accountable for writing them down.

In Vietnam, the top division has fourteen clubs. Not one publishes a seasonal injury report. Athletics is thinner still: medical staff tend to appear only around competitions, like a rapid-response team, and when the meet ends the records end too. Youth setups mostly still run on paper. I once asked for the fitness records of an under-seventeen cohort to compare muscle development rates. The answer was: "let us find it first."

A World Cup 2026 sofa taught me to read injury as open-source code. The principle is simple: an athlete's body is not a black box but a readable system — on one condition, that somebody keeps a changelog.

In 2026 I was not sent to Russia. I sat at home, pulled data from FIFA's medical network and the final's movement statistics, and counted the acceleration bursts of a young French winger — Kylian Mbappe. The frequency far exceeded the normal accumulation threshold for a single half. I wrote fifteen hundred words predicting muscular injury risk if the fixture calendar stayed that dense. Published on 20 July, it was barely read. Three months later it was shared widely.

The lesson was not whether the prediction was right. The lesson is this: a prediction only has value when it is recorded before the event, with a date and defined criteria. Without a timestamp, all sports analysis collapses back into post-match commentary.

7 June 2026 — the day I stopped trusting intuition and started trusting data. Football was suspended, I had four empty months, and I used them to build a tracking sheet from six domestic seasons, cross-referenced with nutrition data from thirty young players. On the day the league restarted, I sent the host club an internal bulletin: one winger's muscle mass index sat roughly five percent below his pre-pandemic level, and I projected a form dip across the next two matches. Two weeks later he left the pitch in the sixtieth minute with an adductor injury.

There was no magic in it. There was a baseline drawn in advance, and a data point placed beside it.

Since then I read injuries in three layers. The first is the scene: the moment of exit, the mechanism, the body's reaction, who caught him, who gave the instruction. The second is the official statement, and I always sort statements into three categories: facts, opinions, and projections. "He has muscle pain" is a fact if it comes with an imaging date. "We are confident he will return soon" is an opinion. "He will definitely make the next match" is a projection, and that third category is almost always wrong, because it depends on tissue response rather than human will.

The third layer is the historical workload record. In football that means load cycles: acute load over seven days divided by chronic load over twenty-eight, sprint counts above threshold, minutes at high intensity, matches within a ten-day block. That ratio does not predict who will get hurt. It only shows who is entering territory their body has never crossed. In athletics the mechanics are entirely different: longer stride amplitude, greater ground reaction force, and a hard track that forgives far less than grass. Carbon-plated shoes have changed how we read both performance and injury: they allow athletes to hold speed at lower metabolic cost, but they channel force into the Achilles tendon and plantar fascia in a distribution that did not exist before.

Here I have to be explicit about my own conduct. At one SEA Games I sat and calculated the competition density of a female international running four events across five days — Nguyen Thi Oanh. I recorded the schedule, the recovery windows between rounds, the track dimensions, the start times. I wrote not a single word about her physical condition, because I had no medical data. Fans called it sacrifice. I called it a schedule that needed to be documented; diagnosis belongs to whoever holds the imaging and the signature on the file.

In Vietnam, reading injuries also runs into three environmental constants that overseas literature rarely accounts for properly. The first is heat and humidity: dehydration reduces plasma volume and raises heart rate at the same running speed, which distorts intensity readings unless corrected. The second is pitch quality: a team can play four matches in ten days on four surfaces of different hardness. The third is travel: long bus journeys before matches eat into sleep, and sleep is the most neglected recovery variable in every tracking sheet I have ever seen.

Add those three together and you have a technical reason why a small Vietnamese club cannot copy a European training plan. But you also have a reason why they can do far better than they currently do, because everything worth recording is cheap: date, minutes, self-rated intensity, sleep, site of pain.

An injury case is a test: does the club believe in the person or in the numbers?

Now the part I suspect many in the industry will not like.

Demanding more data can become a trap. I have seen twenty-column tracking sheets, updated daily, that nobody reads. Data does not generate conclusions; it generates a feeling of safety. A spreadsheet without a guiding question is just neatly arranged rubbish.

The root problem sits in the incentive structure. A club has reasons not to disclose a key player's injury: transfer value, opponent psychology, sponsor pressure. A reporter has reasons to exaggerate: drama sells. A fan has reasons to consume the story of a star's body, because it is easier to grasp than a load chart. Inside that incentive system, the honest operator loses twice: once for being slow to the story, once for having nothing to publish.

But I would argue the obsession with a star's medical file is hiding a far larger gap: the competence of the people who teach sport at grassroots level. A fifteen-year-old who learns landing mechanics incorrectly pays for it at twenty-five, and that payment never appears in any injury bulletin, because it gets filed under "poor progression". Academies branded with former stars are opening faster than properly curriculum-based coach education programmes. That is where the questions should be aimed.

The same logic applies to the transfer market. The race among big clubs is largely a brand arms race, where a contract is priced by engagement volume. But the clubs that generate real value are usually the small ones that know how to keep a player for three more seasons, how to manage his load, and when to sell. They do not have elegant data dashboards. They have one person watching and one notebook.

Team doctors do not treat football; they treat the seasons still ahead. That line holds in Europe, and it holds even harder where a single hamstring recurrence can erase an entire club's campaign.

If I had to propose one small thing that can be done immediately, it would be this: one page of medical bulletin per club, per month. Three indicators, anonymised if necessary, plus the number of injuries that month, average days lost, and recurrence count. Ten months makes ten pages. One season makes a readable file. No expensive software, no foreign consultants, no large budget.

A file like that is worth more than any press conference, because it answers the question press conferences always dodge: how much are we paying for a season?

As for that question at ten past ten on a Tuesday night, I still have no answer for my editor. And I suspect that one day, a national sports system openly saying "we do not know" will be the first sign of maturity in Vietnamese sports medicine — before we ever have enough data to say anything else.