Clinical patterns

Capture & quality gate

When the person operating the device cannot interpret what it produces, they have exactly one safety judgement available to them: was the input good enough? This pattern is about making that judgement possible for someone with no clinical training — and about refusing to produce a finding when the answer is no.

Stable · v1.0 FieldGrade WCAG 2.2 AA IEC 62366-1

Overview

Everything else in this system assumes the reader can check the software's work. A clinician looks at the trace before the interpretation; if the machine is wrong, they see that it is wrong. That assumption is what makes evidence before conclusion a workable strategy at all.

Remove it and the safety architecture has to move. A screening operator in a high-street optometry practice cannot tell a healthy retina from a diseased one, and should not be asked to. What they can tell — with training that takes an afternoon rather than a decade — is whether the image is in focus, correctly framed, of the right eye, and free of the artefacts that make it uninterpretable. So that is where the safety judgement is placed, and the interface is built to support that judgement and no other.

Upstream, not downstream

This pattern is the operator-side, pre-analysis counterpart to out-of-scope disclosure, which is the reviewer-side, post-analysis version of the same instinct — withhold rather than extrapolate. The difference matters: by the time a confidence score exists, the bad input has already been analysed. The gate exists so that never happens.

It is also distinct from signal quality on the ECG review screen. That annotates quality for a reader who can already interpret the trace and lets them decide. Here there is no such reader, so the software decides.

Gate before analyse

Adequacy is settled before any analysis runs. A finding derived from an inadequate image is worse than no finding, because it looks like one.

Judged on the input

Every question the gate asks the operator is answerable without clinical knowledge. If it needs interpretation, it is the wrong question.

Ungradable is an answer

"We could not assess this" is a valid, complete, reportable outcome — never a degraded version of "nothing found".

Anatomy

Four fundus images per person — macula-centred and disc-centred, each eye. Each is gated individually, and the encounter is only as complete as its weakest field.

The gate sits between capture and analysis
Capture Quality gate Analyse Result issued
Quality gate Retake Refer to human grader

There is no path from a failed gate to a result. That is the whole design.

Per-field capture state
Capture · R. Adeyemi · NHS 449 812 3376 3 of 4 fields adequate
  • Right eye · macula-centred Adequate
    Focus, framing and illumination within limits
    09:14:02
  • Right eye · disc-centred Adequate
    Focus, framing and illumination within limits
    09:14:38
  • Left eye · macula-centred Adequate
    Focus, framing and illumination within limits
    09:15:20
  • Left eye · disc-centred Not adequate
    Optic disc not fully within frame. Ask the person to look at the fixation light and recapture.
    09:15:54
PartRule
Field identity Eye and field named in full on every item — left eye, disc-centred, never L-DC. Wrong-eye capture is this device's version of wrong-patient error, and abbreviation is where it starts. See Patient header.
Verdict Adequate or not adequate. Two states, no middle. "Borderline" is a category that exists to let throughput win an argument it should lose.
Reason Required on every failure, in operator language, naming the physical cause — not a score, not a code.
Instruction What to physically do differently. A reason without an instruction leaves the operator retaking the same inadequate image.
Exits Exactly two: recapture, or refer to a human grader. There is no third button and no way to proceed to analysis.
Completeness The encounter states how many fields passed. Three of four is not a complete screen, and the result must not be issued as though it were.

What the gate may ask

The constraint that shapes everything: every question must be answerable by someone who cannot interpret a retina. That rules out more than it sounds like it does.

The gate may judgeThe gate may not judge
Focus and sharpness Whether a lesion is present
Framing — is the required landmark within the field Whether an appearance is pathological or a normal variant
Illumination, over- and under-exposure Whether the finding is worse than last year
Artefact — eyelash, reflection, dust, smudge Whether the person needs treatment
Media opacity obscuring the view Why the media are opaque — that is a clinical question, and the referral exists so a clinician answers it
Laterality — is this the eye it claims to be Whether one eye's result can stand in for the other. It cannot.
The rule that carries the risk

A field that fails the gate produces no finding at all. Not a finding with a caveat, not a lowered confidence score, not "no referable disease detected — image quality limited". Every one of those is read as a negative result by the person receiving it, and the caveat is the part that does not survive being repeated at the front desk.

