Ep 10: How to Market RUO Products Without Triggering FDA Oversight

Transcript

Transcript

Former FDA compliance officer Josh Levin explains the regulatory minefield of marketing Research Use Only products. This conversation covers the exact language that triggers investigations, how to present data safely, and strategies for working with diagnostic customers without becoming a diagnostic company yourself.

Defining Research Use Only and FDA Intent

Jasmine Gruia-Gray [0:00]

Hey, welcome to a splice of Life Science marketing. I'm Jasmine Greer Gray, and as always, I'm joined by Matt Wilkinson. Hey, Matt, hi. So today, tracking what you can and can't say about Research Use Only products or sometimes that's abbreviated as r u O, and how to avoid tripping the FDA wires. Our guest today is Josh Levin. He has led post market work at FDA, CDRH for molecular and pathology devices, focusing on compliance around Ruo products and lab developed testing as well as working with firms on transitioning their CLIA quality systems to an FDA compliant system. He later drove quality system implementation at pgdx and diagnostics regulatory strategy at A, S, E, L, L and G, s, k, through iron line consulting, he now advises labs and diagnostics teams on regulatory strategy and QMS. Prior to FDA, Josh worked at research product firms for 10 years, including a stint as director of R and D at kpl. Matt, why don't you kick us off? Thank

Matt Wilkinson [1:26]

you so much. Now, Josh, Research Use Only sounds pretty simple, but in one minute, what does it actually mean, and how does the FDA determine a product's intended use in practice versus the sort of totality of claims and context, and not just considering this a disclaimer,

Joshua Levin [1:46]

sure. Well, thank you Matt and Jasmine for the opportunity to speak on this subject. So FDA views Research Use Only as almost a diagnostic product that's in the developmental stage. So you know that because the product is being developed, FDA understands that there might be kits that are being developed for the purposes of researchers to try and use in their research, but there's also an understanding that FDA quality system regulations don't apply at this stage, and the claims that companies can make around these products are very limited. Not sure. I completely answered your question, but happy to elaborate

Matt Wilkinson [2:26]

further. Thank you for that. Now that was that was

Required RUO Statements and Labeling

Jasmine Gruia-Gray [2:29]

really useful. So what specific Are you? Oh, statement has to appear where and does punctuation, capitalization matter for ads, data sheets and slide decks.

Joshua Levin [2:42]

Yeah, so there's a standard statement, which is defined in the FDA regulations. And there's, there's actually a very useful FDA guidance on this. And the statement, I don't remember exactly, but it's something about for Research Use Only, not for use in diagnostic procedures. And this is something that our UL company should have on their labeling, just to make it very clear that they're not promoting the product for diagnostic use.

Jasmine Gruia-Gray [3:06]

Yeah, I've often used this in companies where I've worked and seen it in many others, for example, on antibodies. On the label of the vial, it says Research Use Only, so that that sort of covers it, does it?

Joshua Levin [3:21]

Yes, I think we'll probably talk about how Research Use Only manufacturers tools. Manufacturers can work with their partners who might be using the product and diagnostic applications and and what firms can do to protect themselves against FDA inspection or oversight.

Permitted and Prohibited Claims

Matt Wilkinson [3:39]

I can't wait to get into that. But before we do, what can a manufacturer say and not say about a Research Use Only product? And maybe more importantly, is there a difference between written copy and verbal communications, or are you creating both of those treated exactly the same?

Joshua Levin [3:58]

That's a very good question, especially around the written and verbal communication. So So companies, tools companies, or research use products companies are allowed to talk about the analytical capabilities of their product. So to give you an example, I had a and that should be very transparent to the user. We had a company who we were investigating at FDA, where the company had a combined score of 80 different biomarkers, and they were claiming this was a Research Use Only tool. And we said, Okay, well, what are the 80 markers you need to disclose that to your to your customer, and what the analytical performance is on each of those? And because they were unwilling to do that, we said, this is not a research tool. You're marketing. This is a diagnostic because of that lack of transparency. So tools companies should be very transparent about the analytical performance of their product on the particular marker. So for example, if you have an antibody, you know, being able to show western blots or Elisa data or what have you on performance of that antibody.

