ComplianceLive · in the productRegister

RadDose

Every exposure counted per patient, against the levels you imported.

Get RadDose Open the appAvailable nowHow pricing works →

What it is

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.

Who uses it: Built for: Diagnostics & Labs
Reads: Modality dose reports, imported reference levels, patient age
Writes: Dose records, dose alerts, justifications
Never: 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.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

How it works

Load 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.
Record 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.
Read 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.
Answer 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.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

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.

AI in RadDose

AskQuestions about what is on screen — “What needs attention in RadDose today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

RadDose — Radiation Dose — Count a patient’s radiation dose against the levels you imported — 01Radiation Dose — Count a patient’s radiation dose against the levels you importedCaptured from the running demo clinic

01Radiation Dose — Count a patient’s radiation dose against the levels you importedCaptured from the running demo clinic

1 of 1

Connected to

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.

Reads from · 2

ImageVault Patient Registry

Hands to · 1

ReadQueue

See the whole clinic →

Questions clinics ask

What does RadDose do?

Every exposure counted per patient, against the levels you imported. 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.

What data does RadDose read and write?

RadDose reads modality dose reports, imported reference levels, patient age and writes dose records, dose alerts, justifications. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does RadDose deliberately 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.

What happens to our data if we uninstall RadDose?

All clinical data stays in the record.

Is RadDose available today?

Yes — RadDose is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see RadDose running on your own patients?

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.

More in Compliance

All 154 →

Featured inDiagnostics QA stack Diagnostics & Labs Radiology