This is a governed behaviour. The gate has no sensitivity setting exposed to a deployment, no per-site threshold, and no operator override — because the pressure to loosen it is a throughput pressure, and throughput pressure is exactly what a safety gate exists to resist.

Ungradable is an answer

The strongest temptation in an autonomous screening device is to treat "could not assess" as a failure of the encounter rather than as its outcome. It is not a failure. A person whose media are too opaque to photograph has been given real, actionable information: this cannot be screened by camera, and you need to see someone who can examine you directly.

A complete, reportable outcome
Not assessable by camera — referred to a grader
Both left-eye fields were obscured after three capture attempts. This is not a result about the health of the eye: it means the photograph could not show enough of it, and a person will look at what was captured.
2 of 4 fields adequate · referred 09:22:41 · grader response expected within 5 working days

Note what is absent: no confidence score, no "probably normal", and no alarm colour. An ungradable image is a state, not a clinical priority — so it takes a neutral chip and never an IEC hue. See Colour.

Retake, refer, and the loop that must end

Recapture is the right first response and the wrong last one. Each attempt costs the person a flash, some discomfort and some goodwill, and after a few attempts the marginal image quality stops improving — the limit is the eye, not the operator.

AttemptWhat the interface does
First failure Names the physical cause and what to change. Recapture is the prominent action.
Second failure Same, plus the refer option raised to equal prominence. The operator is told this is normal and not their error.
Third failure Recapture stops being offered for that field. The encounter proceeds to referral. The decision is the system's, not the operator's, so that no one has to justify stopping.
Any point Refer is always available immediately. An operator who can see it is not going to work must never have to perform two more attempts to prove it.
Why the cap is the system's decision

Put the stopping decision on the operator and you have created a judgement call between "keep trying" and "send this person to a clinician", made by someone with no clinical training, under appointment-time pressure, with a queue in the waiting room. The cap removes the judgement. It is a smaller design than it looks and it is the reason the operator's afternoon of training is enough.

States

StateRendering
Capturing Field named before the shutter, not after. The operator confirms which eye they are about to photograph, not which one they just did.
Assessing Activity shown in place, with the field named. Never a full-screen block — the operator is mid-encounter with a person in the chair.
Adequate Neutral chip and a plain statement. No celebration, no green tick: passing the gate is the ordinary case and does not deserve emphasis.
Not adequate Quiet chip, physical cause, instruction, and the two exits.
Gate unavailable Capture is disabled. If adequacy cannot be assessed, images must not be taken and banked for later analysis — an unassessed image in a queue is an unscreened person who believes they were screened.
Encounter incomplete Named field by field. The person is never told "screening complete" while any field is outstanding.

Do's and don'ts

Do
Not assessable by camera
Referred to a grader. This is about the photograph, not about the health of your eye.

A complete outcome. It says what happened, what it does not mean, and what happens next.

Don't
No referable disease detected
Image quality was limited for some fields.

A negative result with a caveat attached. The headline is what gets repeated at the desk and remembered a year later; the second line is not.

Do
Left eye · disc-centred Not adequate
Optic disc not fully within frame. Ask the person to look at the fixation light and recapture.

Physical cause plus a physical instruction. The operator knows exactly what to change before the next attempt.

Don't
L-DC Q-score 0.41
Below threshold

A code, a number and a threshold. It tells an untrained operator nothing they can act on, and the abbreviated laterality invites a wrong-eye retake.

Do

Two exits, both legitimate. Neither is framed as giving up, and refer is available from the first failure onward.

Don't

An override. Every appointment running late will press it, and the gate has been converted into a suggestion.

Do

Both eyes required. Right eye adequate; left eye not assessable — left eye referred.

Laterality carried all the way to the outcome. One eye's result never speaks for the other.

Don't

Screening complete. No referable disease detected.

Issued on one adequate eye. The person now believes both eyes were examined, and will not come back for a year.

Accessibility

Outcomes of use

What this contributes to, in the terms of Usability & context of use. These are attributes believed to contribute to an outcome; the outcome itself is settled by observing real use in a specified context, not by this page.

Clinical safety notes

Risk controls carried by this pattern

Trace these in your risk file (ISO 14971) and usability engineering file (IEC 62366-1).

NotJustAnyMed.Tech Design System · Capture & quality gate · v1.0 · draft for review
Reference applications named in this system are fictional; all patient data and screening pathways shown are fabricated and illustrative.