RadDose

What RadDose does

Dose is recorded per exposure from something a machine produced — the modality’s own dose report, its image headers, or the readout a technologist copies at the console — and every row names which. Totals accumulate per patient by quantity and unit, computed at read time rather than stored. A dose above a reference level raises an alert that closes only with a written justification. NO REFERENCE LEVEL SHIPS WITH THE APP: levels are imported from a document the hospital supplies, and cannot be stored at all without naming it, so until one is loaded every exposure is recorded and nothing is compared — which the screen says in as many words. Where an image archive is connected, dose is read from the study record; where none is, console entry is the whole app and it works.

How you actually use it

1. 1Load the reference levels your hospital works toNone ship with the app: on Reference levels, name the document and paste its rows as modality, study, quantity, value, unit, and every row keeps that document’s name beside it.
2. 2Record what the console showedRecord what the console showed takes the patient’s id, the modality, the study, the quantity, the value and the unit — and every exposure row names what produced its number rather than an estimate.
3. 3Read one patient’s running totalOn A patient, paste the patient’s id and the totals appear per quantity and unit, computed on every load and never added across units, beside every exposure and where each was read from.
4. 4Answer what went overOver the level lists exposures above an imported level; Justify asks for the reason in writing and closes the alert with your name on it — the app does not block imaging, and a study whose unit no level was imported in is not compared at all.

What it does not do

It does not block imaging, and it invents nothing: no reference level ships with it, and a level cannot be stored without naming the document it came from.

Questions clinics ask