Comparison date errors in radiology reports

Comparison date errors are a leading radiology report quality failure: they appear in nearly every category of documentation audit, and they are almost entirely preventable.

A comparison date error occurs when a radiology report documents the wrong prior study, references a date that does not match the study used for comparison, or notes a finding as stable or changed relative to an exam that was never actually pulled. Those errors matter because comparison is central to radiology interpretation. For interval scans, the reported change or stability depends entirely on what the report is being compared against. An incorrect comparison invalidates that assessment.

This article covers why these errors happen, what the standard of care says about comparison documentation, and how two different interventions address the problem at different points in the reporting workflow.

Why does the comparison date matter in a radiology report?

The comparison date identifies which prior study the radiologist used when interpreting the current exam. That information serves two purposes. Clinically, it tells the ordering provider exactly which baseline the radiologist was working from, so the stability or progression claim can be evaluated in context. Operationally, it establishes accountability: if a report says a nodule is stable compared to a prior chest CT from two years ago, the reader of that report needs to know which exam from two years ago was used.

The ACR Practice Parameter for Communication of Diagnostic Imaging Findings calls for comparison with relevant prior examinations and reports “when appropriate and available.” The RSNA quality initiative on prior comparison utilization tracks whether reports document the date and type of a relevant prior comparison as a distinct quality metric.

When a comparison date is wrong or missing, the clinical foundation of the interval assessment is missing too.

What kinds of comparison date errors reach clients?

The most common types fall into three categories.

Wrong prior cited. The report references a different exam date than the study actually used for comparison. This happens when the radiologist pulls the prior manually and notes the date from memory, or when the prior search surfaces multiple studies and the wrong one is selected.

Missing comparison. The report contains interval language such as “no significant change” or “decreased in size” without documenting which prior was used. Clinicians and quality reviewers who later read the report have no way to evaluate the claim.

Comparison date mismatch. The date in the comparison section does not correspond to any study in the patient’s imaging history. This can result from a transcription error, a system display issue, or a wrong patient’s study being surfaced.

Each of these is a documentation failure that peer review will catch only occasionally, because retrospective review operates on a sample. As discussed in the comparison between radiology peer review and automated QA, sample based retrospective review was not designed to prevent routine documentation errors at scale.

How do comparison date errors happen in a busy teleradiology operation?

In a manually managed workflow, the radiologist or a coordinator locates the prior study through the PACS or an external viewer. That search depends on study descriptions, patient identifiers, and system interfaces that vary by client site. Overnight, when system support is reduced and study volume is high, the conditions are exactly right for a prior to be misidentified or skipped.

The specific failure modes are predictable:

• The worklist does not surface a relevant prior automatically, so the radiologist searches manually and uses the first result that appears.
• Multiple prior studies exist and the most recent is not the clinically relevant one, but there is no prompt to review which comparison is appropriate.
• A prior study is available in a different system (an outside facility or an older PACS archive) and is never retrieved because the current interface does not surface it.
• The radiologist notes the date of the prior they recall reviewing but does not confirm it against the study metadata.

None of these are failures of clinical judgment. They are workflow gaps that a well designed system can address before the report is drafted.

What does the standard of care say about comparison documentation?

The ACR expectation is clear in principle: comparison with relevant priors is part of the radiologic consultation where appropriate and available. Legal precedent reinforces this. In cases where a radiologist failed to compare a current chest study with prior films, plaintiff experts have characterized the failure as a breach of the standard of care. The ACR communication standard calls for comparison with relevant prior examinations and reports “when appropriate and available,” and that phrase has been examined closely in malpractice proceedings.

The RSNA quality improvement initiative goes further, measuring compliance as a distinct metric: whether each report documents the date and type of the prior study used for comparison and whether any interval change was noted.

For teleradiology groups serving multiple clients, this is not a theoretical standard. It is a measurable expectation that appears in quality reviews and, when it fails at volume, in client feedback.

How does automated prior retrieval address the upstream problem?

The most direct response to comparison date errors is to solve the prior retrieval problem before the radiologist begins reporting. If the right comparison study is already identified and summarized when the radiologist opens the case, the conditions for a comparison date error are mostly removed.

Automated prior retrieval pulls the clinically relevant prior study and summarizes the prior report before reading begins. The radiologist does not search. The right prior is present. The comparison date in the report corresponds to the study that was used, because that study is the one that was surfaced.

