Radiopharmaceutical orders scheduled around decay, and every dose logged against the batch it came from.
A nuclear medicine department’s hot lab on one screen. You list your isotopes, each with its half-life and where you read it (a nuclear data table, the product leaflet); none ships. Each vial received or generator elution is logged with its calibrated activity and time and, when you have it, its volume. A physician orders a study with the activity they prescribe, the scan time and the uptake time; the injection time follows. From then on only physics is worked out, from your half-life: the activity each open batch will hold at the injection, the volume to draw, and the order sheet — how much to order calibrated for a given time so that every injection that day still gets its activity. Each administration is logged against its batch with the dose-calibrator reading and the times, corrected for decay and any residual; a dose more than your department’s own tolerance from the prescription (a setting with its source; with none set, nothing is judged) needs a reason, and a logged dose is kept as logged. The register lists every receipt and administration for a period and downloads as CSV.
/nuclear-medicinenucmed.readWhat it does not do, by design. A listing with only benefits is an advertisement.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.