EVIDENCE

What each number measures
and what it does not prove

Start event, end event, period, sample, nature of the evidence and limitations. When a piece of information is not documented in the available source, it appears as not validated.

Stopwatch arc with fine tick marks and a hand at the start of its sweep

The 52-second metric

  • NATUREMeasured in production
  • WHAT WE MEASURETime from opening the editor for that exam to signing the report
  • MEDIAN52 s · 54.6% under 1 min
  • MEAN3 to 5 min in the same snapshot
  • SAMPLE5,200 completed reports
  • PERIODFixed 30-day historical snapshot: 2026-04-09 to 2026-05-09
  • INCLUSIONcompleted reports in the available snapshot
  • EXCLUSIONacquisition, PACS queue, study transfer and administrative steps outside the editor
  • LIMITATIONDoes not measure the service's total TAT, clinical quality, causality or future performance.
WHAT THE 52 s DO NOT SAY

A number that falls apart if you ask too much of it.

DOES NOT MEASURE ACCURACY Telemetry counts time, not clinical correctness. A fast, wrong report is worse than a slow, correct one.
DOES NOT COMPARE INSTITUTIONS Exam mix, template and shift habits change the number. It cannot be used to rank institutions.
DOES NOT PROMISE YOURS The median comes from our production base. Your number shows up in your pilot, with your criteria.

Where the clock starts and where it stops

The stopwatch starts when the radiologist opens the editor for that exam and stops at signature. Left out of the count are image acquisition, the PACS queue, study transfer and any administrative step before or after. The metric covers exactly the stretch where the platform acts, and nothing beyond it.

That boundary is a choice against our own interest. A TAT measured from the exam's arrival to signature would yield a larger number of minutes saved. And it would largely measure the institution's operation, not the product. We prefer the narrow window: it is smaller, it is auditable and it answers only for our part of the workflow.

The available source confirms the window, the sample and the start and end events. It does not publicly document stratification by modality, complexity, institution or a detailed outlier policy. That gap prevents treating the result as representative of any service.

Median, mean and estimate are not interchangeable

In the historical snapshot, the median is 52 seconds. Among the reports, 54.6% are under one minute, and the reported mean is between 3 and 5 minutes. The three values describe the observed distribution, but do not explain causality or clinical quality.

The estimate of about 10 hours per 100 reports uses a different class of evidence. It combines the rounded internal mean of 4 minutes with an approximate external baseline of 10 minutes. It is not observed time saved in a paired comparison.

We withdrew the claim of a reduction of up to 78% because it mixed statistics and a baseline without a reproducible paired comparison.

The literature-based estimate

The approximate baseline of 10 minutes per exam is attributed to Forsberg et al., Journal of Digital Imaging, 2017. This page classifies it as a literature-based estimate, not as a Laudos.AI measurement.

The external study's modality mix, year and setting may differ from your service. A locally measured baseline should prevail in the institutional pilot.

The second measurement, which is not clinical validation

Time does not describe quality. LaiBench is a controlled internal fidelity benchmark on a published, versioned set. It does not constitute external clinical validation. The AI structures and suggests; the physician reviews, edits, validates and signs, in accordance with Resolution 2.454/2026.

The LaiBench score and editor time measure different things. Neither of them, alone or combined, proves clinical outcome, safety in any context or superiority over competitors.

How to knock down this number

The honest way to check is to reproduce it. Before changing anything, measure in your service the time between opening the editor and signing, using the same event definition as this page. Record the median and the mean. Then run the pilot and measure again, over the same 30-day window and without discarding any case.

If the difference in your environment is smaller than ours, the number that counts is yours. We want to know: we publish the methodology here so you can challenge it with measurement, not opinion.

A historical snapshot, not a real-time dashboard

The published value corresponds to the fixed period from 2026-04-09 to 2026-05-09, with 5,200 reports. Without access to a more recent verifiable internal source, it remains frozen with its date.

Every page that cites the median must point to this snapshot. Updating the date or calling the number a rolling window without recalculating the source would be fabricating recency.

