Clinical Research Data Entry: Why Form Layout Changes Accuracy

At a glance

Preserve useful relationships

When the data source already contains meaningful relationships, the form can preserve them instead of asking the person to translate or reconstruct them.

Reduce mental mapping

Every unnecessary translation, lookup, or relationship someone has to remember adds work before the value reaches the field. That work can also create errors that ordinary validation may never detect.

Design for the work, not just the data

Two forms can collect exactly the same fields while requiring very different amounts of work. A good data structure does not automatically make a good data-entry form.

Quick, imagine knowing nothing about corneal staining (okay, check 😊), and you've been tasked with rating eye disease severity.

Now look at the two forms below. Which one would you rather use to rate the images?

Form A probably jumped out. And you didn't need to know a thing about corneal staining to pick it.

Your eyes made the decision before your fingers ever touched the form.

Keep in mind that both forms ask the same questions and collect the same ratings. But getting those ratings into the form is a very different experience. One makes the job considerably easier.

So what's going on? Turns out there's a lot more here than meets the eye.

Let's start with probably the most intuitive part of what's happening: spatial relationships. The source already has a shape. The staining appears in a particular location on an eye. The question is whether the form preserves that relationship or requires the person to reconstruct it.

When the Form Loses the Map

When we talk about accurate data entry, the discussion usually centers on what the fingers do: put values into fields.

The familiar techniques are worth knowing and using: skip and branching logic, showing or hiding fields, required fields, valid ranges, data type restrictions, input masks and formatting rules, cross-field consistency checks, and conditional validation rules.

All these matter. They help keep out-of-range values, missing responses, and contradictory answers from making their way into a dataset.

But notice where the attention is focused: on the data. Is the value present? Is it allowable? Is it formatted correctly? Does it agree with the values around it?

What's largely missing from that discussion is the work required to produce and enter it.

Form B is what happens when we primarily organize around the fields.

It's a logical layout. The locations run down the rows. Right and left eyes run across the columns. Ten fields. Compact. Organized. Easy to understand when you're thinking about the structure of the dataset.

But that organization comes at a cost for the person entering the data. Consider what happens when they see staining in the lower part of the left eye:

With Form B, the person has to translate what they see into Bottom, find the corresponding row, remember that the left eye is OS, move to the correct column, find the field, and enter the rating.

With Form A, the spatial relationship does much of that work for them.

Now do it again. And again. Ten times, for multiple participants and visits.

Some of that work is required by what we're trying to collect. The rater still must examine the eye and decide whether the staining is diffuse, localized, or not applicable. The form can't eliminate the judgment we're trying to collect.

But much of the remaining work is different. Translating where the staining appears into Bottom, finding the Bottom row, remembering that the left eye is OS, moving to the correct column, and locating the field don't help the rater judge the staining.

We created that work with the form.

Each step creates another opportunity for error before the value ever reaches the field. Get one of them wrong and the dataset says the disease was somewhere it wasn't.

The particularly troublesome part is that this type of error may not be caught by validation rules, because the value itself can be perfectly allowable while still recording the wrong observation. It may generate no warning, query, or even stand out during cleaning. Someone lost track during all that mental mapping, and the data simply record something other than what was observed.

This is a problem you can design out of the form.

Preserve What's Already There

Look at what happened to the source. The staining started as spatial information. Its location on the eye was part of the observation.

Form B does not preserve that spatial relationship. Instead, it asks the person to recreate it using labels, abbreviations, rows, and columns.

The observation started spatial. The form turned it into a lookup problem.

Form A does something much simpler. It preserves the structure that was already there.

The two circles correspond to the two eyes and appear in the same left-to-right order as the images above them. Each circle is divided into the same spatial regions the rater is examining.

Now the process collapses: see staining toward the bottom of the left eye, move to the bottom of the left diagram, enter the rating.

Less to translate. Less to remember. Less to search for.

Form B moves the work to the person. Form A moves the work into the design.

That's the value of spatial correspondence in this task. When location already carries meaning in the source, preserving that relationship in the form can eliminate mental mapping that has nothing to do with making the observation itself.

Anatomy is an obvious example. But the same question applies anywhere the source contains meaningful spatial information.

Space Isn't the Only Relationship

Spatial correspondence is one of the easiest places to see the principle, but space isn't the only relationship a source can give us.

•Position

A familiar EHR screen may consistently put a value in the same area. That location is already helping someone find it. A form doesn't have to reproduce the screen, but moving the value somewhere completely different may create unnecessary searching.

•Order

If a clinic note presents blood pressure followed by heart rate, preserving that order can keep someone from bouncing back and forth through the source.

•Spatial

An image, diagram, or the patient in front of you may carry left/right, upper/lower, anterior/posterior, quadrant, or regional relationships. Flattening those relationships into unrelated fields can force the person to reconstruct them mentally.

•Grouping

Systolic and diastolic pressure belong together. When the source groups related information, separating it on the form can break a relationship the person already sees.

•Hierarchy

A source may organize information as visit, then assessment, then measurement, or use headings and subheadings that tell the person where a value belongs.

•Emphasis

Weight, size, colour, or icons may direct attention to particular information. The goal isn't necessarily to copy the styling. It's to notice the work that styling is already doing.

•Patterns

Matrices, ordered response options, repeated structures, diagrams, and other patterns may help someone recognize where they are and what comes next.

Before reorganizing the source into fields, look at what the source is already doing to help the person understand and navigate the information.

None of this is an argument for copying the source. The source may be poorly designed. Two sites may present the same information in different ways. Some of its organization may have nothing to do with the research question, and reproducing it could carry someone else's problems into our form.

So the principle isn't match the source. It's this: look for useful relationships and cues in the source before reorganizing the information into fields.

Now Let's Make It Harder

It would be easy to finish here with a simple rule: If the source is spatial, make the form spatial.

Except that rule is wrong.

We've concentrated on one part of our framework: the source. What happens when we bring in the person?

Put it to work

• Look for correspondence worth preserving.

  Before designing the form, examine how the source organizes the information. Look for useful relationships in where information appears, what appears together, the order in which it appears, and the visual cues that help someone find and interpret it.

• Compare the source with the form.

  Where does the form preserve useful relationships, and where does it force the person to translate, reorder, search, remember, or reconstruct them?

• Follow one value all the way through.

  Pick a real observation and trace every step required to get it from the source into the correct field.

• Look for errors validation won't catch.

  Could someone enter an allowable value into the wrong location, field, side, row, or category without triggering a warning?

If the person has to reconstruct useful relationships that the source already gave you, look for a way to move that work into the form.