Matt Wilkinson [4:57]

So that's really interesting. So you're allowed to talk about the analytical capabilities, and then it's up to the user to go that extra step if they want to use it for diagnostic purposes, they have to then do the proof in the lab developed test. And this is

Joshua Levin [5:10]

where the difference between written and verbal communication comes in handy. So written communication is what FDA is going to scrutinize, and website copy, for example, is probably the most accessible medium to FDA, and where companies tend to get tripped up a lot, because the website copy is often written by marketers. No, no offense, but there's, there's a bit of a desire to overstate what that product can do, and be happy to share some suggestions for how to imply a diagnostic claim and written labeling in verbal communication, you have a lot more flexibility, because the court has ruled, I don't remember the exact case, but there was a court ruling that FDA cannot regulate freedom of speech. So for example, if you have a salesperson saying something to the effect of, well, we we know customers are using this in diagnostics. We're not supposed to be marketing it for that purpose. But you know, you can do what you want with it. You know something that statement like that FDA, FDA can control what a salesperson says. That being said. However, I definitely recommend training your sales staff very closely that they don't cross that particular line and that. Again, I think statements like the one I mentioned are ways you can kind of get around saying what you want to say without actually saying

Matt Wilkinson [6:26]

it brilliant. And that's it. That's such a subtle distinction. And I love that free speech comes in even to a conversation about, Oh, you are brilliant, yeah.

Red Flag Words and Safe Alternatives

Jasmine Gruia-Gray [6:35]

So I'd love to go back to what you said earlier, about how what's written, particularly in very public information, like a website, can trip you up. What are some of the red flag words that you've seen in your experience? What is some safe praise phrasing? What kind of guidance would you give our audience?

Joshua Levin [6:57]

So let's say that you you had this antibody, and the antibody had a had a particular diagnostic use for, I don't know, let's say prostate cancer, just to make something up. If in your website copy, you were to say, our product is useful in the diagnosis, diagnosis of prostate cancer or something like that, that could trip you up, and FDA could say you're making an implied claim. But if you said something like this antibody has been shown to be a useful marker in prostate cancer, and then you list literature references, then you're not saying it's your product, you're just saying that this is what the scientists say. So FDA can't or will be less willing to call you on that, because you're not making a claim specifically about your product, but about this class of products and this particular biomarker

Jasmine Gruia-Gray [7:42]

can are there documents that can help researchers with this phrasing and with how to avoid making claims on diagnostic intent

Joshua Levin [7:54]

happy to use the opportunity to promote iron Line consulting services, where we certainly work with clients on on this issue, you know. And I'll give maybe another example that we worked on with the client where the clients marketing department wanted to claim that they were interference free for a particular interference this was a diagnostic company, but they hadn't performed the testing, so we recommended that they use the language of interference free by design, rather than simply interference free, because we didn't want to imply that they had done the testing. So that's an example of where we can work with clients. I don't think there's anything specifically written. Again, the Research Use Only guidance the FDA puts out as a good general guidance, but it doesn't necessarily talk about specific examples, promote the use of a good regulatory consultant, even for tools firms, to help avoid that particular issue, and it's usually something we can solve fairly quickly. That's that's

Presenting Analytical Data Safely

Matt Wilkinson [8:52]

got me thinking. I mean, I know the words can be interpreted in different ways, but so can data. So if I'm marketing an iuo product, I want to look at analytical performance and talk about some of, you know, some of the performance of, you know, the tool that I'm selling. I could imagine that even that data could actually imply clinical validity. So is there a way to ensure that you're framing that data in a way that isn't implying clinical or diagnostic validity, but it's actually just sort of showing this is the analytical performance

Joshua Levin [9:23]

