Route an Unsolicited Scientific Question With Care

A physician catches you after a session and asks about a use of your product that never appeared on the approved label. Nothing about your training prepares you for the pause that follows. As a Medical Science Liaison, you cannot answer from a promotional instinct, and you cannot pretend you did not hear the question. You need a process that captures what the clinician actually wants to know, keeps the exchange scientific rather than promotional, and gets them a response built on evidence. Handle this poorly and you either drift into promoting an unapproved use or you leave a physician with a real patient care question and nothing useful in hand.

Why This Conversation Goes Wrong

Most MSLs know the rule in the abstract. Document the unsolicited question, route it through medical information, do not offer a personal opinion on an unapproved use. The trouble starts when the question shows up live, in a hallway or after a formal presentation, and the physician expects an answer right then. Silence feels unhelpful. Improvising feels natural. Both instincts push you toward saying more than you should.

A second failure mode shows up when you assume you already know what the physician wants. They mention a use outside the label, and you jump straight to citing a mechanism or a trial you remember, without confirming what kind of evidence they are actually asking for. You might be a few sentences into an answer before you realize you have skipped the intake step entirely.

A third problem is patient detail. Physicians describe real cases because that is how clinicians think. If a name, a diagnosis detail, or an identifying combination of facts slips into the conversation, you now have a privacy problem stacked on top of a compliance one. None of this makes the conversation adversarial. The physician is not trying to trap you. They have a patient in front of them and a question they think you can answer. Your job is to take the question seriously while keeping the process intact.

How to Prepare Before the Question Lands

You will not have time to think this through in the moment, so decide your approach before you are standing in front of someone. Know your organization's process for unsolicited requests cold, including who receives the request, what response the requester should expect, and roughly how long that response takes. Vague answers about the process erode trust fast.

Know the difference between the evidence types a physician might ask for. Some want published literature. Some want detail on study methods or population. Some want a broader scientific perspective that goes beyond a single paper. Have a short, natural way to ask which one they want, so you are not guessing.

Build a habit around patient details too. Decide in advance how you will redirect a story that starts naming specifics, so the pivot to a general question sounds like normal conversation rather than a compliance reflex. And have a simple way to capture the topic on the spot, even if it is just a note on your phone right after the exchange, so the details do not depend on memory later.

What to Say When the Question Comes

A physician says, "I want to ask about using this outside what is on the label."

You respond, "I can log this as an unsolicited scientific question and set up a proper follow up on it. Can you tell me what you are hoping to see, without naming the patient?"

The physician says, "I want to look at the published literature on that use."

You reply, "Understood. I will note that you are asking for published literature on this specific use. I cannot get into that here, but I will submit the request through our medical information channel and come back to you with a separate scientific discussion once I have the material pulled together."

If the physician pushes for a quick opinion in the moment, hold the line without sounding defensive. Something like, "I know you want a sense of this now, but I want you to have the full picture from the right source rather than my recollection of it. I will move quickly on getting you the real material." That keeps the tone collaborative. You are not refusing to help. You are making sure the help is accurate and traceable.

Mistakes That Undermine the Response

Answering from memory instead of routing the question is the most common mistake, and it usually comes from good intentions. You want to be useful in the moment, so you offer a partial recollection of a study. That partial answer can shape a treatment decision without the physician ever seeing the actual data.

Letting patient identifiers sit in your documentation is another one. Even a first name and a rare diagnosis combination can be enough to identify someone. Strip that detail before you write anything down, not after.

Promising a specific timeline you do not control causes its own problems. If you tell a physician they will hear back in two days and the internal process takes longer, you have created a new complaint that has nothing to do with the original question.

Editorializing about the evidence is a subtler mistake. Even a phrase like "I think you will find this promising" nudges the physician toward a conclusion before they have seen the source material. Stick to describing the process, not the expected outcome.

Finally, do not let the redirect sound like a brush off. A flat "I cannot discuss that" without an explanation of what happens next reads as evasive. Physicians respond well to a clear next step. They respond badly to a wall.

How to Practice and Score This Conversation

This is a conversation that improves with repetition, because the pressure to improvise never fully goes away, it just gets easier to resist. Ask your manager to roleplay a physician who is impatient, one who tries to slip in patient details, and one who pushes back on the redirect. Each version tests a different part of your discipline.

Score the practice on a few concrete points. Did you confirm the evidence type the physician wanted before saying anything else. Did you catch and redirect any patient identifying detail. Did you document the topic and the requested source without adding your own interpretation. Did you name a real next step instead of a vague promise.

DealSpeak gives you a way to run this scenario repeatedly against an AI counterpart that varies the pressure each time, then scores how you handled the intake, the redirect, and the documentation. That repetition matters more here than in most conversations, because the failure mode is quiet. You will not always know you crossed a line until someone reviews your notes later.

If your work also touches patient support conversations, the piece on how to Prepare Clinic Staff for an Authorization Expiry Workflow covers a related situation where staff need a calm, structured redirect under time pressure. Office based colleagues handling coverage questions may also find Clarify a Benefits Verification Question for Office Staff useful for the same reason, since it walks through another version of confirming what someone actually needs before responding. You can find more scenarios built for your role in the Pharmaceuticals practice conversations collection.

An unsolicited scientific question is not an interruption to your job, it is a routine part of it. Treat the intake as seriously as the answer itself, and the physician gets a response they can trust, built on evidence rather than your recollection of it.