Forms that keep their word

Every behavioral health agency changes its forms. A state requirement arrives, a payer wants one more question, a clinical director rewords an assessment so it reads the way the team actually talks. It’s routine work, and it’s some of the riskiest work an agency does, because every note already signed on that form is a legal record.

We asked Rodney what he sees go wrong, and how that shaped the forms designer in Vigil, a Knight Software platform and a behavioral health EHR built for Florida.

Custom forms come up a lot in your consulting and data work. Why?

“Because custom forms designers are often difficult to use, misleading, or not very well documented. And they try to do too much, when the basics are what matter most.

“What I see all the time in our Knight Data Services work: a form change is made, and the organization loses data. The structure underneath didn’t have guards to protect it. Someone takes a field away and loses data that was extremely valuable.

“Or it’s a communication problem. The change isn’t explained to everyone, so clinicians think they’re in the wrong form, or don’t know how to use the new questions.

“And auditors can end up finding signed notes that no longer reflect the note as it was on the day it was signed.”

Why does it keep happening?

“Forms design teams usually aren’t frontline clinical teams. They’re not the same people. So forms designers end up making forms for people who design forms, not for the clinicians, billing staff and leaders who have to live with them.

“Our own older forms designer had the usual problems: a big designer, tons of options, little documentation, little explanation of what each option did, and little room for testing and reuse. That left knowledge gaps.

“It’s a big part of why Vigil is so deliberately wordy in its documentation and its small on-screen explanations. That microcopy isn’t decoration. It tells you, quietly, what is about to happen to your data.”

The four basics

If a leader asked you what a forms designer simply has to get right, what would you say?

“Start with the foundational question types: drop-down list, radio button, checkbox, free text. That’s what you need to make a form. What you do with them makes all the difference:

1. Every answer is stored where you can report on it. A field that shows on the page but isn’t stored properly underneath is a field you can never report on. If a form isn’t reportable, there’s hardly any point in building it.
2. Versions. When a form changes in a way that matters, it gets a new version. For any note, you must be able to see which version it was written on, and the old versions must be kept. They have to be there.
3. A preview while you design. I think it’s the single biggest thing you can give a form builder: see what will come out while you’re building, so you aren’t going back and forth guessing.
4. A record of every change. What changed, who changed it, and when.

“Data linkage and conditional logic are great too. But if the core isn’t there, the nice-to-have features have no bones to stick to.”

In Vigil, the designer’s preview and service entry draw a form with the same code: what you see while designing is what clinicians get.

Wearing the auditor’s hat

In Vigil’s forms designer, a form locks only once a service is saved on it (not as a draft) or signed. On a form that’s in use you can still fix wording and help text, add new questions and choices, retire ones you no longer want, and set an End date. A bigger change, such as changing what kind of answer a question takes or what a choice means, is made on a new version, and the designer tells you so in plain words.

Where did you draw that line?

“We’re always walking the line between absolute audit integrity and being friendly to use. You have to be able to make small changes without making everyone publish a new version.

“But when what a field holds changes, anything that isn’t simply cosmetic, version control has to kick in right away. That’s when the auditor hat goes on.

“It protects agencies from not being able to answer the hard questions. When did you start tracking that on your intake form? When did you add the DLA-20 to your evaluation? Some things you have to be able to answer with absolute certainty.

“Cosmetic changes, we allow. A wording fix also shows on services already saved on that form, and that’s exactly why every change is recorded.”

A safety net, even from yourself

In Vigil, saved answers are never lost. A choice someone has already picked is retired, never deleted, and it still shows and prints on the services that answered it. Every change to a form is recorded: what it was, what it became, who changed it and when.

Who does that actually help?

“It isn’t punitive, and ‘transparency’ isn’t quite the right word either. It’s a buffer, a kind of confidence in your own work.

“Say someone asks, we’re not seeing child welfare data in our outcome forms anymore — what happened? We can find out exactly when that changed. Because fixing it isn’t just fixing the form. It’s picking up the data that fell along the way.

“Real life happens. The audit trail is a safety net, even from yourself.”

“You can’t prevent every mistake, because we’re human. The audit trail is a guiding light for picking up the pieces when it does.”

And the reason behind a change?

“The why matters, because it can shed light in ways you wouldn’t expect. Say a question disappeared from an evaluation, and it seems easy to just add it back. But if you know why it was removed — say the team had built a separate form that already asks it, and didn’t want clinicians entering the same thing twice — then you know the removal was a success, not a mistake. Without the why, it’s easy to undo good work in a vacuum.

“Knowledge sharing, microcopy, a deep audit trail. Those three go together.”

Vigil records what changed, who changed it and when. The why is worth writing down with your team, every time.

Three questions for any forms designer demo

If a behavioral health leader is watching a vendor demo next week, what should they ask?

“If the answers are vague, your data is the thing at risk.”