Skip to main content
Radiology & Imaging10 min read

TLD Badge and Radiation Worker Dose Record Management

Personnel monitoring fails on administration, not on physics. This is the working cycle for issuing, collecting, dispatching and acting on TLD badges, the records an inspection asks for, and the escalation path when a reading comes back high.

Aparna Raghavan

Diagnostic Imaging Operations Manager

#tld badge#personnel monitoring#radiation safety officer#occupational dose records#aerb compliance
TLD Badge and Radiation Worker Dose Record Management

The failure is administrative, and it is always the same failure

Personnel monitoring is conceptually simple. Radiation workers wear a dosimeter, the dosimeter is periodically exchanged and read by an approved laboratory, and the readings become a permanent occupational record for each worker. Almost nothing about the physics causes hospitals trouble. What causes trouble is the administration around it: badges not worn, badges worn by the wrong person, cycles dispatched late, reports received and filed without anyone reading them, and staff who left two years ago still on the list while a new technologist has never been issued one.

The consequence is not merely a compliance finding. The record exists to protect the worker, and a gap in it cannot be reconstructed later. If a technologist asks in ten years what their cumulative occupational exposure has been, the honest answer for many departments would be that nobody knows, because two of the quarterly cycles were never dispatched and four badges were reported as unreturned. That is a duty-of-care failure that happens to also be a regulatory one.

Treating it as a recurring operational cycle with a named owner, rather than as a periodic chore that surfaces when the laboratory sends a reminder, is the whole of the fix. Everything below is the shape of that cycle.

Personnel monitoring cycle showing issue, wear, collection, dispatch, reading and record filing
Personnel monitoring cycle showing issue, wear, collection, dispatch, reading and record filing

Getting the worker list right, and keeping it right

Everything depends on an accurate list of who is a designated radiation worker, and that list is wrong in most departments. It should be derived from role and actual working location rather than from who asked for a badge. Radiographers and radiologists are obvious. The people commonly missed are those who work in radiation areas without thinking of themselves as radiology staff: cath lab nursing and technical staff, theatre staff present for image-intensifier use, and biomedical engineers servicing equipment in beam-on conditions.

The list has to be maintained against joiners and leavers rather than reviewed annually, because the gaps it produces are silent. A new technologist working three months before a badge is issued has three months of unrecorded exposure that cannot be recovered. Tie badge issue to the same onboarding step that grants system access and area access, and tie badge return to exit clearance, so the list moves when staff move rather than when someone remembers to check.

Record enough identity detail on the badge assignment to make the record meaningful later: full name, employee identifier, designation, work area, date of designation as a radiation worker, and the badge identifier and its assignment period. A dose report that cannot be tied unambiguously to one individual across a name change or a transfer is of limited value as a lifetime occupational record.

Roles frequently missing from the monitored list

  • Cath lab nursing and technical staff present for fluoroscopy
  • Theatre staff working with mobile image intensifiers
  • Biomedical engineers servicing equipment under beam-on conditions
  • Staff rotating in temporarily or covering another department
  • Contract and agency staff working in designated areas

The exchange cycle, run as a calendar rather than a reminder

The exchange cycle is where slippage accumulates. Badges are collected, dispatched to the approved laboratory, read, and reported, and a new set is issued for the following period. Each of those steps has a date, and the whole thing works when those dates are on a calendar with a named owner and fails when it depends on someone noticing that a cycle is due.

Set the calendar backwards from the dispatch date rather than forwards from the collection date, because dispatch is the step with an external dependency and therefore the one that determines whether the cycle is late. Build in the collection reminder, the physical collection round, the reconciliation against the issued list, the packing and dispatch, and the expected return of results. Assign each step to a role, not a person, so the cycle survives leave and resignation.

Reconciliation at collection is the step most often skipped and the one that catches the most. Count what came back against what was issued, by badge identifier, and chase the difference the same day. Badges left in a locker, taken home in a coat pocket or quietly lost are ordinary events; a badge unaccounted for at dispatch and never followed up becomes a permanent hole in someone's record.

Exchange cycle calendar working backwards from the dispatch date with each step assigned to a role
Exchange cycle calendar working backwards from the dispatch date with each step assigned to a role

Reading the report instead of filing it

Dose reports arrive and are filed. That is the second great administrative failure, and it defeats the purpose of the exercise entirely, because the report is the only mechanism by which the hospital learns that something in its practice has changed. The radiation safety officer should review each report against the previous ones for the same individuals and against the pattern for their role, and record that the review happened.

