Assemble a Cited Data Package for Review at a Health System

A medical director asks you for a data package before a pharmacy and therapeutics committee meeting, and the request sounds simple. Pull the studies, format the citations, done by Friday. But underneath that ask sits a harder problem. The director wants something that reads like a clear recommendation. Your job description and your company's promotional rules only let you organize evidence and describe what it says, not tell a committee what to conclude. If you do not manage this conversation deliberately, you either hand over a package that looks like advocacy or you hand over something so hedged that the pharmacist reviewing it cannot find the answer to the question the committee actually has.

Why this conversation goes wrong

Most MSLs run into trouble here for one of two reasons. The first is speed. A committee meeting date gets set, someone remembers late that they need supporting literature, and the medical director calls you with two days on the clock. Under that pressure it is tempting to send whatever slide deck or literature summary you already have on file rather than build something matched to what this specific committee needs. The second reason is scope. The director may ask a question that sits outside standard medical information territory, something closer to an off label discussion or a request for your personal read on which drug performs better. Answering that directly, even informally, creates exposure for you and your company. The fix for both problems is the same. Slow the request down for thirty seconds before you agree to anything, and find out exactly what the committee needs and how it plans to use what you send.

How to prepare before you say yes

Before you commit to a deadline, get clear answers on four things. First, ask which evidence domains the committee cares about, efficacy data, safety data, cost data, or comparative data, since a broad request usually means someone has not narrowed the question yet. Second, ask what citation format and level of detail the reviewers expect, because a pharmacist doing a formulary review wants methodology, sample size, and endpoint definitions, while a physician on the committee might only need the summary and reference list. Third, confirm the real deadline, not the one someone assumes, and ask when the committee packet actually closes for submissions. Fourth, check whether any part of the request drifts into territory that needs a different process, such as an unsolicited request for off label data or a question that only your medical information team can answer through its formal channel. Route that piece separately and keep it out of the package you assemble yourself.

Once you know the scope, pull only approved, balanced materials. Include the study limitations next to each finding, not buried in an appendix nobody opens. If the evidence has a gap on a question the committee is likely to ask, say so in the package rather than letting a pharmacist find the gap during the meeting and question everything else you sent.

What to say when the director pushes for a conclusion

The moment that trips people up is when the director asks you to just tell them what the data shows. Handle it directly instead of dodging it. The director says, "Can you just give us the bottom line on this therapy. What should we conclude." You reply, "I can build a cited package and walk the committee through the study designs and what each one reported. I want the committee to reach its own conclusion once it sees the full context, including where the evidence is thin. Which parts of this will the pharmacist scrutinize most closely." The director says the committee is mainly worried about how the studies defined their patient populations and their endpoints, since that is where a prior formulary review got stuck. You tell them you will organize the package around those two sections first and flag every place the endpoint definitions differ between studies. The director then asks for your honest opinion on whether the drug deserves formulary placement. You say, "That call belongs to the committee once it has seen the evidence. What I can tell you is where the data is strong and where it is not, and I can make sure every claim in the package points back to a labeled source."

That exchange does three things. It answers the request instead of stonewalling it. It draws a clear line around what you will and will not say. And it uses the director's answer to make the package more useful, because now you know exactly which sections need the most detail.

Mistakes to avoid

A few habits turn a good package into a liability. Sending an internal marketing deck instead of primary literature is the most common one, since it reads as promotional even when nobody intended it that way. Leaving out a negative or neutral finding because it complicates the story is worse, since a pharmacist who finds it later will question everything else in the package. Skipping the study limitations because they slow down the narrative removes the exact detail the committee needs to weigh the evidence correctly. And answering a scope question yourself instead of routing it through the right channel, especially anything that touches an off label use, puts you outside your role and outside the guardrails your company set up for a reason. If you are unsure whether a question needs that separate path, Guide an Independent Research Inquiry to the Right Process covers how to sort a request like that before you respond.

How to practice and score this

Have a colleague or your manager play the medical director and push you toward a conclusion at least twice during a mock run, since that is where most people cave under repeated pressure rather than on the first ask. Score the run on four things. Did you ask enough clarifying questions before agreeing to a scope. Did you hold the line on describing evidence instead of endorsing a conclusion, even on the second and third push. Did you route any off label or specialized question to the right process instead of answering it yourself. And did the resulting package, when someone reads it as a skeptical reviewer, show a source for every claim and a clear label on every limitation. If you want a structured way to rehearse the whole exchange, including the harder version where the director gets frustrated with your hedging, Pharmaceuticals practice conversations covers this scenario alongside related situations MSLs run into with health systems. DealSpeak's scored practice sessions let you run this conversation enough times that the boundary between organizing evidence and offering a conclusion becomes automatic instead of something you have to think through live. A related skill worth practicing alongside this one is Take an Investigator's Scientific Question Intakesince it uses the same instinct to separate a scientific question from a request that needs a different process.

What you gain

Get this conversation right and the committee gets a package it can actually trust, because every claim traces back to a source and every gap is named instead of hidden. That is worth more to your credibility with that health system than a fast answer that reads like a sales pitch.