Good evening, and welcome to Bausch + Lomb's BL1332 ocular surface pain R&D update call. All participants will be in listen-only mode. Should you need assistance, please signal a conference specialist by pressing the star key followed by zero. After today's presentation, there will be an opportunity to ask questions. To ask a question, you may press star then one on your touchtone phone. To withdraw your question, please press star then two. Please note, this event is being recorded. I would now like to turn the conference over to Sam Eldessouky, Executive Vice President and Chief Financial Officer. Please go ahead.
Good afternoon, everyone, and thank you for joining us. On the call today, we have Yehia Hashad, our Chief Medical Officer, and Mayssa Attar, Senior Vice President of R&D. Over the next 30 minutes, they will share a detailed update on our ocular surface pain program. As you know, BL1332 is a phase II program, and it was designed to look for an initial efficacy signal. As Yehia and Mayssa will share, we gained valuable learnings from the study, and we look forward to discussing the next steps with the FDA. With that, I am excited to turn the call over to Yehia.
Thank you, Sam, and good afternoon, and thank you, everyone, for joining us. Earlier today, we announced the top-line phase II results for BL1332 in post-PRK, or photorefractive keratectomy, ocular pain. We are excited to walk you through the full data set of the top line, and I will be joined today by Mayssa, as Sam mentioned. Before I hand it over to Mayssa, here are the key highlights of the results. BL1332 showed a compelling clinical profile. Both doses showed numerically greater pain relief than vehicle across every primary, secondary, and exploratory analysis out to the 72 hours, despite the fact that we did not meet the primary endpoint. Exploratory analysis showed more patients reach complete pain relief and clear signal of faster recovery of the corneal epithelium, which generates the hypothesis also of a pain therapy that may support healing.
This is opposite of the trade-off clinicians faces today with steroids and non-steroidal anti-inflammatory as the standard of care. BL1332 was well tolerated with no new safety signals. On that basis, we have initiated extensive analysis of the full data set to initiate discussion with the FDA and other global health authorities on next stage of development with larger confirmatory studies. First, let me remind you why these results matter a lot for eye care. Ocular surface pain is one of the most common reasons patients see an eye care professional. The cornea is the most densely innervated tissue in the body, so even small injuries as abrasions or small ulcers are very painful. In acute pain, 10%-15% of the 4.5 million- 5 million cataract and refractive surgery patients each year are not adequately helped by steroids and non-steroidal anti-inflammatories.
Corneal abrasions or corneal infections and some dry eye flares add to that and are common causes to present sometimes at the ER. Yet, there is no approved treatment that directly address ocular surface pain at its neurosensory source. Clinicians rely on anesthetics in the ER, but they cannot prescribe it or prescribe steroids and non-steroidal anti-inflammatory, which treats inflammation rather than the pain itself and can also delay the wound healing. In chronic pain, 20%-30% of patients with dry eye and neuropathic corneal diseases and 5%-15% of patients underwent surgical procedures could develop chronic ocular pain with non-ocular diseases associated with eye and are inadequately treated. Eye care professional need a better way to manage ocular pain without compromising healing or accepting the trade-offs of steroids and non-steroidal anti-inflammatory.
A topical therapy that directly addresses pain while allowing the ocular surface to heal and does not cause anesthesia of the cornea could fill a meaningful gap in eye care. That is the profile of BL1332 is designed to deliver, and now Mayssa will walk you over the study results.
Thank you, Yehia. As Yehia mentioned, the cornea is the most densely innervated tissue in the body. That is why the ocular surface is so sensitive to pain. On the cornea and conjunctiva, in the terminals of sensory neurons, the TRPV1 receptor is a primary sensor of ocular pain. By blocking, also called antagonizing, TRPV1, we stop the signaling cascade that leads to pain. Bausch + Lomb has two TRPV1 antagonists. BL1312 is our first-generation molecule, which achieved clinical proof of concept in post-surgical pain. Our lead candidate is BL1332, which is more potent and water-soluble. We have been building a clinical evidence dataset for BL1332, and today, we are sharing results from our first phase II study. BL1332 is a new chemical entity and a potent TRPV1 antagonist. We are developing it as a treatment for ocular surface pain by directly targeting the nerve pain signaling pathway.
Here's what we know so far. In phase I, doses up to 0.3% were safe and well-tolerated. In a phase I-B proof-of-mechanism study, BL1332 was highly effective at relieving pain after a capsaicin-induced pain challenge. Capsaicin invokes a pain response via TRPV1, so that phase I-B study showed that BL1332 engages TRPV1 on the ocular surface. Today, we're sharing data from the first study in an intended patient population. This is a phase II trial evaluating BL1332 for treatment of pain after photorefractive keratectomy, or PRK surgery. This study was a randomized, double-masked, vehicle-controlled study in 129 adults ages 18-58 undergoing PRK. Participants were randomized 2:2:1 to BL1332 0.3%, the high dose, BL1332 0.15%, the low dose, or vehicle, which is the placebo, in the study eye. Dosing started immediately after surgery, five doses over 24 hours for three days, with follow-up through day 14.
The primary endpoint was a sum of pain intensity difference, or SPID, at 24 hours. The secondary endpoints were SPID at six and 12 hours, and we looked at 48 and 72 hours as exploratory endpoints. Oral rescue pain medication was allowed for pain above four on the numeric pain rating scale after the first six hours. Importantly, the pre-specified significance level was 0.10 in this study. This study was designed to look for an initial efficacy signal, and it was not powered as a pivotal study. Let's move to the demographics of the patient population. The analysis population had 126 participants. They were young adults with an average age of about 35, roughly half men and half women, and age and sex were well-balanced across the three arms. Before we get to the results, let's discuss a key measure in this study.
SPID, which again stands for sum of pain intensity differences, is an important measure. The way we use it here, our patients are asked to rate their pain from 0, which is no pain, to 10, which is unimaginable pain, at scheduled times after surgery. Each rating is compared with the patient's pre-surgery baseline that's weighted by time and added up. Looking at the graph on the right, we see the baseline pre-surgery. Patients start at 0, and after surgery, patients begin to report pain. SPID captures both how large and how long an effect is. In this study, we compare pain in vehicle-treated patients to BL1332-treated patients. In this analysis, a lower SPID value means less pain. Importantly, FDA's draft acute pain guidance describes SPID as a common primary analysis, and that's why we used it in this study.
Let's move to BL1332's efficacy. Let me orient you to this table. The first column lists the different SPID time windows from six hours through 72 hours. The second column indicates whether the result is for the 0.3% or 0.15% BL1332 dose. The forest plot in the middle depicts how BL1332 performed relative to vehicle, the high dose in dark green squares and the low dose in light green squares. The 0 line indicates no difference between 1332 and vehicle. A negative number, so when the square is to the left of the 0 line, indicates less pain for BL1332-treated patients compared to vehicle, while to the right of 0, a positive number favors the vehicle. As you can see, there are no squares to the right of 0.
If we focus on the green shaded region in the middle, which is the primary endpoint, SPID at 24 hours, we did not reach statistical significance, and therefore, the primary endpoint was not met. As you can see, both doses were numerically lower than vehicle, - 11.5 for the 0.3% dose and -9 For the 0.15% dose. That said, every time window consistently points in the same direction for each dose, so a total of 10 estimates, all of them favor BL1332. A clear signal that supports BL1332's efficacy is early. In the first six hours, when patients were not allowed rescue medication, the 0.3% dose lowered cumulative pain versus vehicle and was nominally significant at our pre-specified 0.10 alpha level. Again, this study was not powered to serve as a pivotal.
Next, we want to share with you two exploratory endpoints that reveal potentially important clinical attributes of BL1332. The first is a responder analysis that looked at patients who reached complete pain relief, meaning a pain score of 0. During the period of peak pain, more BL1332 patients were pain-free. At six hours, about 14% on either dose versus under 4% on vehicle. At 12 hours, 10% and 12% versus none on vehicle. At 24 hours, the groups were similar. Then, as pain resolves, the gap returns. At 72 hours, 71% on 0.3% dose and 59% on the 0.15% dose versus 54% on vehicle. At 72 hours post-surgery, we see that the high dose of BL1332 outperforms the low dose.
While this is an exploratory analysis, it points in the same direction as the SPID results, and pain-free patients is a meaningful endpoint that we can pre-specify in a future study. Now let's move on to a second exploratory finding that looks at the cornea itself. In a subset of patients, we measured central corneal epithelial thickness using anterior segment OCT. Now, why does that matter? After PRK, the epithelium, which would have been removed prior to surgery, has to regrow. Typically, that happens within a few days. Delayed healing of the epithelium is associated with more pain, haze, and infection risk, which can affect vision. Rapid, complete re-epithelialization is a recognized goal. Now let's look at the graph. On day three, epithelial thickness was clearly greater on both BL1332 doses versus vehicle. On day four, the 0.3% dose was still greater.
This result demonstrates that epithelial thickness recovered earlier in BL1332-treated eyes. This is very encouraging as an observation, and we want to better understand and measure this result prospectively in future studies. Recognizing, as Yehia mentioned early on, current medications used to manage pain, like steroids and NSAIDs, which treat pain indirectly, can also delay wound healing. Confirming this attribute of BL1332 would further differentiate it from currently available medications. Specifically, a drug that relieves pain and promotes faster recovery of a healthy ocular surface would be an important new tool for physicians and patients. Overall, what did we learn about BL1332's efficacy in this first study in an intended patient population? Like we said, the primary endpoint, SPID at 24 hours, was not met, but BL1332 was numerically better than vehicle in every SPID window, with nominal significance at six hours.
Importantly, this was the period when no oral rescue medication was allowed. More patients were pain-free after surgery, and epithelial thickness was greater at days three and four. These consistent directional findings and potential differentiating clinical performance attributes will guide the design of future studies. On to safety. BL1332, again, in this study, was well tolerated. There were no treatment-related adverse events, no serious adverse events, no discontinuations due to adverse events, and no deaths. Adverse events were infrequent, none were severe, and there were no new safety signals that emerged from the study. Recall, in our phase I study, there was no hyperthermia, which is a class concern with earlier systemic TRPV1 antagonists. Looking ahead, we are completing the analysis of the full dataset, and we expect to discuss the findings with the FDA and global health authorities.
Informed by those outcomes, we will advance potential phase III planning, evaluating study designs, endpoints, and patient populations that best align with the profile we saw here. Together with the phase I and I-B results, these data will shape those discussions and the program's future development. In summary, our clinical evidence dataset demonstrates BL1332 is well tolerated, it engages its pharmacological target, and in this study, showed a consistent direction of benefit, even though the primary endpoint was not met. We will let the data and the regulatory discussions guide the path forward. Thank you.
Thank you.
I just would like to remind everyone with what we communicated earlier last year at the Investor Day. Acute post-surgical pain is our starting point, not our destination. PRK is one of the most demanding pain models in eye care, which makes it a rigorous place to establish efficacy. The mechanism is also very important. TRPV1 is a primary sensor of pain on the ocular surface, regardless of what caused the injury. That gives this approach the potential to expand beyond post-surgical pain to full range of conditions we discussed previously. That is why we see this as a franchise rather than a single product, with an estimated peak sales of approximately $1.4 billion. It is also natural fit for Bausch + Lomb, as we already serve the surgeons and the eye care professionals who treat these patients every day across our surgical and dry eye portfolio.
Let me leave you with these three points. First, BL1332 showed a consistent pain relief signal across every analysis, with a favorable safety profile, despite missing the statistical significance on the primary endpoint. Second, it showed the potential for a differentiated profile, relieving pain while allowing the ocular surface to heal and without compromising corneal sensitivity. Third, the data gives us clear conviction to discuss with FDA and other global health authorities a potential path forward for phase III planning. Our goal is simple, to give eye care professionals a better way to manage ocular pain without compromise. Next slide, please. Before we open for the line for questions, I want to thank the patients who took part in this study, the investigators and the site teams who conducted it, and our colleagues across Bausch + Lomb who made this program possible.
With that, operator, we are happy to take questions.
Thank you. We will now begin the question and answer session. To ask a question, you may press star then one on your touch-tone phone. If you are using a speakerphone, please pick up your handset before pressing the keys. To withdraw your question, please press star then two. At this time, we will pause momentarily to assemble our roster. The first question comes from Daniel Clark from Leerink Partners. Daniel, your line is live. Please go ahead.
Oh, great. Thank you so much. Could you quantify how much rescue medication was used by arm? If you have color on the percentage of patients requiring rescue, time to first rescue, and total consumption. Just trying to think through how that was used after the initial six-hour period when you showed a nominal significance. Thank you.
Yeah, sure. Mayssa, would you like to address this question?
Yeah. We've looked in the initial top-line dataset. We still need to look at this more carefully. But what we can see is essentially across the three arms, after the six-hour time point where they weren't allowed rescue medication, patients did start using rescue, and it seemed it was pretty consistent across the arms. We need to really look at those data, and that'll be in the additional analyses.
Yeah. We have also to remind that in the protocol, we didn't put strict criteria for rescue medication. So basically, you can see that some patients have used Tylenol, they have used some oral medications, just as a precaution as well. So, I think we're digging into more of this analysis, but as Mayssa mentioned, the good thing that it looks like across the three arms, that there is no big differences.
Thank you. Your next question is coming from Douglas Miehm from RBC Capital Markets. Douglas, your line is live. Please go ahead.
Okay, great. You mentioned that pain-free patients is a meaningful endpoint we can pre-specify in a future study. For phase III, are you leaning towards the NPRS = 0 responder rate as the primary, or would you still require the SPID as the primary, per the FDA's draft acute pain guidance?
I think that's a great question. Again, I will have Mayssa comment, but the initial comment, SPID is the one currently based on the guidance from the FDA is recommended. Obviously, responder analysis is an additional analysis that adds, but so far, the guidance recommends SPID. It doesn't state, but it recommends. Mayssa, would you like to add any other thing, or there's other points?
I want to maybe amplify what you're saying. It is a recommended analysis and recognized as a common primary analysis. Having said that, I think that's what the discussions with the FDA are about. Our goal is to demonstrate what's meaningful to patients, and certainly, being pain-free is meaningful. So, that's something we would like to explore with the FDA, recognizing each asset and drug will have its own attributes that need to be demonstrated as clinically meaningful to patients.
Could the potential thickness finding support a co-primary or a key secondary? Also, in this trial, if you were to run it based on the results you received, how large a patient population would you have had to have run for a P 0.05, 80%-90%?
Yeah. That's a great question because actually, let me start maybe with the second part of the question. In fact, we know that, as Mayssa mentioned, this was a proof-of-concept study. It was not powered as a pivotal study. However, based on the calculations from Obviously, this is rough calculations. We still need to adjust more once we have further analysis of the data, that whether we go with the 80% or 90% confidence, the number of patients will have to be about 190 to 250 or 260. So, it's not a big number of patients that will be required, or huge number of patients that would be required. This also speaks to the magnitude of effect here that we had, that it just that we need more powering and slightly higher sample size than what we had.
The other part of the question, I am sorry, I missed the first part of the question once.
Just around the epithelial thickness finding that you had there. I guess, what is the mechanism behind that, first of all? Then, would you pursue a key secondary or co-primary with that one?
I think, based on the OCT data, and OCT data is usually pretty accurate, I think we can go for secondary endpoints. What we are trying, this is going to be not necessarily it is a differentiation point. This is a product that we think that this can add to the differentiation of such a product rather than in terms of the mechanism, it is a great question. I do not have specific insights, but maybe Mayssa, do you have insights on this one, on the mechanism?
Sure. We have been looking at what else engaging TRPV1 could elicit. There are literature reports around anti-inflammatory effects of TRPV1, so we are pursuing those experiments in our disease biology labs to better understand what is the underlying mechanism for the robust observation we saw in this study.
Thank you.
Thank you. Your next question is coming from Yi Chen from H.C. Wainwright. Yi, your line is live. Please go ahead.
Thank you. This is [Katie] on for Yi. How does this result change the broader ocular pain development strategy for you guys? Are you guys on track? Are you adding anything to the picture? How should we think about this going forward?
I think this is exactly what, so far, what we have communicated. Obviously, this is the first indication that can be moving forward based on the discussion that we will have with the FDA. But I think, as we have said before, it could give the potential for so many other indications to follow, primarily on the chronic ocular surface pain as well. But for the acute, I think this is, again, as mentioned, is matching with our expectations that we communicated at the Investor Day so far.
Thank you.
Thank you. Our last question comes from Aidan Leahy from Bank of America. Aidan, your line is live. Please go ahead.
Hi, good afternoon. Thanks for taking the questions. I guess I'll ask a two-parter. First, how should we think about timings towards discussion with the FDA, and when we could hear about a possible go or no-go on the phase III? Are there any precedents you would point to where you've seen progression to phase III with just a numerically higher efficacy? How should we think about a possible requirement of an additional phase II? Thank you.
Yeah, so these are great. In terms of the timing, I think we will need approximately maybe six months in order that we fully analyze the data, preparing briefing packages. As mentioned before, we are trying to target not only the FDA, but we could be targeting some other global health authorities, so we'll try to work at addressing multiple health authorities at the same time as well. In terms of a go, no-go decision, I think this will be dependent, obviously, on the discussions with the health authorities. I think, as mentioned, usually health authorities can give guidance or feedback without making them the go or no-go decision. But we are actually planning to put for them what type of plans that we're looking for, and we will see what feedback we can get from them.
The third part of the question, I think, was related, is there a possibility for another phase II study? I think if we do another phase II study without enlarging the sample size and getting more of a confirmatory type of design and increase the sample size to go for 80% confidence or 90% confidence, which is designed for a pivotal study, I think this is the next phase, because just repeating another study that is slightly underpowered or things like this, it will give us the same answers. This study have answered what it should be answered, which is there a clear efficacy signal? Yes. Safety profile is favorable? Yes. Does the dose or there is a dose separation that favors the specific dose that we can move forward? Yes.
Number four, does the magnitude of effect is good enough that we can take it for a bigger confirmatory sample size? The answer is yes. So, doing another phase II, I don't think so. The next phase, we should think of a larger confirmatory study.
Thank you.
Thanks.
This concludes our question-and-answer session. I will now turn it back to Dr. Yehia Hashad for closing remarks.
Well, thank you very much, and we really appreciate that you are joining towards the end of the day today. As I mentioned, I just remind you that BL1332, with the results of this study, have shown us a compelling clinical profile with greater pain relief, faster corneal epithelial recovery, and obviously, the next steps will be the FDA discussions and other health authorities for a potential next phase planning. Thank you very much for the time, and again, we would like again to see you with hopefully another next study in the near future. Thank you.
Thank you. The conference has now concluded. Thank you for attending today's presentation. You may now disconnect.