Providing the Right Evidence Source for a Clinical Review

A research coordinator emails you the night before an internal committee review. She needs the source behind a training statement your team gave months earlier, and she needs it in the exact form the committee will accept. You know the material well. You also sense that the coordinator is under pressure and might want you to say more than the evidence actually supports. This is a common trap for clinical specialists. Handle it well, and you give the coordinator exactly what she needs and nothing she can misuse. Handle it badly, and your name ends up behind a claim your company never approved.

Why This Conversation Goes Wrong

The problem rarely starts with bad intent. It starts with a deadline and a gap between what a document supports and what a coordinator hopes it says. She is preparing a committee packet, she remembers a training slide that sounded encouraging, and she wants confirmation that reads as certainty. You want to be responsive and helpful, especially to someone you work with often. That instinct pushes you toward filling in gaps from memory, softening a qualified statement, or agreeing that a piece of evidence "shows" something it only supports in a limited way.

The stakes are higher than a casual conversation because this material is heading into an official review record. Once a claim gets written down as fact, it tends to stay that way, and correcting it later is harder than getting it right the first time. A clinical specialist who blurs supporting evidence with proof of outcomes creates a problem that outlives the phone call or the email thread.

How to Prepare

Before you respond, get specific about what you are being asked for and what you are allowed to give.

1. Ask which exact statement the committee is reviewing. Coordinators sometimes describe a claim from memory, and the wording matters more than they realize.
2. Locate the approved version of the source document and confirm it is current. Training materials get revised, and an older version can carry different qualifiers or a different citation.
3. Know your organization's channel for scientific or medical information requests that go beyond your role. If a question about outcomes requires a clinical or medical affairs specialist, you need to know how to route it before the conversation starts, not while you are typing a reply.
4. Separate what the document supports from what the coordinator wants it to mean. A study that shows a device performs consistently in a lab setting is not the same as a promise that a customer's outcomes will improve.
5. Confirm the delivery channel the coordinator is permitted to use for this material, whether that is a secure portal, a formal information request, or another approved route.

This preparation takes a few minutes and prevents the far longer cleanup that follows a misquoted source in a committee record.

What to Say

Suppose the coordinator writes, "Can you just summarize this as proof that our outcomes will improve? The committee meets tomorrow and I need something clean."

You respond, "I can send you the approved source behind that statement, along with its citation, for the committee's review. I cannot describe it as proof that your organization's outcomes will improve, because the document does not support that claim. Can you send me the exact slide or wording you are working from? I will confirm the approved source or route this to the right scientific information contact if it needs one."

She might push back, "I don't have time to go back and forth with another department. Can't you just tell me it supports our results?"

You hold the line without making her feel dismissed. "I understand the timing is tight, and I want to get you something you can actually use in front of the committee. What I can do right now is pull the approved document and its exact wording, so you have accurate material in hand today. If the committee needs a statement about your specific outcomes, that has to come from someone authorized to make that claim, and I can get that request moving as soon as you send me the wording."

This keeps the relationship intact. You are not refusing to help. You are giving her something more useful than a vague reassurance, an accurate source she can defend if anyone on the committee asks a follow up question.

Mistakes to Avoid

A few habits turn this conversation into a liability.

1. Do not paraphrase the source from memory. Pull the actual approved document every time, even when you are confident you remember it correctly.
2. Do not send whatever version is easiest to find. Check that it is the current approved version before it goes anywhere near a committee packet.
3. Do not agree to reword a slide or statement to make it sound stronger. If the coordinator asks you to help "tighten up the language," treat that as a request to change a claim, not a request for editing help.
4. Do not answer questions about outcomes or efficacy if that call belongs to an authorized specialist. Saying "I'll just note this for context" is how unauthorized claims slip into official records.
5. Do not let the deadline decide the accuracy of your answer. A rushed but correct answer protects both of you. A rushed but generous answer creates a record neither of you can defend later.

How to Practice and Score It

This is a conversation worth rehearsing before it happens for real, because the pressure to soften your answer is strongest in the moment, not when you are planning ahead. A manager can run this as a short roleplay, playing a coordinator who pushes for a stronger statement and watching whether you hold the line while still sounding cooperative. Score the exchange on three things. Did you identify the exact statement and source before responding. Did you avoid characterizing the evidence as proof of an outcome. Did you route anything outside your authority to the right channel instead of answering it yourself.

DealSpeak lets you rehearse this exact scenario against an AI coordinator who reacts the way a real one would, including pushing back when you decline to go further than the evidence allows. You can find this exercise along with other Medical Devices practice conversations built around situations clinical specialists face regularly. Two related conversations are worth pairing with this one. Addressing a Device Orientation Gap for Float Staff covers a different kind of pressure, where staff need training support fast, and Making a Clean Clinical Education Handoff to the Unit Educator covers how to hand off responsibility clearly instead of letting it blur, which is the same skill you are using here with the coordinator.

Getting this conversation right protects the coordinator's committee submission and protects you from being quoted as the source of a claim you never made. Practice it once with a colleague or through a rehearsal tool, and the real version becomes far easier to handle under a deadline.