of the product. Yes, certainly. And it you mentioned, Matt, it's a very subtle distinction. I think, if you're clear that you're you're testing, you're doing retrospective testing on pay, on patient samples, for example, like if you, if you're not implying that this is part of a clinical study. It's especially useful if it's someone else's data. If you have like a research collaborator, and then you're presenting that person's data, it can be a very subtle distinction. So you do want to make sure that the language really avoids any implication that it's a diagnostic tool. Let it start with the thought that this is a research tool and you're showing research. Research data's data in support of your research clients. I think you know, you'll, you'll be in good shape, if you kind of look at it that way. I think firms get into trouble where they try to, they try to be cute, and they know they have diagnostic customers. And you know, again, happy to get into how you might actually work with a diagnostic customer.

Matt Wilkinson [10:18]

I'd love to do that sort of just to dig into sort of something that made me think of there, which was, if I was to, you know, to have a product, you'd look at some retro, you know, retrospective samples. Then if I look at a correlation between, you know, the analytical capabilities of my tool and my test, and shall we say, the diagnosis of condition is that then implying that it can be used as a diagnosed, as a diagnostic, or am I actually just saying, In this study, we showed a great correlation between the analytical capabilities and diagnosis?

Joshua Levin [10:52]

I think that you do want to be careful there. I think saying if, again, if it's sort of like put in a research frame of mind that that we took patients with prostate cancer, we measured them, and, you know, our antibody showed that X percent had had this marker. As long as you're, you know, you're not, you're not going out and and implying with your data that people can then use this product directly for diagnosis. But kind of the goal of the study is a research goal, and that is, it's put in that context. I think that's kind of the mindset to have in mind. But it can be very subtle, because a lot of these tools, obviously are of interest for for diagnostic purposes as well. So

Application Notes and Case Studies

Jasmine Gruia-Gray [11:31]

as as you probably know, Josh, a very common tactic in the r, u, O space is to have application notes, case studies, whether it's from a key customer or a key opinion leader. Are there any guardrails around applying these, these success stories or these application notes and any disclaimers that that need to be included in the messaging,

Joshua Levin [12:01]

I would again promote the use of a good regulatory consultant to screen the language. But I think keeping to the same mindset that you're you're putting out an application note as a research tool. If you were putting it out for diagnostic purposes, you wouldn't be a tools company anymore. I think you know if, it's written by a third party, I think you're a little safer there, because it's the third party's opinion. If, for example, that third party the Kol was to say, I think this product could be useful in the diagnosis of XYZ, that's their opinion. And you may, you may get away with that. It's, it's often a little difficult to know what FDA is going to pick on, because oftentimes FDA gets told about things by competitors. You know, what's, what's the risk of putting that language in your documentation, and how important is it to you? That's what you really have to balance. Do

AI and FDA Compliance Monitoring

Jasmine Gruia-Gray [12:51]

you? Do you think that AI will actually have an impact on what the FDA finds out that they no longer rely on information from competitors, but they actually go searching out for these misses themselves. So

Joshua Levin [13:09]

Jasmine, I think you've given FDA a great idea, because, as you know, FDA is very resource strained at the moment, and you know, there's been, as you can imagine, a brain drain from FDA, especially in the diagnostic group, and they're really struggling to get good people they so they have, even when I was there, we had very limited resources to do compliance, so AI could really potentially help a lot there. FDA has tried to use AI, not entirely successfully, in the review process, but I think in the fact that they took a step in that direction indicates that that your idea might not be too far off about them using AI for compliance, it could actually be very effective there in as a screening tool that would be later vetted by humans you

Working with Clinical Lab Customers

Matt Wilkinson [13:55]

mentioned earlier, sort of looking about how r u O companies can maybe work with, you Know, diagnostics or clinical labs, you know, if I'm selling iuo product and my, you know, my sale, you know, I get a request from somebody in a clinical lab, how do I handle it if I learn a customer is using an r, u, O product diagnostically, is there anything I need to say or do or behave differently if they're if it's obviously an academic lab versus if it's actually a clinical lab that is Using an IUI product in a maybe a lab developed test or something like that?

