pharmaverse

A connected network of companies and individuals working to promote collaborative development of curated open source R packages for clinical reporting usage in pharma, in a space where previously we would only ever have worked in silos on our own closed source and often duplicative solutions. Adopting shared solutions in this post-competitive space should ultimately ease regulatory review, resulting in bringing new treatments to patients faster.

Disclaimer: Anyone is free to choose any selection of pharmaverse recommended software or those from any other source, as there are many different pathways available. Being listed on our site gives no endorsement of the reliability of any code, it is up to you to assess suitability for your needs. Finally, before using any open source software you should always check the license.

Browse pharmaverse topics

Our Charter

Charter for pharmaverse covering our high level objective and scope, along with recommendations for new collaborations.

End-to-End Clinical Reporting Packages

A curated set of R packages that make up the pharmaverse core.

Other Useful Packages

Packages that are key to the pharmaverse, but transcend end-to-end clinical reporting.

Contribute

Ways in which you could contribute to the pharmaverse - for new or existing packages.

Support

How to get support for pharmaverse packages.

Other Open Sourcing

Further open source resources useful for either R enablement or beyond.

Mostly Asked Questions

Is there any presentation available to learn more about the pharmaverse?

Please see our keynote speech at R/Pharma 2022.

Who decides what’s in and not in the pharmaverse?

Anyone can raise a request for a package to be included in the pharmaverse, by raising an issue here and choosing our “New package request” template. Similarly, anyone could raise an issue requesting for anything to be removed from pharmaverse, with the rationale provided. Then we leverage our community via our Slack workspace to give the opportunity for anyone to comment on the proposal. Our website team will then either action the request (if no concerns from our community) or for any contentious decisions our council will be asked to adjudicate.

How can I get involved?

Firstly, join our community on Slack using this link. We are always looking for new collaborators to join us in helping achieve our vision - visit our Contribute section of the site for all options.

How can I get access to these packages?

While it’s likely in a production use of the packages you will be maintaining your own CRAN-like library within your company, for exploration and development purposes any of the hex logos shown above include a link direct to the GitHub repo of each package. We also host the packages, and their dependencies, in a CRAN-like server on R-universe. Please follow this link to see how to point add this CRAN-like server to your library list in R. See information at Get packages

Is this validated/GxP/regulatory assured?

No, but we currently are connecting with several companies and industry working groups (see Other Open Sourcing) to assess whether there could be an industry recommended approach to R package validation utilising open source packages. Until we have this, we’d be happy to share our learnings and current strategies in this area from the companies involved in pharmaverse.

Contributors