Following The Publication Trail of Two RSV Drugs

RSV from Ref. [6]
RSV – Ref. [6]
In a publication from 2007, investigators from Arrow Pharmaceuticals told us that A-60444 (later renamed to RSV-604) was already in Phase 2.  Since then, it has been very quiet about this compound.  Some have suggested that Novartis has stopped development [1], an impression supported by the fact that the drug is not mentioned on the Novartis Clinical Pipeline chart which lists drugs in development  [2].

We still have only scant clinical information on RSV604:  from the Phase 1 trial we only have a company poster [3],  and from the PoC trial in stem cell transplant patients there is a conference report [4].  Clearly, the data did not justify the initial enthusiasm.  And nobody really likes to tie up loose ends for an abandoned compound or work on a full-fledged publication when results were disappointing.  Nonetheless, the patients that altruistically participate in a research trial in order to advance science deserve better.

The story of GS-5806 is just the opposite.  Just a few months after study completion, the positive results are published with fanfare and great detail in the NEJM [5].  There is not only a main summary article, but also a supplemental appendix describing statistics and secondary data.  Even the full protocol is available, thanks for asking.  The Journal has an editorial ready for the occasion and a nice commentary about the ethics and history of human experimentation with infectious agents.  Everyone must have fast-tracked this publication right from the moment the blind was broken.

GS-5806
GS-5806

There is no argument here:  Patients really will benefit from a drug that works in RSV infections.  Gilead is on track with GS-5806 in this effort providing efficacy data from a nicely executed study.  Let’s give credit where it’s due:

RSV studies are notoriously difficult: there is no established precedent, there is no surrogate marker, the clinical presentation is non-specific and the virus is not causing viremia.  As a mucosal disease, there is great inter- and intraindividual variability of viral shedding over time.  Sampling respiratory secretions is a messy way of generating quantitative data.  There is also no good animal model for testing as animal strains are not infecting humans and vice versa.  Not surprisingly, the field is littered with poorly executed studies.  Therefore, my congratulations to DeVincenzo and the Gilead team for executing an innovative study successfully.

  Overall US hospitalization rates for influenza and RSV are similar    H Zhou. CID 2012; 54:1427  

 References:

[1] H. Costello.  http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3835183/
[2] http://www.novartis.com/innovation/research-development/clinical-pipeline/index.shtml
[3] J. Dent. 45th ICAAC, Washington, DC, 2005, Poster F-483
[4] F Marty.  IXth International Symposium on Respiratory Viral Infections.  Causeway Bay, Hong Kong, Mar 3-6, 2007
[5] J. DeVincenzo.  NEJM 371: 8, 2014
[6]  www.niehs.nih.gov

Print Friendly, PDF & Email

2 Replies to “Following The Publication Trail of Two RSV Drugs”

  1. RSV-604 works. Novartis have disclosed that verbally many times. They used the human challenge model but it was many years ago and there were some issues with one study arm that made Novartis think the publication would be sub-standard. They have subsequently talked about publishing, but never have. And of course many people then left Novartis so it will probably never be published. Poor Arrow. They got bought and then sacrificed by AZ so we’ll never know what might have happened.

    • Thanks for your insights, Jeff. I have no proof that “RSV-604 works” as you say and remain unconvinced for lack of data in the public domain.
      It seems the findings in the PoC efficacy study were inconclusive. The sad thing is that these results never got published, so we may never know whether it was the drug that did not work or whether there was a problem with the test conditions and the drug did not get a fair chance to show efficacy. I trust it was safe…

      some other glitch creating an issue. that made it difficult to determine

Leave a Reply

Your email address will not be published. Required fields are marked *