Alkermes plc (ALKS) Earnings Call Transcript & Summary
November 17, 2020
Earnings Call Speaker Segments
Operator
operatorGreetings, and welcome to the Alkermes conference call to discuss regulatory update for ALKS 3831. My name is Melissa, and I'll be your operator for today's call. [Operator Instructions] Please note that this call is being recorded. Now I'll turn the call over to Sandra Coombs, Vice President of Investor Relations. Sandy, you may begin.
Sandra Coombs
executiveThank you. Welcome to the Alkermes plc conference call to discuss the regulatory update for ALKS 3831. With me today are Richard Pops, our CEO; and Heather Faulds, our Senior Vice President of Regulatory Affairs. Before we begin, let me remind you that our discussions during this conference call will include forward-looking statements relating to, among other things, our expectations concerning next steps in the regulatory review and potential approval of ALKS 3831. These forward-looking statements are neither promises nor guarantees and are subject to a high degree of uncertainty and risk. Please see our press release issued this morning and our most recent annual and quarterly reports filed with the SEC for important risk factors that could cause our actual results to differ materially from those expressed or implied in the forward-looking statements. We undertake no obligation to update or revise the information provided on this call as a result of new information or future results or developments. After our prepared remarks, we'll open the call for Q&A. Now I'll turn the call over to Richard.
Richard F. Pops
executiveThank you, Sandy. This morning, we announced that FDA issued a complete response letter related to the new drug application for ALKS 3831. The items that led to the CRL relate only to the manufacturing of 3831 at our Wilmington, Ohio facility, and we believe we have a clear path of resolution of those items. As you may have seen from other companies in the past few days, COVID-related issues are impeding FDA's ability to conduct pre-approval inspections. In normal course, we believe the CRL request would have been addressed in the context of a pre-approval inspection. We'll talk a little bit more about that in a minute. But it's important to understand that the CRL did not identify or raise any concerns related to clinical efficacy or safety, and no further clinical studies are requested by FDA to support approval of the application. We were quite surprised to receive the CRL following a week of active and productive discussions on the label with the Division of Psychiatry. I won't give any specific insight into the label until it's finalized upon approval, but it's important to understand that 2 different divisions of FDA are involved here. The review conducted by the Division of Psychiatry has gone according to our expectations, including the completion of the successful advisory committee meeting. The CMC review is conducted by a different office within FDA, the Office of Pharmaceutical Quality or OPQ. In the context of COVID-19, OPQ is conducting only limited pre-approval inspections and is relying instead on document requests. We understand that the CRL was driven by OPQ as the observations noted in the letter were relating to the tablet coating process in certain development batches of ALKS 3831. We believe that, that issue has been resolved for some time and that sufficient data are available to address these observations. We've been in contact with the FDA since we've received the CRL, and FDA has indicated that it hopes to work with us expeditiously to review our responses once they've received them. So Heather Faulds, who runs our regulatory affairs at Alkermes, is going to give you a bit more color on this. And so I'll turn it over to Heather.
Heather Faulds
executiveThanks, Rich. Before I provide further detail on the complete response letter, I'd like to provide some additional context around the remote records review process. A normal course of pre-approval inspection identifies any relevant observations and provides the opportunity for agreement on the provision of additional information or corrective actions. However, earlier this year, in light of COVID-19's impact on FDA's ability to conduct inspections, FDA issued a guidance for industry stating that it intends to use tools -- other tools and approaches, including remote records requests in lieu of inspections where possible. In circumstances where the records review does not sufficiently support approval, FDA has 2 primary options to collect additional information. If a pre-approval inspection is required to address FDA's concerns before approval can be granted, the PDUFA date may be extended until such time that the PAI can be completed. If the agency believes additional documentation may satisfy its concerns, additional information is often requested within the context of a complete response letter. It's important to note that if a question arises during the record review process, the FDA is not obligated to reach out to the sponsor until the action date, even if the sponsor may already have information responsive to FDA's concern. So consistent with guidance, the agency did not conduct a pre-approval inspection at our Wilmington, Ohio facility during its review of this NDA and instead conducted a remote records review. On September 11, FDA confirms receipt of the records requested. Since that date, FDA has not communicated with us about any concerns stemming from this records review despite our numerous requests for feedback. The ALKS 3831 complete response letter noted that based on FDA's review of manufacturing records, the agency requires resolution of certain conditions related to the tablet coating process, which had resulted in some eroded tablets in certain development batches of ALKS 3831. We had identified and addressed this issue and have since manufactured multiple validation batches of ALKS 3831, none of which evidence tablet erosion. The company believes that it has sufficient data to address FDA's observations and is currently preparing those data for submission. We plan to work expeditiously with the agency to address any remaining outstanding items to support approval of ALKS 3831. With that, I will turn the call back over to Rich.
Richard F. Pops
executiveThanks, Heather. So we can finish up there. I'll just finish by saying I'm confident in our processes and the ability of our team to address these outstanding CMC issues in support of the approval of 3831, and we appreciate that this is as frustrating for our shareholders as it is for us. At this point in time, our anticipated launch timing planned for the end of Q1 next year may or may not be impacted. We will provide updates as we progress with FDA. We are quite excited about the opportunity 3831 represents for the patients and the company, and we've developed a very clear go-to-market strategy which leverages our growing presence in this market. So you can expect to hear much more about that as we complete the regulatory process. So with that, I'll turn the call back over to Sandy to run the Q&A.
Sandra Coombs
executiveThanks, Rich. Melissa, we'll now open the call for Q&A, please.
Operator
operator[Operator Instructions] Our first question comes from the line of Vamil Divan with Mizuho.
Vamil Divan
analystMaybe just in spite of the limited amount you can say right now, but just I'll ask a couple of questions. So just one in terms of when you think you will speak to the FDA next and maybe provide a little bit more insight on the costs around the manufacturing review. I'm not sure if there's anything, but appreciate schedules or if there's any sort of general time line that you expect on when you should hear back. And then it sounds like when this is resubmitted, ultimately, it would be a class 1, so I guess, a 2-month review process. And now it's a 6-month review. Can you just confirm that's a reasonable assumption?
Heather Faulds
executiveYes. This is Heather. Thanks for your question. So we've already been in contact with the FDA, and we plan to collaborate and work expeditiously with them on this resubmission. Currently, within Alkermes, we are assembling the necessary documentation to address the issue, and we feel confident in that this is a class 1 resubmission, as you said. And generally, FDA acts on class 1 resubmissions within 2 months.
Operator
operatorOur next question comes from the line of Cory Kasimov with JPMorgan.
Cory Kasimov
analystI guess -- so it sounds like the whole coating issue is something that you already identified and addressed. So is it really a function -- like the hard part of this, at least from what the FDA cited so far, is kind of taken care of, and it's more the paperwork now. Is that the right way to think about it?
Richard F. Pops
executiveYes. Cory, it's Rich. Yes, that's what's so frustrating about it, is that this is an issue that related to development batches. And so typically, in development, you'll be working through various manufacturing issues. We had identified this and fixed it, and it could have been resolved with a document request in the context of the review, but we found out about it in the CRL.
Cory Kasimov
analystOkay. And then as we think about potential timing, it sounds like much of this might just come down to whether or not the FDA decides they need to inspect this facility or can -- or just kind of the electronic records would be sufficient, right? So if they needed to do the inspection, then it becomes more a function of COVID and how long it takes them to do it in the midst of the pandemic. Is that -- am I thinking about it right?
Richard F. Pops
executiveYes. I'll give you my perspective, but I'll let Heather fill it in. That's right. That's why we're actually encouraged that we came back in the form of a CRL as opposed to a delay and just pushing out the PDUFA date pending an inspection. So we're hopeful that it should be resolvable with documentation, but you never know until it's over. But Heather, I'd be happy to hear your point of view on that.
Heather Faulds
executiveYes. I just wanted to underscore that we are encouraged that we received a CRL rather than a request for pre-approval inspection. We do feel like we have the documentation needed to resolve it, and we can move forward with a class 1 resubmission hopefully.
Operator
operatorOur next question comes from the line of Brandon Folkes with Cantor Fitzgerald.
Brandon Folkes
analystMaybe just can you confirm beyond the erosion if there were any other issues raised in the CRL? And just so that I'm clear on this, the issue has been identified and resolved. The PDUFA was Friday. So in terms of documentation, was there anything submitted to the FDA in terms of that resolution prior to the CRL? Or was it just that you thought this was -- the FDA would identify this as an isolated incident in terms of those batches and look at the totality of manufacturing? Just any color to understand in terms of how the issue has been resolved, given that the CRL has just raised it.
Heather Faulds
executiveSo there were no other issues identified in the complete response letter. They were largely around the erosion issue. We didn't submit anything prior to the CRL because we didn't know that it was an issue before the CRL. But the issue does go back to development batches, as Rich said. The team has resolved the issues, and we successfully executed on our validation batches. So as part of the class 1 resubmission, we'll be including those executed batch records along with the associated documentation.
Operator
operatorOur next question comes from the line of Umer Raffat with Evercore ISI.
Umer Raffat
analystHeather, Rich, here's my question. When -- you mentioned there's 2 primary options FDA had. One was through the PAI, the pre-approval inspection; or just to request additional documentation. And you said they went with the latter. But my understanding was that during COVID, FDA is only doing pre-approval inspection since July on "mission-critical drug with a huge public health benefit." And I wonder to what extent that tied into the lack of pre-approval inspection. Or do you think there's additional things about this drug or about this facility that made FDA feel reasonably comfortable they didn't necessarily have to go in personally? Could you just elaborate on that?
Richard F. Pops
executiveYes, Umer. I'll give my point of view, and then we'll ask Heather for hers. Yes, I think it's what you mentioned. The Wilmington facility is an active GMP manufacturing site. We make VIVITROL, ARISTADA, multiple products there for a long time. It's been inspected many times. It had a successful pre-approval inspection in 2018, so it's a site that's known to the FDA. We expected in the context of COVID to have a remote records review under a provision of the law that's called 704(a)(4), which is the authority by which they conduct these remote records reviews. So we were not surprised not to have a PAI. We weren't surprised to receive the CRL on that small -- on that focused topic. So Heather, feel free to chime in on that.
Heather Faulds
executiveYes. I would just underscore what Rich said and add, as we just stated earlier, that during the remote records review process, the agency has no obligation to reach out to the sponsor to ask for additional documentation or information prior to the complete response letter.
Umer Raffat
analystOkay. Got it. And Rich, how has the timing not changed? I thought the reason it was end of Q1 launch was because of scheduling time. I got to believe you have to wait until approval before that process starts. So just curious, is the end of Q1 still possible?
Richard F. Pops
executiveThat's a great question, Umer. Thank you for asking. I should have brought it up proactively, honestly. Because, actually, the descheduling process is not driven by 3831 per se. It's driven by samidorphan. Because -- samidorphan in development, because of its structure, was deemed a class 2 -- category 2 during development. But FDA has recommended to DEA and DEA has now recommended that samidorphan be descheduled. That descheduling process is still underway, and so it hasn't been affected by this FDA action. We continue to expect that to be resolved in Q1 so when the approval comes for 3831, it will be a descheduled drug.
Operator
operatorOur next question comes from the line of Akash Tewari with Wolfe Research.
Akash Tewari
analystSo your PR noted that you had not completed labeling discussions with the FDA on 3831. So would you know at this point if the FDA was going to raise any issues on labeling, let's say, if they had issues with the REMS? And do you feel like these separate discussions could further delay approval? And in terms of time lines, was it -- is it generally normal for labeling discussions to be occurring kind of the week of the PDUFA?
Heather Faulds
executiveAll right. This is Heather. So I can answer that question. So we were in active labeling negotiations with FDA through last week. We're happy with where things stand, and we expect that we'll be finalizing the labeling negotiations expeditiously with the agency after we submit our class 1 resubmission.
Richard F. Pops
executiveAnd Akash, it's Rich. Unfortunately, it's not unusual at all to be in label negotiations right up until the very last moment of the action date.
Akash Tewari
analystOkay. And just to be clear, on the issue of whether you're going to have a REMS program related to 3831, you guys currently feel like that will not be a requirement. Is that fair to say?
Richard F. Pops
executiveNone of our assumptions have changed on that.
Operator
operatorOur next question comes from the line of Jason Gerberry with Bank of America.
Jason Gerberry
analystRich, I just wanted to follow up on the samidorphan part. We've been talking about the descheduling of samidorphan for like 2 years. So what is, I guess, taking so long? And the confidence that you'll have it all sort of resolved in the near term, is it just that you've gotten more concrete FDA guidance as of late as it pertains to the samidorphan descheduling?
Richard F. Pops
executiveYes, you're right. It's -- unlike PDUFA, there's not a clock that this happens on. And I think that the descheduling of samidorphan, in many ways, was still pending an FDA approval of the drug -- or the expectation of FDA approval of the drug. But we do know the process works where FDA makes a recommendation to DEA about scheduling or descheduling. At almost, I think, 100% of the time, DEA follows FDA's recommendation. We knew last spring that the FDA had recommended to DEA to deschedule samidorphan. And then it went into the DEA's black hole. And we recently learned that it's come out of the DEA, and it's gone to OMB, where they make a determination then if it goes back to DEA. So we expect it to be published in the federal register in short order. I can't -- none of us know exactly when, but we expect that notification to be published fairly soon. So it's just something that proceeds at its own pace, and we are making progress.
Jason Gerberry
analystGot it. And if I could just squeeze a follow-up in. So are you expecting to be able to, it sounds like, submit within weeks or 1 month? Or can you be any more specific how quickly you can turn around and resubmit?
Richard F. Pops
executiveWell, we're going to go as fast as we possibly can. I'll let -- Heather is in charge of actual -- all the operations to do it. So I'll let her provide a little bit more color, if she can. But the fact is we activated right away, and we're going like hell. And the fact is we think that the problem is already solved, so that's helpful.
Heather Faulds
executiveYes. Just to build on that. The team is moving swiftly to put together all the documentation needed for the resubmission. There's not a need to generate new data. So it's just a matter of assembling documentation and getting the submission out the door.
Operator
operatorOur next question comes from the line of Terence Flynn with Goldman Sachs.
Terence Flynn
analystI was just wondering if you can talk at all about what's left on the commercial preparation side as you head into next year. And then any perspective on pricing, as I'm assuming most of your discussions with payers have happened? So that would be great if you could weigh in there.
Richard F. Pops
executiveYes. I won't comment on pricing now other than it's a fairly standard approach to think about pricing a new psychiatry product in these markets. Commercial is actually quite exciting. And I was hoping that on this call, we'd be talking more about that, had we not gotten the CR. We're quite excited about a couple of things. One is that we're integrating a lot of the knowledge and learnings of the last few months under COVID and the advent of telepsychiatry and remote interaction with caregivers and so on into what we think is going to be a very modern, streamlined and efficient launch plan that leverages our current presence in the market with ARISTADA. So you'll hear more about that as we get through the regulatory process, and we then prepare it for launch. But what we really like is the fact that we have a really fine long-acting injectable antipsychotic, and now we think we're going to have a really fine oral as well. And the 2 share features of strong efficacy and excellent patient tolerability, and we think those are really important elements in the marketplace.
Operator
operatorOur next question comes from the line of Douglas Tsao with H.C. Wainwright.
Douglas Tsao
analystJust if you could maybe help me understand the chronology a little bit. It sounds like you had, prior to the CRL, identified these issues on their own and corrected them. I'm just curious why you actually didn't reach out to the FDA to inform them that these corrections have been made. Is it just that you didn't think that they would be of sufficient sort of magnitude to warrant the CRL? And then just as a follow-up question on the commercialization and still staying on track, does that mean that given the news and your confidence in approval that you're going to proceed with the pre-commercialization activities that you would have done if you had gotten an approval today?
Richard F. Pops
executiveOkay. So I'll start with the second one, and I'll ask Heather to answer the first. So yes, we're going to continue to proceed from the anticipation for the launch of the drug because we think that's going to happen in Q1, and we want to be ready for that. Heather, you might want to comment on some of the chronology.
Heather Faulds
executiveYes, certainly. So regarding -- in regards to the chronology and ID-ing issues on our own, we did, and that's part of the normal development process. So the issues were identified in development batches, as I mentioned before, and the team addressed the issues and have successfully manufactured a number of batches since then. So there was really no need to reach out to FDA because it's just part of normal drug development. And like we said, we were surprised that it was an issue in FDA's mind, and we didn't hear about it or learn about it until the complete response letter.
Douglas Tsao
analystSo just as a follow-up, Heather, it sounds like as part of the NDA, there were -- there was data from subsequent batches that has corrected this issue. Is that correct?
Heather Faulds
executiveYes, that were not included in the NDA because with small molecules, the validation reports are not included in NDAs.
Richard F. Pops
executiveAnd Doug, just to make a finer point on that. In normal course, you have a pre-approval inspection, and the pre-approval inspection concludes with a closeout report that either results in some discussion about remedial things that should be done, the issuance of a 483 and corrective actions. You have immediate feedback on what needs to be done. Under this new 704(a)(4) provision, they request records, we send records in, and then you might not hear anything until the CR. And I don't think anybody in the industry thinks that's a good plan, but that's the current plan that's operative under COVID.
Operator
operatorLadies and gentlemen, there are no further questions. At this time, I'll turn the floor back to Ms. Coombs for any final comments.
Sandra Coombs
executiveThank you. Thanks, everyone, for joining us on the call this morning. Please don't hesitate to reach out to us at the company if you have any follow-up questions. We'll make ourselves available. Thank you so much.
Operator
operatorThank you. This concludes today's conference. You may disconnect your lines at this time. Thank you for your participation.
Read the full transcript via the API
You're viewing the first half of this call. Get the complete Alkermes plc transcript — plus 248,000+ transcripts from 12,000+ companies, speaker segments, AI summaries and full-text search — through the EarningsCalls.dev API.
Get the API View API docs →For developers and AI pipelines
Programmatic access to Alkermes plc earnings transcripts and 248,000+ others is available through the
EarningsCalls.dev REST API. Plans from $24.99/month — full transcripts, speaker segments,
full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.