Joshua Levin [14:24]

Matt, that's a good question. As you know, this is an area I'm very passionate about. I've been in kind of all sides of that. As director of r&d kpl, we were balancing the needs of our research customers and our our diagnostic customers. Then again, at FDA, and then at pgdx diagnostic company. So I can, I can speak to my experiences at a Tool Company at kpl. And there we we knew who our customers were and what they were doing with it. So we would, we would put the disclaimer in very big letters. Now it was a little different, because we sold antibodies for food detection salmonella and Listeria and things like that. Well, was FDA regulated, but not in the same way diagnostics is, but with diagnostic companies, sometimes they would come to us and say, well, we need you to be GMP. And we would say, No, we're not going to do that, you know, but we're ISO 9001 you take it or leave it. And then they would come in and do an audit and satisfy themselves, and then leave. So we knew what they were doing. They knew what we were doing, and our attitude was, whatever you guys want to do with the product that's on you. We're selling it for research. You want to make it into a diagnostic have fun. Try not to make any any bones about us being a diagnostic company, and that was one of the reasons for not going to full GMP with our production at pgdx. We were selling our product as as kind of for beta testing or alpha testing. We did have to train our sales staff. I remember a meeting where they put up a list of our customers for the Ruo product and and they had clinical, clinical, clinical, and so we made them take that off. So don't put that on slide. That's discoverable. We are going to get FDA inspected at some point, and well, with lab developed tests, that's a whole nother situation. And when I was at FDA, we were actively trying to get a handle on lab developed tests by going after tools manufacturers. And you can see this with a couple of recent warning letters. We actually have a blog post about a warning letter that was sent to a Gina diagnostics Well, first of all, the name of the company makes it sound like a diagnostic company. So okay, that there's that, but they had an Ruo product where they were making very explicit diagnostic claims, and FDA called them on that, and then when FDA showed up for an inspection, the quality manager just didn't handle it very well, so they weren't really prepared to deal with that kind of question. So they got a warning letter, and there have been a couple examples like that. We did put a lot of effort into to trying to find some use cases when I was at FDA, and it was very difficult to prove intent. So what I would recommend to the tools company is imagine getting inspected by FDA, and think about how you would handle that and make sure your documentation, and, more importantly, your quality people are well equipped to handle a kind of visit from FDA, because it can happen

Matt Wilkinson [16:59]

that's pretty interesting. So in terms of being able to, you know, you wouldn't necessarily go down the GMP routes, there's actually almost things, from a business perspective, to avoid, to almost protect yourself from, saying, Hey, we're a diagnostics company. There's clearly some, some language that you've just you've just told us that have to be really careful of it still feels like there's a, there's this, there's a there's a large sort of gray space that you have to operate in to be really successful

Joshua Levin [17:23]

here. That's true. I would say that some tools companies do go to the effort of creating GMP products and and they'll tell the IBD customers in vitro diagnostic customers, do you want the GMP product or the regular product? Because FDA is very clear on that component suppliers to an in vitro diagnostic do not have to be GMP. So for example, if you're making that antibody and you're selling it to a diagnostic company, you're not required to be be under GMP. But there is a lot of gray space in that. We FDA knew that these tools manufacturers knew where they were selling to and the laboratory developed test situation, which we could talk for another hour about, is another reason why FDA would like to get a handle on Research Use Only products, because they've been told by a court they can't go after lab developed tests. So that that then gives FDA the incentive to move backward into the supply chain to try to get some control over these diagnostic tests, which laboratory developed, tests not cleared or approved by FDA, make up probably 99% of the diagnostic testing market. So 1% of the diagnostic tests are actually FDA regulated. And so FDA would like to get some sort of handle on this, if they could. And that does put tools companies under the microscope

Matt Wilkinson [18:39]