SkiaManager’s auto comparison fetch handles this step: the right prior study surfaces automatically, so there is no manual search and no opportunity for a date to drift from what was actually reviewed. That same automated context is part of a broader radiology workflow automation layer that handles the coordination steps around reporting so reading staff focus on interpretation rather than administration.

Automated retrieval does not eliminate all comparison date errors. A radiologist can still override the surfaced prior or work from a study the system did not surface. But it removes the most common failure category by handling retrieval reliably rather than leaving it to manual effort under time pressure.

How does pre submission QA catch comparison errors before they leave?

Even with automated prior retrieval, some comparison date errors will reach the submission stage. A second protection layer is needed: a check that runs at submission, before the report reaches the client.

Pre submission QA reviews the comparison documentation in the report and flags inconsistencies while the case is still open. Specific checks include:

• Is a comparison date documented for a study where a prior is expected?
• Does the cited date correspond to a study that exists in the patient’s history?
• Does the body of the report reference interval change without documenting which prior was used?

These checks run in seconds at submit time. If there is a problem, the radiologist sees it immediately and can resolve it before the report leaves. This is what SkiaQA does for comparison dates: it reviews every report at submission rather than sampling retrospectively.

The distinction from peer review matters here. A comparison date error caught by pre submission QA is fixed before the report reaches the client. The same error caught by retrospective peer review, a week or a month later, may be logged and discussed but does not change what the client originally received. The broader overview of common radiology report errors shows where comparison errors sit relative to other documentation failures.

Does fixing prior retrieval also affect turnaround time?

Yes, indirectly. The time a radiologist spends searching for a prior study is time not spent interpreting the case. In an overnight teleradiology operation running at volume, the manual prior search step multiplies across every serial scan in the worklist.

Automated prior retrieval removes that step. The radiologist opens the case with clinical context already in place. That changes the workflow at the start of each read rather than at the end, which means the time savings compound across the queue rather than appearing as a single incremental gain.

For operations tracking turnaround time alongside quality metrics, the two goals reinforce each other. A correct comparison is also a faster comparison when prior retrieval is no longer manual.

How to evaluate your operation for comparison date risk

Four questions help identify whether comparison date errors are likely leaving your operation regularly.

Do radiologists search for priors manually? Manual prior search creates the conditions for comparison date errors. The more manual the process, the more variable the result.

What percentage of your serial studies have a prior documented correctly? A quality audit that tracks this specifically will tell you quickly whether the problem is systematic or isolated. Most operations do not track it at this granularity, which is why the failures remain invisible until a client calls.

How does your QA process catch documentation errors? If the answer is retrospective peer review, the errors are being caught after delivery. Pre submission review catches them before.

What is your overnight prior retrieval process? Overnight is when volume, reduced support, and time pressure combine to create the highest risk. If the overnight process is manual, the error rate overnight is likely higher than the daytime rate.

These are not trick questions. Most radiology operations manage comparison documentation as a secondary concern relative to diagnostic interpretation. Treating it as a trackable, preventable error category changes the outcome.

Frequently asked questions

What is a comparison date in a radiology report?

A comparison date is the date of the prior imaging study the radiologist used to compare the current exam against. It tells clinicians and quality reviewers exactly which prior baseline the interval assessment was made from, and it is part of standard radiology documentation where a relevant prior exists.

How common are comparison date errors in radiology reports?

No large scale study has measured comparison date error rates in isolation. However, comparison with prior imaging is tracked as a quality metric by the RSNA, and documentation failures in this category appear consistently in radiology quality improvement audits. The errors are common enough that ACR practice parameters address comparison documentation directly.

Why do wrong comparison dates reach clients?

Most radiology QA programs are retrospective and sample based. They audit reports after delivery, and they sample rather than review every report. Comparison date errors that are not clinically dramatic are easy to miss in retrospective review and rarely trigger callbacks on their own, so they often go uncounted.

Can automated review catch comparison date errors?

Yes. Pre submission QA that reviews every report at submit time can check whether comparison documentation is present, whether the cited date corresponds to a real prior in the patient’s history, and whether interval language in the report is consistent with the documented comparison. SkiaQA checks for comparison date consistency on every report before submission.

Does comparison documentation matter for malpractice?

It can. Failure to compare with prior imaging when a prior was available has been raised as a breach of the standard of care in radiology malpractice cases. The clinical argument is that a different comparison (or a comparison that was conducted) might have changed the interpretation and the course of treatment.

If you want to see how comparison date checking fits into a pre submission quality layer across your whole operation, book a demo and we will walk through how SkiaQA and SkiaManager work together on this.