Medical module

Injuries and illnesses in one place — status, expected return, diagnosis, and history.

Every injury and illness an athlete has had, kept as one record each — and on the group screen, the answer to the question asked before every session: who can train today?

ForCoaches, medical staff & athletesWhereWeb app

An open Medical record for a right ankle sprain: the properties row reading New, Open, No training and Club physiotherapist; the start and expected-return dates; circumstances for competition, contact, domestic training environment, moderate and grass; a clinical note; the OSIICS diagnosis AL1 Sprain lateral collateral ligament ankle tagged right, ankle, ligament; and the athlete's other records listed beside it as two open and four closed. — One health record: what it is and how much it limits training, when it started and when they're due back, how it happened, the note, and the coded diagnosis.

Set the Injury status the day a problem appears, even if nothing else is filled in yet. It's what colours the athlete on the group screen, and what Team daily readiness reads the next morning.

Where to find Injuries & Illnesses

Open the Medical module from the main menu. As a coach or medical staff member, pick one of your groups and then an athlete, or choose Entire Group to see that squad at once. As an athlete, you go straight to your own records, if your team gives you access to them.

Medical data is sensitive, so who can see and edit it is permission-controlled and configured per team, and also per group — a coach can have full access to one squad and read-only access to another. If you don't see this module, it may not be enabled for your team — ask your administrator.

Who can train today

The group overview is one row per athlete, and it's the screen you'll use day to day. Each row carries:

a status pill — the athlete's worst current Injury status, the field that says how much they can do right now, across everything they have open. Green means full training, which is not the same as an empty record: an athlete can be back in the session with an injury still open;
their open health problems, each with an icon marking it as an injury or an illness;
the expected return to full training, or a dash when no date has been set. A date that has passed turns red and says how many days overdue it is.

An athlete with nothing open still gets a row, marked No health problems.

The Medical module's group overview, a dark table with one row per athlete: two athletes green with no health problems, one amber whose expected return has passed and is flagged as overdue, one red with an illness due back imminently, one green with an injury still open, and one red with two open injuries — one of them with no return date at all. — A green pill means full training, not an empty record — one of these athletes is back in training with an injury still open.

Log an injury or illness

Add the record

Select + (Add record) above the athlete's record list, and choose Injury or Illness.

Name it

The record opens straight away, ready to edit. Type over the placeholder title.

Fill in what you know

Set the Injury status first — it's the field the rest of Yarmill reads — then the dates, the diagnosis, the circumstances, a note, and whoever is looking after it. There's no Save: everything auto-saves, and every change is written to Activity.

A new record starts with its Date of injury set to today, its Treatment status at Open, its Classification at New, and its Injury status at Modified training for you to correct.

The Medical module with the plus button above an athlete's record list selected, opening a two-item menu offering Injury or Illness. — The + above the record list is the way in: pick injury or illness, and the record opens.

Or log it in seconds with New record

New record in the tool bar — or the N shortcut — opens a short dialog instead of the full record. It takes only the essentials: the Record type, a name, the Status, the Date of injury, and any files you already have. It's the one to reach for pitch-side, when the point is to get the group screen right today and fill in the clinical detail later.

It's also the one place in the module that waits for you: Save commits it, Open full detail commits it and takes you into the record, and closing the dialog without either discards it.

The New record dialog over a record, with fields for record type, name of injury, status, date of injury and files, and buttons for Open full detail and Save. Three parts are labelled: record type, injury or illness; status, how much they can train — it colours the group screen; and Save, or Open full detail — both create the record. — The New record dialog asks only for what makes the group screen right today.

What a record holds

Every field on a record, in the order the record shows them. The first four sit together in the Properties row, the three dates under Key dates.

Name

What the problem is, in the athlete's record and in every list — for example, "Right ankle sprain (lateral)". Click the title to rename it.

Type

Injury or Illness, chosen when you create the record. It sets the icon on the card, and it decides which half of the diagnosis codelist you search.

ClassificationDefault: New

New or Recurring — the flag that makes a repeat problem visible as a pattern rather than as another isolated entry.

Treatment statusDefault: Open

Open or Closed. Closing a record moves it to the Closed list.

Injury statusDefault: Modified training

How much the athlete can do right now: Full training or competition (green), Modified training or competition (amber), or No training or competition (red). This is the colour on the group overview.

Responsible staff

The staff member or institution looking after the problem. Free text.

Date of injuryDefault: Today

When the problem started.

Expected return to full training

When you expect the athlete back. This is the date the group overview shows, and the one it turns red once it has passed. Clear it with the × if it stops being meaningful.

Closure date

Stamped when you close the record, and editable afterwards.

Circumstances

Optional context for how it happened — Activity, Injury mechanism, Location, Severity, Surface. The values in each list are configured for your team: a football club might log mechanism, playing surface and severity from purpose-built lists, while another team has a different set or none at all.

Note

Free text — the mechanism, the treatment plan, what to watch for on the way back.

Diagnosis

The coded diagnosis, its Side (injuries only), and the body-region and structure tags that follow from it. See Code the diagnosis below.

Files

Documents on the record: medical reports, X-ray and MRI images, physiotherapy plans.

Activity

The automatic change log, and the comment box. See Track the return to training.