a bit that's almost frightening, that whatever the lab says they are, where's the accountability in that?

Joshua Levin [18:43]

So the lab position on this is that they're regulated by CLIA regulations. Our position at FDA was that CLIA does a very good job of regulating the laboratory operations and and making sure that patient results are not, say switched, for example, which is a very important thing. So you know, you send a sample into Quester LabCorp, and you want to make sure that test result is is yours, and CLIA does a very good job on that. Where we FDA felt that CLIA wasn't doing a particularly good job, was on the test validation. So the requirements are very weak on what constitutes a validated test. And not to go into some detail, but New York state actually has some more sophisticated requirements. But to make long story short, FDA doesn't believe that CLIA is adequate for assuring develop a validation of a diagnostic test. But the labs disagree that the you know, and many of the big labs actually do have very good validation programs. You know, the very sophisticated FDA approach was, well, not we're not worried about you big labs. We're worried about fact that anybody can do this. So there's been a debate for many years to which the labs currently have the upper hand, both because of the court case and because, frankly, the labs FDA has mentioned doesn't have a lot of people left who can really speak to this issue. Most of us have gone to industry where we feel like we can, honestly, we feel like we can do a lot more good by by helping companies work with FDA.

Distributor Compliance

Jasmine Gruia-Gray [19:59]

So if we can pivot a little bit on the business side of things, as you know, many tool companies use distributors, what compliance language belongs in a distributor agreement? What kind of marketing approvals and partner training is typical to prevent off label promotion of an r, u, O product by a distributor.

Joshua Levin [20:24]

So I do have to admit, this is an area where I don't have a large amount of knowledge, but speaking from the regulatory side, or when I was in a research products company working on the R and D side, it would be, you know, scrutinizing, making sure we had the ability treating that distributor as a supplier and making sure we had adequate supplier controls. We had the ability to scrutinize their language. We had the ability to audit them. For example, you know, putting those things into place. And the tools companies I worked with were ISO 9001 certified, which is a good way to build quality system that lets you perform those kinds of supplier related tasks. So I kind of turned my answer into a quality regulatory answer, which I probably didn't fully answer your question, but some of that I have less experience with the contracting side. Well, I

Jasmine Gruia-Gray [21:09]

think what you said makes, makes perfect sense, auditing your distributors, having some kind of approval process to review the documentation before it goes public, review their their website language before it gets public, goes public.

Joshua Levin [21:26]

Absolutely, I think treating them like a supplier, like you would handle your critical suppliers that way. At least I'd hope tools companies do that. They're obviously not required to. But the supply chain is, is a very important piece of these products.

Combined-Function Instruments

Matt Wilkinson [21:38]

Absolutely, just for keeping on that sort of supply chain, but maybe sort of, sort of looking at usage again. If an iuo reagent runs on an instrument also used clinically, or your analysis software outputs a report that could be perceived to be patient like, what marketing lines can't be crossed before you trigger this sort of the IVD requirement. So

Joshua Levin [22:02]

this is a great question. Matt And FDA actually has a guidance on instruments with combined functions. So if you think about like an Illumina sequencer, for example, or PCR device, those can be used both in IBD and Ruo environments. And FDA wants to make sure the instrument manufacturer has a way to carve that out, you know, in order that the instrument isn't going to report. Going to report out, ru, oh, data in a clinical environment. So for example, if you're selling that product, if you're an if you're an instrument manufacturer, like an Illumina or or bio rad, or whoever makes the PCR device, you're selling the instrument into a clinical laboratory, you're able to keep from from that reporting. It is complicated somewhat by the laboratory developed test situation. But FDA does have a guidance on on how you, you, as an instrument manufacturer, can appropriately close off certain functions for diagnostic customers,

Matt Wilkinson [22:51]

and what sort of functions would those be, just so they can, so they can understand, I'll give an example

Joshua Levin [22:55]

