Responding to a Health System’s Standardization Review
Keep a strategic conversation factual when a system is reviewing device standardization across sites.
A health system standardization review usually shows up as one line in a meeting or a short email from a value analysis committee, and it can feel like the account is already lost. The instinct is to defend the product right away, list every feature, or offer a discount before anyone has explained what the health system is actually deciding. That instinct causes more damage than the review itself does. The better move is to slow down, learn the scope of the decision, find out who owns it, and get clear on what information the committee actually wants. Only then do you provide materials, and only through channels the health system has approved.
Why this conversation goes wrong
Most account managers have never sat inside a standardization review, so they fill the gap with assumptions. They assume the committee has already picked criteria. They assume fewer suppliers means their product is the one getting cut. They assume a broad pitch about value or outcomes will change a decision that has not even reached the analysis stage yet. None of that is confirmed, and reacting as if it were tends to make the account manager look defensive rather than useful.
The second failure mode is just as common. Once an account manager hears there might be a clinical or scientific question buried in the review, they try to answer it on the spot, in a hallway conversation or a quick email, without routing it through medical affairs or regulatory approved channels. That puts the company at risk and puts the account manager in a position they are not equipped to defend if someone asks a follow up question they cannot support.
Both problems come from the same root cause, which is treating a fact finding conversation like a negotiation. A standardization review at this stage is not a negotiation. It is a data gathering exercise, and your job is to understand it before you respond to it.
How to prepare
Before you take the call, write down what you actually know and what you do not. Know your current footprint at the health system, meaning which sites use your product, under what contract terms, and when those terms expire. Know who else touches this account, including any colleagues who cover other sites in the same system, so the health system does not get inconsistent answers from different people on your team. If the system has gone through a merger recently, confirm your contact list is current before this conversation starts, since a review can stall for weeks if you are sending materials to someone who left the organization. The post on Verifying Account Contacts During a Health System Merger covers how to check this without guessing.
Know which materials your company has already approved for this kind of request, and know who signs off on anything that falls outside that set. If a clinical question comes up, know the name and contact information of the person on your side who owns clinical or scientific communication, so you can route the question there instead of answering it yourself. Write down three questions you plan to ask before you say anything about your product. Those questions are what turn this from a defensive conversation into an information gathering one.
What to say
Grace, a director at the health system, opens the call by saying, "We are looking at reducing the number of device suppliers we work with next year." Omar, the account manager, does not defend or explain. He says, "Thank you for telling me directly. Can you help me understand what decision is being considered, which sites would be affected, and who is leading the review on your side."
Grace answers that a value analysis committee is still gathering information and has not set criteria yet. Omar responds, "That is helpful to know. I want to make sure your committee has accurate, approved information to work from rather than piecing it together from different sources. Could we agree on what specific information the committee needs, and who on my side should send it to, so everything goes through one contact."
Grace mentions that the committee has some questions about outcomes data tied to one of the devices. Omar says, "I do not want to guess at an answer to a clinical question. Let me connect you with the person on our team who owns that data and can respond with something the committee can actually rely on. I will set that up this week." He does not try to answer the outcomes question himself, and he does not treat the mention of a possible supplier reduction as a decision already made.
Notice what Omar avoids in that exchange. He never argues that the review is unfair or premature. He never pitches. He asks about scope, timing, and ownership, and he treats the committee's own criteria as the frame for the rest of the conversation.
Mistakes to avoid
A few patterns show up over and over in these calls, and each one costs trust.
- Arguing with the premise of the review instead of asking about it. Telling a health system that a standardization review is unnecessary rarely lands well, since the decision to run the review was already made by someone above your contact.
- Treating an early stage review as a final decision. Committees gather information for weeks or months before anyone selects criteria, and reacting as if the outcome is set signals that you do not understand how these reviews actually work.
- Answering clinical or scientific questions yourself because you want to seem responsive. This is the fastest way to say something your company cannot support later, and it puts your contact in an awkward spot if the answer turns out to be wrong.
- Sending materials to whoever answers the phone instead of confirming the single point of contact for the review. Multiple people at the health system receiving different versions of the same information creates confusion that works against you.
- Promising a fast turnaround before you know what was actually requested. It is better to confirm the request in writing first and then commit to a date.
How to practice and score it
This kind of call is hard to get right the first time you face it for real, which is why rehearsal matters. Practice an opening where the health system contact raises a standardization or supplier reduction review, and force yourself to ask three questions before you say anything about your product, specifically the decision being considered, the sites in scope, and who owns the review. Record yourself or run the scenario with a manager playing the health system contact, then check your notes afterward for three things, the decision stage, the scope, and the named owner. If any of those three is missing after the call, your next outreach should close that gap before your team drafts any kind of response.
A manager scoring this conversation should watch for whether the account manager asked before positioning, whether they routed any clinical question to an approved resource instead of answering it directly, and whether they confirmed a single point of contact for follow up information. Medical Devices practice conversations on DealSpeak let you rehearse this exact scenario with an AI counterpart that plays the health system role and pushes back the way a real committee contact would, and you get scored against these same criteria. The related post on Reducing Repetitive Meetings in a Complex Device Account covers a related problem, which is keeping this kind of account organized once the review turns into a longer process with multiple stakeholders.
A standardization review is a test of discipline, not persuasion. The account managers who handle it well are the ones who ask before they explain, and who know exactly which materials and which people they are allowed to bring into the conversation. Get the scope, the owner, and the information request confirmed first, and the rest of the process gets much easier to manage.
Practice these next
Use local usage evidence and input from lab owners to understand uneven adoption without directing customer staff.
Create a clear approval path when an outside collaborator requests project information from a research institution.
Turn overdue actions into a focused governance agenda without assigning the customer’s internal owners.
Help a strategic account manager maintain clear ownership when two research groups combine.
Coordinate research, procurement, and support conversations around change dates owned by the customer.
Map local decision rights before coordinating a discussion about shared research tools.