Code collaboration in NEST

R-bloggers 2025-04-09

[This article was first published on pharmaverse blog, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

In the ever-evolving field of clinical data analysis, innovation and collaboration are key. Today, we are pleased to share an initial, yet important milestone as part of a collaboration effort between Roche and Clinical & Statistical Programming, IDAR, J&J Innovative Medicine (further referred to as J&J) within the NEST framework.

Table creation in clinical reporting in pharma

In clinical trials, the presentation of data is as crucial as the data itself. Clear, accurate, and standardized tables ensure that the results are interpreted correctly and that regulatory bodies can easily review and approve submissions.

For an overview of creation of tables within end-to-end clinical reporting in pharma, both Pharmaverse TLGs Overview and the effort from R Consortium are a useful read to compare examples from several packages.

Code collaboration

Moving forward at J&J, we are transitioning towards adopting R as our preferred analytical tool, and we were thrilled with the capabilities within the NEST framework ( GitHub – insightsengineering/rtables: Reporting tables with R {rtables} , tern {tern} and teal {teal} ) designed by Roche.

As of today, we are building our new internal standard table shells using the open source packages from this NEST framework.

The GitHub – insightsengineering/rtables: Reporting tables with R {rtables} package is designed to simplify and standardize the process of creating tables for clinical trial reports. It offers a flexible and robust framework for generating high-quality, reproducible tables that adhere to industry standards.

While the framework is robust in terms of type of analysis that can be performed, a key requirement for J&J was not met. Our table output format requirement is the usage of rtf with non-monospace fonts.

As such, the initial scope of our collaboration was focusing on this Output Format Customization requirement.

We are proud to share the first result of the collaboration effort! With the current CRAN release of GitHub – insightsengineering/rtables: Reporting tables with R {rtables} , functions related to pagination or export can deal with truetype fonts. See the NEWS updates (rtables 0.6.8) to find out more details on the new features.

While a formal rtf exporter function is not yet available, these updates were key to be able to create tables in our desired output format. Further development will be done to release this functionality for broader usage.

By improving the efficiency and reliability of data presentation, researchers can focus more on the science and less on the formatting. With this update, we have to focus even less on output formatting issues.

Get Involved

We believe in the power of community and open-source development.

We are thankful to Roche for welcoming us as a new collaborator and giving us the opportunity to being part of this journey. Let’s make clinical data analysis smarter, faster, and more reliable than ever before!

This partnership marks a significant milestone in our commitment to contribute to open source package development within a cross pharma network of companies.

We are excited about the potential of NEST packages to transform the way clinical trial data is presented and are confident that, with combined expertise, our industry can achieve remarkable results.

For more information, visit the NEST project page, and don’t forget to follow our progress on GitHub.

As we embarked on this journey, we invite you to join us. Whether you’re an experienced user with feedback, a developer interested in contributing code, or a researcher looking to leverage GitHub – insightsengineering/rtables: Reporting tables with R {rtables} , tern {tern} , or teal {teal} for your projects, your input is invaluable.

We welcome both individual contributors and organizations. Please reach out to contribute via our GitHub, via pharmaverse/slack

Last updated

2025-04-08 12:21:55.029331

Details

Reuse

Citation

BibTeX citation:
@online{augustyns2025,
  author = {Augustyns, Ilse and Masel, Nicholas and Lewandowski, Tad and
    Becker, Gabriel and \& Statistical Programming, IDAR, Johnson \&
    Johnson, Innovative Medicine, Clinical},
  title = {Code Collaboration in {NEST}},
  date = {2025-04-08},
  url = {https://pharmaverse.github.io/blog/posts/2025-04-08_code_collab.../code_collaboration_in__ne_st.html},
  langid = {en}
}
For attribution, please cite this work as:
Augustyns, Ilse, Nicholas Masel, Tad Lewandowski, Gabriel Becker, and Clinical & Statistical Programming, IDAR, Johnson & Johnson, Innovative Medicine. 2025. “Code Collaboration in NEST.” April 8, 2025. https://pharmaverse.github.io/blog/posts/2025-04-08_code_collab…/code_collaboration_in__ne_st.html.
To leave a comment for the author, please follow the link and comment on their blog: pharmaverse blog.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Continue reading: Code collaboration in NEST