from next generation sequencing, which is probably the technology I'm most familiar with. With a lot of these tests, there's, there's a limited number of variants that the system can report in diagnosis mode. So if you're using but of course, next generation sequencing, you can port out, report out an infinite number of variants for research purposes. So FD will want to help have the instrument designed that if it's being run in diagnostic mode, that only those variants can be reported out. In fact, there's a couple of approvals where FD went further and tiered the analytes in terms of how much evidence there was around that particular analyte marker. So some had very clear clinical data associated with them. Some only analytical data, and some were more preliminary.

Matt Wilkinson [23:39]

That's really interesting. And I love the example, because you've got me thinking about some work I used to do with, you know, with the software company that essentially created a software as a service to be able to look at genomic data. And it's being used in by the NHS and, you know, so it is a in some ways, you'd call it a diagnostic product, but it's when it, you know, it was focused on rare disease, and often rare disease. We don't have diagnostic markers yet. We have Mark variants of interest, if you will. So it isn't, it isn't, it's almost impossible to get it validated as a diagnostic instrument in its you know, tool in its entirety, because what you actually want to do is, okay, we've got these markers, as you say, that could be reported out as a diagnosis, but everything else could actually be something of interest, where they are variants of interest, where, actually, if we get enough data, we might be able to one day say these are diagnostic of this particular rare disease.

Joshua Levin [24:34]

That's correct. There are four companies who've gotten approval under pre market approval for their next generation sequencing system. I mean, in addition to Illumina, that has a clearance for the instrument, but those four companies were asked by FDA to come up with a plan for how they were going to continue to monitor variants and update their their test as more information became available from the variants. And to be fair to clinical labs, clinical labs that are doing next generation Sequencing, especially the good ones, are doing this all the time. They're also updating their knowledge base.

Matt Wilkinson [25:06]

Yeah, it's so important, and it's getting that right balance between being able to help a patient with a diagnosis and actually also being able to continue to further knowledge about what are many times are underserved and understudied diseases. No,

Joshua Levin [25:19]

absolutely. And this is one of the areas where the line between Research Use Only in in vitro diagnostics is very tenuous. And at FDA, we were very interested in this, because there's obviously a lot of there were a lot of companies offering sequencing services, and then there were other companies, as you mentioned, Matt, offering the software. So labs were able to put two and two together and come up with a next generation sequencing, oncology diagnostic we were at FDA a little concerned about how to deal with that particular situation. Again, I think, given that laboratory develop tests are no no longer under FDA peer review, that effort has at the moment, it's not a priority of FDA, but that's something to look for. They look at at companies combining different r, u, O, components to make an in vitro diagnostic, which is completely legitimate if they're bringing that diagnostic through FDA. You know, again, as I mentioned before, there's there's nothing wrong with having Research Use Only components in your in vitro diagnostic, long as you go to fda

Three Tips for Entering the Diagnostic Space

Jasmine Gruia-Gray [26:13]

with it. So to round out our discussion today, which has been fantastic, and it's just surfaced how complex this talk is, but to put you on the spot a little bit, are there three tips you can give to tools companies about getting into the diagnostic space? Well, that's

Joshua Levin [26:33]