What you are looking for is not only an absolute reading against a limit. It is change and inconsistency: a reading materially higher than that worker's own history, one worker in a group reading much higher than colleagues doing the same work, a reading where none was expected, or a reading of essentially zero for someone working full time in a fluoroscopy suite, which usually means the badge was not worn. Each of those tells you something specific about practice or about the monitoring itself.

Record the review as a dated entry with the reviewer named and any action noted, even when the action is none. An inspection asking whether dose reports are reviewed is asking for evidence, and a stack of laboratory reports with no annotation is evidence that they were received rather than that anyone looked at them.

Patterns in a dose report worth investigating

  • A reading materially above that individual's own established pattern
  • One worker reading well above colleagues doing identical work
  • A near-zero reading for someone working full time in a beam-on area
  • A reading recorded for a worker who was on leave that period
  • Any reading approaching an investigation or notification level

What to do when a reading comes back high

A high reading needs an investigation, not an email. The first question is whether it reflects genuine exposure or an artefact, because artefacts are common and are the more likely explanation. Badges left on a control console, stored near a source, sent through a scanner, or damaged in transit all produce readings that have nothing to do with the person named on them. Establishing which of these applies is the first step and is often the last.

If it is not an artefact, the investigation moves to practice and equipment. Was there a change in workload, a period of unusually heavy fluoroscopy, an equipment fault, a shielding problem, or a working position that puts the individual closer to scatter than intended? Involve the person concerned early and directly; they usually know what was different about that period and are entitled to be told what is being investigated about their own exposure.

Document the whole sequence, including the conclusion and any corrective action, and follow the notification requirements applicable to your facility where the reading crosses a level that requires them. Then check the following cycle specifically for the same individual rather than waiting for the routine review, and record that check. An investigation that concludes without a verified return to expected readings has not concluded.

Our first high reading turned out to be a badge that had spent six weeks clipped to the fluoroscopy console instead of a coat. The second one, a year later, was real. The only reason we knew the difference was that we had investigated the first one properly.

Radiation safety officer at a tertiary care hospital

The records an inspection expects to see

Inspection readiness for personnel monitoring is not a separate exercise; it is what running the cycle properly produces as a by-product. The artefacts expected are the current list of designated radiation workers with their badge assignments, the sequence of dose reports with no unexplained gaps in the cycle, evidence that reports were reviewed rather than merely received, investigation records for any elevated readings with their conclusions, and the retention of individual dose histories for the required period.

Retention deserves specific attention because occupational dose records are kept for a long time, and long-term retention is where departments relying on paper folders and individual laptops fail. Records have to survive a change of radiation safety officer, a department relocation and a system migration. Holding the dose history alongside the individual's employee record rather than in a departmental file makes it far more likely to survive all three.

Where the records live matters less than that they are complete, retrievable and attributable. Keeping the monitored-worker list, the cycle calendar and the review log in the same system the hospital uses for its other operational records, with the activity trail that comes with it, removes the commonest audit finding of all, which is not a bad reading but an absent one.

Making the programme survive a change of officer

Personnel monitoring programmes are often held together by one conscientious person, and they degrade quickly when that person moves on. The knowledge that lives in their head is exactly the knowledge the programme depends on: which laboratory, which contact, which cycle dates, where the historical reports are, which staff are on the list and why, and what was concluded about the elevated reading three years ago.

Write that down as a short standing operating procedure and keep it current, covering the worker list and its maintenance triggers, the cycle calendar, the dispatch process and the laboratory relationship, the review protocol, the escalation path for an elevated reading, and the retention arrangement. Two or three pages is sufficient. The test of it is whether a competent successor could run the next cycle correctly from the document alone.

Then have a second person run one cycle a year under supervision. It is the only reliable way to discover that a step nobody documented is load-bearing, and it means a resignation, an illness or a period of leave does not produce a missing quarter in a record that is supposed to last a working lifetime.

Standing operating procedure and cross-trained deputy keeping the monitoring cycle running through staff changes
Standing operating procedure and cross-trained deputy keeping the monitoring cycle running through staff changes
Share this article
Back to all articles

Keep reading

Related articles

See HealUDoc in action

From EHR to analytics, watch how one platform runs your entire hospital. Book a personalized walkthrough with our team.