The 3.06% WER metric

  • NATUREControlled internal benchmark
  • WHAT WE MEASUREWord error rate (WER) in dictation of radiology sentences in Brazilian Portuguese
  • RESULT3.06% WER after vocabulary on the controlled set
  • SAMPLENot documented in the available public source
  • AUDIOExactly the same audio sent to each model evaluated
  • VOCABULARYMeasured raw and after medical vocabulary, with the same vocabulary applied to all models
  • CLINICAL TERMSExact preservation of medical terms evaluated separately from overall WER
  • DANGEROUS ERRORNegation, laterality and measurements count separately: they weigh more than articles and grammatical normalization
  • VERSION AND PERIODBenchmark v1.0, August 2026
  • DOES NOT COMPARENumbers published by other systems are in English, with their own test set and normalization

What the 3.06% does not say

It is speech recognition WER, not clinical correctness. The number says that the dictated word came out written as it was spoken. It does not say the report is right. LaiBench is what answers for correctness, and the two measurements do not replace each other: a perfect transcription of wrong reasoning is still wrong.

A direct comparison with other systems does not exist, and we are not going to fabricate one. The numbers they publish are in English, on their own test sets, with their own normalization criteria. Stacking everything on the same bar would make a pretty chart and an indefensible claim. What this number supports is narrower. In radiology dictation in Brazilian Portuguese, with medical terms inside sentences, the transcription got 3.06% of the words wrong.

The sentences are controlled, and that is a limitation, not a detail. A shift has room noise, a bad microphone, accents, fatigue and interruptions. The reading-room number is the one that shows up in your pilot, with your audio. If it comes out worse than this one, yours is what counts.

A public sample is not yet documented for the WER. Missing are the number of audio clips, speakers and devices, as well as specialties and the normalization protocol. Until that is published, we treat the result as a controlled internal benchmark, incomplete for generalization.

The LaiBench fidelity score

  • NATUREControlled internal benchmark
  • RESULT90% fidelity in the published snapshot
  • VERSION3.10.0
  • SAMPLE120 cases
  • SNAPSHOTPublished on 2026-06-23
  • SUITEHash b7f412e25a713520…
  • LIMITATIONFidelity score on the published internal set; not external clinical validation.
TIME PER REPORT, IN THE SAME MEASUREMENT
Manual workflow (literature) ~10 min
Laudos.AI · mean, complex cases included 3–5 min
Laudos.AI · median 52 s

Median and distribution measured in production, from editor open to signature. The mean includes the complex cases. See methodology

See the public benchmark Run the numbers on your volume View demo Talk to us

How to read the numbers without turning them into a slogan

What the 52-second number includes

The measurement starts with the editor open and ends at signature. It includes dictation, structuring and review within that interval. It is not the total time since the exam arrived. And it does not claim that every case takes the same time. The median describes the center of the distribution, while complex cases remain longer and call for separate analysis.

The 54.6% rate under one minute sizes the operational effect, together with the estimate of hours returned. Neither replaces the institution's baseline. Modality, complexity, experience and template quality change the result. That is why the pilot measures the team itself with the same criteria before and after.

Speed does not end the evaluation

A clinical adoption should also look at corrections, addenda, template adherence, disagreements and the perception of those who review. Gaining seconds while increasing rework would not be a gain. The public methodology exists so anyone can question, reproduce and compare the number against quality, not to end the conversation.

NEXT STEP

Bring your criteria

If your operation measures differently, the pilot uses your event definition. Bring your exam types, your template, your workflow and your baseline.

FAQ

Questions and answers

What exactly do the 52 seconds measure?

The time between opening the editor and signing the report, as a median. In the same measurement, 54.6% of reports come in under one minute. The measured workflow

Does every number published on the site have a methodology?

The time metrics have an event, a window, a sample and limitations. The 3.06% WER does not yet have a documented public sample and is not externally reproducible. LaiBench is internal and controlled, not external clinical validation. The quality measurement

Why is the mean higher than the median?

Because the mean includes the complex cases. We measure median and distribution in production, from editor open to signature, and publish both side by side so the tail is not hidden. The numbers in the same measurement

Does speed end the evaluation?

No. Speed does not measure clinical quality. LaiBench measures fidelity on a controlled internal set; the institution still needs to validate safety, integration, performance and results in the local context. LaiBench

Content updated on .

How to cite

LAUDOS.AI. Methodology and published measurements · Laudos.AI. Laudos.AI, 2026. Available at: https://www.laudos.ai/metodologia.

BibTeX
@techreport{laudosai-metodologia,
  title       = {Methodology and published measurements · Laudos.AI},
  author      = {Laudos.AI},
  year        = {2026},
  institution = {Laudos.AI},
  url         = {https://www.laudos.ai/metodologia}
}