a great question, Jasmine. So first of all, I would say, go in with your eyes wide open. And again, I'll give you a brief plug for what iron line consulting does. So we look at four elements, the science behind it, which presumably, is there, if the tools company has been doing good science all along, the commercial goals, which are very important, and what is as a company? Maybe this is one of the three tips I'll give us as as a tools company, what is your goal in getting into the diagnostic space, and really understanding that. And then the other question is, what diagnosed diagnostic Do you want to develop? And why? You know, we often see companies coming to us with great technologies, and we ask them what they want to do with it, and what disease do you want to look at? Because you when you develop a diagnostic, you have to have that sees expertise on your team to understand how customers are going to use your product. So I think that would be one, is understanding is understanding the commercial space. And maybe I'll say four tips, counting the good science, because that becomes even more critical as you go to validation under diagnostic realm, then your quality system is very important. As I mentioned, we think it's best practices for tools companies to be under ISO 9001 that's not always possible, but it's it's a good general practice, and but then how do you elevate that, from that to the medical device quality system, which is ISO 1345, which is a lot more explicit around the design process, and has is tied into risk management and things like that. So that is kind of a step up that tools companies need to take. And I'll give an example of something that happened during the covid era. I was working in a diagnostic company at the time, a cell and we wanted to partner with this, a little tools company that had this really cool technology, and they said they could run their assay in two hours. And I said, How is that possible, given all the all the steps you have in your assay? So they invited me over to see them, and I said, Okay, I get how you're doing it in two hours. You're not documenting anything where, in a medical device company, you're writing everything down when you when you run that assay, where they were not even lab enough, this wasn't even best practices. But anyhow, so like quality system, I think is the third, and then regulatory engagement. What's your strategy around engaging with FDA? We recommend something called the pre submission, which is usually a really good way to engage with FDA, and doesn't cost any money, you know, and it's a good way for companies to tow into the water with FDA and get an idea about what the validation requirements might might be and what the regulatory pathway might be. So I think those are the those are the areas we we would look at. That's a great question. I think those companies are often afraid to take that leap.

Jasmine Gruia-Gray [28:58]

It's a big commitment, both financial, well as culturally. Really, really appreciate all your insights today. Thank you so much for joining us on a splice of Life Science marketing and

Joshua Levin [29:10]

thank you both. I enjoyed this conversation. I appreciate the opportunity you.

Q&A

How do I audit our current website copy to identify phrases that might trigger FDA scrutiny?

Start by searching for any language that directly connects your product to diagnosis, detection, or clinical outcomes. Flag phrases like "diagnose," "detect disease," "for use in clinical," or "identifies patients." Replace these with references to published research and analytical capabilities. For example, instead of "detects cancer biomarkers," use "has been shown in literature to correlate with cancer biomarkers" with citation. Have both marketing and regulatory review every product page, especially antibody descriptions and application notes.

What's the fastest way to train our sales team on safe RUO language without overwhelming them?

Create a one-page comparison chart showing "Red Flag Phrases" versus "Safe Alternatives" with five real examples from your product line. Include the key principle: describe what the product does analytically, not what a doctor could do clinically with the result. Role-play customer scenarios where they're asked about diagnostic use. The safe response formula is: acknowledge you know customers use it in various ways, state you cannot market for diagnostic use, and redirect to analytical specifications and published literature.

If a clinical lab customer asks us to become GMP-compliant, how should we respond?

Clarify your positioning as an RUO supplier upfront. Explain you maintain ISO 9001 quality standards appropriate for research tools, and that FDA regulations do not require component suppliers to be GMP. Offer to host their audit of your facilities and quality system. This allows them to qualify you as a supplier while you maintain clear RUO status. Document everything and ensure your sales team never promotes the diagnostic application. Consider offering both RUO and separate GMP product lines if diagnostic business becomes substantial.

How do I present retrospective clinical data in a case study without implying diagnostic validation?

Frame all clinical data within a research context, never a clinical decision-making context. Use language like "research study on archived samples" rather than "clinical validation." Always attribute findings to the research collaborator, not your product's capabilities. Include the research goal explicitly in your description. For example: "Dr. Smith's research on prostate cancer tissue used this antibody to explore biomarker expression patterns in 50 archived samples." Never state or imply the data supports using your product to diagnose patients.

What documentation should I prepare now in case FDA shows up for an inspection tomorrow?

Ensure your quality team has: clear standard operating procedures for how RUO disclaimers appear on all labeling, documented sales training records showing RUO compliance education, audit trails of website and distributor marketing material approvals, and customer communication templates that reinforce RUO status. Create an FDA inspection response plan identifying who speaks to inspectors (quality manager, not marketing). Keep a clean separation between research and any potential diagnostic activities in all documentation. Review recent FDA warning letters to tools companies to understand current enforcement priorities.