Chapter 5: Put a person between the form and the participant¶
In this chapter you will learn to:
- Describe what a clinical research coordinator does and why participants stay because of one.
- Plan a first contact with a participant whose record needs follow-up.
- Log an interaction so that someone else could pick up where you left off.
- Build a place for unsolicited information into the protocol.
Case study: A Coffee Shop With No One at the Counter¶
As a rare disease mom I have had to work with a lot of organizations over the years: doctors, therapists, schools, the state, supports coordinators, medical supports of every kind. It is daunting. It is almost always a lot of paperwork, a lot of redundant questions, and some homework for me, and it is very much like participating in a study. But a few of those people were so sincerely interested in me, let me talk, let me vent, and asked me about the things nobody else cared about, that I looked forward to the meetings and to doing the paperwork for them. That taught me how good research is conducted, especially a longitudinal study that will reach out again and again. The relationships are the study.
Why wouldn't they be? If you ran a coffee shop, you would not put the coffee on the counter, leave a jar for the money, and walk away. Some people would not pay. Some would walk in, find nobody there, decide it was strange, and leave. You would have a friendly barista who greets people, asks how their day went, asks about the dog, offers something new to try. People come back because they have a relationship with someone, and maybe because they want to see what the barista's hair looks like this week. Everyone understands this intuitively. It always surprises me how often it is forgotten the moment someone has to run a study. People are intimidated by research, assume their common sense no longer applies, and build the equivalent of an unattended coffee shop: a link to a registry, a couple of emails, no one to greet you, no one to ask whether there are peanuts in the baked goods and no label saying so. A store run the way many registries are run would close within the year. Everything you would need to sell a cup of coffee applies here, and in a community this rare, with families who have every reason not to buy, it applies more.
Lessons for registry leaders¶
Families give a registry the same kind of repeated effort that care coordination asks of them. The people whose paperwork I looked forward to were sincerely interested in my family, and a coordinator who works that way is the reason participants come back. An automated reminder can support that relationship; it cannot replace it.
The rules¶
- The measure of success is that the coordinator is seen as a kind helper, a representative of your organization who is first and sincerely interested in the lives of the participants, and someone participants look forward to hearing from. Sincerity cannot be scripted, so hire or appoint for it.
- Name the clinical research coordinator role in writing, even when the founder holds it. In patient-led registries it is often done unnamed and unpaid, and naming it is the first step toward resourcing it.
- The coordinator is the person at the counter: screens, consents, confirms the diagnosis, chases the report, raises the query, sends the reminder and the second reminder, and makes the call.
- Let people talk. The question after the questions, how are you doing and how is everyone at home, is part of the job, not a distraction from it, and it is where the things nobody else asks about get said.
- Label the allergens on everything in the pastry case. A coffee shop labels what is in each pastry so that a customer with a nut allergy does not have to ask, and keeps someone at the counter for the question the label does not answer. A registry does the same: answer the questions a participant will have before they ask them (what this is for, who will see it, how long it takes, how to stop), and have a person reachable when the answer is not on the page.
- Log every interaction with a participant, with a date and what was decided.
- Build a place for unsolicited information into the protocol, and have the IRB approve it. End every contact with an open-ended question, such as "Is there anything else you would like to share with us today that we missed?", and record the answer as the IRB allows: in notes, a summary, a transcript, or a recording. That turns the first conversation with a coordinator, and every check-in after it, into research data. Some of the most useful information I have heard came out in conversation, about things no one had thought to ask in a structured way.
- Budget for the role. A registry with no one in this seat is a self-service counter with a jar for the money, and the people you most need will walk back out.
- If the coordinator and the data manager are the same person, record which hat they are wearing for each task.
- A data scientist joining the registry shadows the coordinator before opening the data.
What AI can do, and what only a person can do¶
What AI can do¶
Draft reminder text, call scripts, and interaction-log templates.
What only a person can do¶
Hold the relationship, hear what a family says between the questions, and be accountable for consent.
Take-home¶
A registry is customer service for people with every reason not to buy; the coordinator is the person at the counter, data exist because that person made the call, and no tool can stand there instead.
Practice¶
Exercise¶
In the synthetic Lantern Registry export, participant LR-003 is listed with a self-reported diagnosis and a variant recorded only as "positive."
- Plan the coordinator's call to the family. What is its purpose? What will you ask for, and how will you explain why? How will you make the call feel like help rather than paperwork?
- End the plan with the open-ended question: "Is there anything else you would like to share with us today that we missed?"
- Record the call in the coordinator interaction log as if it had happened.
Check your work
A strong plan thanks the family first, explains that a copy of the genetic laboratory report lets a qualified reviewer confirm the diagnosis so the family's data count fully in analyses, offers to walk them through uploading it, and asks how things are going at home before closing with the open-ended question.
An example log entry, with invented details for practice:
| Date | Participant | Contact | Purpose | What was decided | Unsolicited information | Follow-up |
|---|---|---|---|---|---|---|
| 2044-03-18 | LR-003 | Phone, 20 minutes | Request genetic report for confirmation | Parent will upload the report; coordinator to send instructions by email | Parent mentioned a new medication started last month; query raised on the meds field |
Check for upload in two weeks |
Your workbook page¶
The Coordinator interaction log page of the Slow Registry Workbook applies this chapter to your own registry. Fill it in online or print it and work by hand. The AI prompt library has a prompt for this chapter's topic, paired with the step only a person can do.
Check your understanding¶
What is the measure of success for a registry coordinator?
That participants see the coordinator as a kind helper who is sincerely interested in their lives, and look forward to hearing from them.
Why build a place for unsolicited information into the protocol?
Some of the most useful information comes out in conversation, about things no one thought to ask in a structured way. With IRB approval, an open-ended question at every contact and a way to record the answers turn those conversations into research data.
Up next: The coordinator makes the data exist; the registry also needs people who know what to do with the data once they exist, and few groups have named those people. Continue to Chapter 6.