Code the diagnosis

Add a diagnosis from the record's Diagnosis section. Type what you're looking for in plain words — ankle sprain, tonsillitis — pick the entry from the list, set the Side if it's an injury (an illness hasn't got one), and select Add, or press Ctrl ↵ (⌘ ↵ on a Mac). Yarmill tags the record with the body region and structure that follow from the code, so AL1 Sprain lateral collateral ligament ankle carries ankle and ligament without anyone typing them.

The list is filtered by the record's type — injury codes for an injury, illness codes for an illness — and the record links straight out to the full OSIICS code list.

A team can pin the diagnoses it uses most to the top of the list, so the everyday cases are there before you type anything. Which ones are pinned is chosen by the team and configured for your instance — it doesn't follow your usage on its own.

The diagnosis picker open on a record, the search box holding the words ankle sprain and the results listing Ankle sprains ALJ, Sprain lateral collateral ligament ankle AL1, Sprain medial collateral deltoid ligament ankle AL2 and Ankle multiple ligaments sprain ALM, above a row with a Diagnosis select, a Side select, Cancel and Add. Three parts are labelled: the OSIICS code beside every diagnosis in the list; search in plain words, type the problem, not the code; and side, left, right, bilateral, or unknown. — Four results for 'ankle sprain' — the general `ALJ`, and three more specific codes.

What OSIICS is, and why the code matters

OSIICS — the Orchard Sports Injury and Illness Classification System — is one of the two coding systems aligned with the International Olympic Committee's consensus statement on recording injuries and illnesses in sport. Each entry is a short code and a plain-language diagnosis, built so the code carries the anatomy: an injury code starts with the body region (AL1 is an ankle ligament), and illness codes all start with M (MPIT is tonsillitis).

A coded diagnosis stays comparable; free text doesn't. Ten people describing the same problem produce ten different strings, and a season of them can't be added up. Coded, the same problem reads the same years and staff changes later, a recurring ankle is recognisably the same ankle, and what you hand to a federation means what they mean by it.

It codes what the problem is, not how it happened or how bad it was — that's Circumstances and the key dates. And unlike the Circumstances lists, which are Yarmill's own and configured per team, the codelist is the same on every instance. That's the point of a standard. Its labels show in English as well as Czech; the code underneath doesn't change.

OSIICS is maintained by John Orchard and colleagues and is free to use with acknowledgement, which Yarmill makes here. Yarmill's codelist is OSIICS version 16; the codelist and its documentation are at johnorchard.com/osiics.html, and the current version is published open access in JSAMS Plus (doi:10.1016/j.jsampl.2025.100119).

Track the return to training

Keep the Injury status current — it's the field the rest of Yarmill reads for availability. A typical recovery walks it back up: No training or competition while the athlete is out, Modified training or competition as they start doing some of the session, Full training or competition when they're available again. Move the Expected return to full training as the picture changes rather than leaving a date to go red.

Every change is logged automatically under Activity, with who made it and when — the status changes, the dates, the diagnosis, each circumstance. Use the comment box to add what the log can't infer: how the session went, what the consultant said.

Close a record, and the history it leaves

When a problem resolves, set its treatment status to Closed. Yarmill stamps the closure date, moves the record to the Closed list, and sets its Injury status to Full training or competition — so the athlete's availability updates without a second step.

A record that turns out not to be over can be reopened: set its treatment status back to Open and it returns to the open list.

Closed records stay in the athlete's Closed list, so the next flare-up of the same problem can be marked Recurring against something you can point at — the basis for preventing the next one rather than only managing this one.

An athlete's health records in the Medical module, split into Open with two entries and Closed with four, each card carrying an injury or illness icon, a coloured status pill, a classification glyph, and — on the closed ones — a check and the date it was closed, going back to 2024. — One athlete's record list: what's open now, and everything that's been closed, with its closure date.

Delete a record

Select the trash icon in the tool bar and confirm.

Deleting is permanent, and it takes the diagnosis, the notes, the files and the history with it.

A problem that turned out to be nothing should be closed, not deleted — the record of what was suspected and ruled out is worth keeping.

What athletes see

Where their team allows it, athletes work with their own records — their Open and Closed lists, the full detail of each one, and Add record or New record to add a problem themselves after a doctor's visit, an X-ray, or an MRI.

On other instances the module isn't shown to athletes at all. Which one you have is a configured permission, so check your own setup before telling a squad to keep their records up to date.

The Medical module in an athlete's own session: the sidebar lists Injuries & Illnesses and stops there, with no group dropdown, no athlete list and no Entire Group entry, and the record list shows only that athlete's own open and closed records, with one of them open beside it. — The same module from an athlete's own account — their records, and no group to switch to.

How it connects

The Injury status flows into Team daily readiness, where it sits alongside the day's wellness questionnaire and device recovery from integrations, so the morning overview already knows who's out — see Read team readiness.
Illness and injury periods are shaded into the background of the recovery and training-load charts, so a dip in load or recovery is read against when the athlete was actually hurt.
The Expected return to full training is a planning input, not a clearance: it tells you when to start rebuilding load, not that the athlete is available.
Documents added to a record are stored with it, alongside the athlete's other files.

6.1Medical module