Chip Baird: Sure. Thanks, Kelsey. Maybe I’ll take the site footprint question first, and then we can talk about the points of differentiation that are emerging in the real-world evidence and real-world setting. From a site footprint perspective, as we’ve described before, we continue to increase the number of sites where documents available for patients and a large market like the US, that’s really important for patients, particularly later-line patients for whom extended travel is difficult. So again, we started it in larger cities and larger academic centers where the was just larger and that made a lot of sense. But as we’ve increased the footprint that’s going to make ABECMA available for more and more patients and we have plans to continue to expand that footprint over time, so that’s an important commercial driver.
But I think the main one is going to be our ability to describe and articulate both the safety profile and the efficacy — competitive efficacy profile of ABECMA in the third-line plus setting. In terms of the what we’re seeing and some of those competitive differentiators in the real-world evidence, again, it’s both safety and I think a closing of the gap from the efficacy perspective, but Anna, I think it would be best to comment on that.
Anna Truppel-Hartmann: Yeah, thank you, Chip. [Indiscernible] evidence data is wonderful to see that the wealth of data is increasing with ABECMA being available now for a while commercially. And what we really can see is that we — whatever dataset that is looked at in the data are reproducible from the KarMMA pivotal study. So any data set has shown either same efficacy or even better efficacy. And of note, many of those patients that are treated in real-world wouldn’t have been eligible for the pivotal study. So this is very, very encouraging to see the real-world evidence data seem to be very beneficial for ABECMA with regards to efficacy, but also with regards to safety. I do think there was also a lot of data around the safety profile of the new agents approved in myeloma.
And also there, ABECMA looks very, very good compared to the other profiles with regards to non-relapse mortality or infections or delayed neurotoxicities, et cetera. So I do think we are very pleased to see how the body of evidence — real world is showing positive results.
Operator: Our next question comes from the line of Samantha Semenkow with Citi.
Samantha Semenkow: Hi, good morning. Thanks for taking our question. I’m wondering if you’re able to share any insight on ABECMA’s utilization trends over the last several months or quarters? What types of patients are receiving, continuing to receive ABECMA — physicians making the decision to utilize ABECMA [Technical Difficulty] competitive BCMA options where — types of centers are you seeing ABECMA use? Any insight you’re able to provide would be helpful?
Chip Baird: Hi, Sam. Yeah. Thanks for the question. I would say it’s really site-specific in terms of how it’s being used. So again, we don’t tend to think of ABECMA being niched for a given type of patient. So really, I think it depends on the site in terms of whether it’s ABECMA-only side versus ABECMA and T cell engager side or whether they have multiple CAR Ts. Those are all different factors that I think impact how ABECMA is being deployed. But certainly, as we think about both the first-line and looking forward to the third-line plus setting, we don’t see ABECMA as niched to a given subset of patients. But Anna, anything from a clinical perspective to add?
Anna Truppel-Hartmann: No, thanks.
Chip Baird: Thank you.
Operator: Thank you. I’m showing no further questions at this time. I’d like to hand the call back over to Chip Baird for closing remarks.
Chip Baird: Thank you, everyone, for making time for the call today, and we look forward to sharing more updates, and I’m sure we’ll be talking again on the other side of the ODAC meeting this week. And with that, I wish everyone a great day. Thank you.
Operator: This concludes today’s conference call. Thank you for your participation. You may now disconnect.
