Common Esterman interpretation traps in driving assessment

A high Esterman score can be reassuring, but it is not the rule. A field with scattered misses and a field with a connected central cluster can have similar totals but very different implications.

The clinician should look at where the misses are, whether they join, whether they approach fixation, and whether they form a neurological pattern. This is the difference between counting dots and interpreting a field.

DRIVE Fields helps by making cluster and extent logic explicit, but the habit still begins with the clinician reading the printout carefully.

If a printout is entered onto the wrong grid, the calculation can become precise and wrong. The central zone, adjoining relationships, and horizontal extent can all shift.

This matters most for non-Humphrey pathways, custom outputs, or printouts that are labelled as driving fields but use a native device layout. The safest practice is to select the source and layout that match the printout, or choose manual review if the match is uncertain.

Teaching point: do not let the app make an unsupported printout look more certain than it is.

Reliability is sometimes treated as administrative detail because clinicians are focused on the field image. For driving assessment, that is backwards. An unreliable field cannot support a confident favourable opinion.

False positives, fixation monitoring, patient instruction, fatigue, lens artefact, and printout readability all influence reliability. A threshold breach is easy to spot, but softer reliability concerns also deserve clinical judgement.

If the field is high stakes or borderline, repeat testing is often easier to defend than forced interpretation.

Austroads allows certain small meridian-related defects to be disregarded for horizontal extent. This does not mean missed points become seen points or that every meridian miss is harmless.

The concession applies to specific patterns: a single cluster of up to three adjoining missed points on or across the horizontal meridian, or a single-point-wide vertical defect that touches or cuts through the meridian, when unattached to other defects.

Those points may still matter for central loss or pattern interpretation. They should not disappear from the clinician mind.

A 108-degree field in a longstanding stable private driver is not the same clinical scenario as 108 degrees in a new stroke, progressive glaucoma, or commercial driver. The number is only one part of the assessment.

Borderline results should trigger context: duration, progression, adaptation, driving task, distance, history, reliability, and authority requirements.

This is where a structured report is better than a binary verdict. It can explain why a result may support conditional consideration, or why manual review is safer.

DRIVE Fields can apply deterministic rules to entered data. It cannot verify that the printout was selected correctly, that the patient fixated, that the authority will accept a particular device, or that the patient drives safely in real traffic.

The best wording keeps the boundary visible: this is clinician decision support based on the entered field and the original printout; the licensing authority decides the licence outcome.

That boundary is not a weakness. It is what makes the tool clinically credible.

The next reader may be the patient, another optometrist, an ophthalmology registrar, a medical review officer, or the licensing authority. If your report simply says "meets criteria" without explaining the source and limitations, you have made the result harder to audit.

Good uncertainty wording is not defensive. It tells the reader exactly what would strengthen or weaken the result: repeat reliable Esterman, clearer numeric printout, confirmed device layout, specialist review, or evidence that a longstanding defect is stable.

A report that preserves uncertainty is often more useful than a report that sounds confident but depends on assumptions no one can later check.