<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PharmaR</title>
    <link>/</link>
    <description>Recent content on PharmaR</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 11 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>{riskassessment} ShinyGatherings x Pharmaverse Workshop</title>
      <link>/posts/news/riskassessment-workshop/</link>
      <pubDate>Tue, 11 Feb 2025 00:00:00 +0000</pubDate>
      <guid>/posts/news/riskassessment-workshop/</guid>
      <description>&lt;p&gt;At a recent &lt;em&gt;&lt;strong&gt;ShinyGatherings&lt;/strong&gt;&lt;/em&gt;, some &lt;code&gt;{riskassessment}&lt;/code&gt; contributors presented a workshop that focused on tailoring the application to org-specific risk requirements to simplify R package validation. Though we discussed the end-user experience, this workshop was really geared towards equipping &amp;ldquo;app deployers&amp;rdquo; to get the highest and best use out of the application for their organization&amp;rsquo;s specific needs. We appreciate &lt;a href=&#34;https://www.appsilon.com/&#34;&gt;Appsilon&lt;/a&gt; for the opportunity to speak about the application!&lt;/p&gt;&#xA;&lt;br&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/blog/2025-02-11-riskassessment-workshop/riskassessment_workshop_graphic.jpg&#34; width=&#34;100%&#34; max-width=&#34;800&#34;&gt;&lt;/img&gt;&lt;/p&gt;&#xA;&lt;br&gt;&#xA;&lt;h3 id=&#34;about-the-workshop&#34;&gt;About the Workshop&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;The workshop&amp;rsquo;s main topics:&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment App v3.1.1</title>
      <link>/posts/news/updates-aug-2024/</link>
      <pubDate>Thu, 08 Aug 2024 00:00:00 +0000</pubDate>
      <guid>/posts/news/updates-aug-2024/</guid>
      <description>&lt;p&gt;Progress is continuing to be made in &lt;code&gt;{riskassessment}&lt;/code&gt;. We wanted to share some of the enhancements and updates included in the most recent release of the &lt;a href=&#34;https://github.com/pharmaR/riskassessment&#34;&gt;application&lt;/a&gt;. There have been multiple releases, both minor and major, since our last post, so we have a lot of new content to cover!&lt;/p&gt;&#xA;&lt;p&gt;But before we get into too much detail, if you are new to what we are doing in &lt;code&gt;{riskassessment}&lt;/code&gt;, we would like to encourage you to check out our &lt;a href=&#34;https://github.com/pharmaR/riskassessment#readme&#34;&gt;&lt;code&gt;README&lt;/code&gt;&lt;/a&gt;. There you can find information regarding what &lt;code&gt;{riskassessment}&lt;/code&gt; is seeking to accomplish and how you can install and deploy an instance of it for your personal or organizational use.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Updates to the R Validation Hub Executive Team</title>
      <link>/posts/news/updates-sept-2023/</link>
      <pubDate>Tue, 05 Sep 2023 00:00:00 +0000</pubDate>
      <guid>/posts/news/updates-sept-2023/</guid>
      <description>&lt;p&gt;As the R Validation Hub closes in on its 5th year of activity I want to take&#xA;a quick trip down memory lane and reflect on how we got here. Perhaps I should&#xA;start by reminding everyone how it all started. Back in 2018, as the prospect&#xA;of using R for any regulated analysis was still a hotly contested question,&#xA;industry participants brought our donated space at Harvard to capacity as&#xA;attendees gathered for the first ever R/Pharma conference. Amidst a slew of&#xA;impressive &lt;code&gt;shiny&lt;/code&gt; applications (I vividly remember shiny being the decided&#xA;tone-setting theme that year), one Andy Nicholls offered up a deceptively&#xA;simple question: what &lt;em&gt;should&lt;/em&gt; validated use of R look like?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment App v2.0.0</title>
      <link>/posts/news/updates-aug-2023/</link>
      <pubDate>Wed, 16 Aug 2023 00:00:00 +0000</pubDate>
      <guid>/posts/news/updates-aug-2023/</guid>
      <description>&lt;p&gt;Welcome! It&amp;rsquo;s with great excitement and long-awaited anticipation that I get to share some recent updates that have hit the &lt;code&gt;{riskassessment}&lt;/code&gt; app&amp;rsquo;s &lt;a href=&#34;https://github.com/pharmaR/riskassessment&#34;&gt;GitHub repository&lt;/a&gt; earlier this month. If this is the first time you&amp;rsquo;ve heard or seen the application, I&amp;rsquo;d recommend starting with our &lt;a href=&#34;https://github.com/pharmaR/riskassessment#readme&#34;&gt;&lt;code&gt;README&lt;/code&gt;&lt;/a&gt; to gain some familiarity with the project, especially with installation instructions. However, (in a nut-shell) the app is a full-fledged R package that seeks augment the utility of the &lt;a href=&#34;https://github.com/pharmaR/riskmetric&#34;&gt;&lt;code&gt;{riskmetric}&lt;/code&gt;&lt;/a&gt; package within an organizational context.&lt;/p&gt;</description>
    </item>
    <item>
      <title>{riskassessment} App voted best Shiny app at shinyConf 2023! 🎉</title>
      <link>/posts/news/shiny_conf_award/</link>
      <pubDate>Fri, 02 Jun 2023 00:00:00 +0000</pubDate>
      <guid>/posts/news/shiny_conf_award/</guid>
      <description>&lt;p&gt;The &lt;code&gt;{riskassessment}&lt;/code&gt; app, presented by Aaron Clark from the R Validation Hub Executive Committee, was voted best Shiny app at shinyConf 2023. The 2nd Annual Shiny Conference was held in March 2023. It was all virtual with over 4k global registrants. Congratulations!!&lt;/p&gt;&#xA;&lt;p&gt;The app provides a shiny front-end to augment the utility of the &lt;code&gt;{riskmetric}&lt;/code&gt; package, thus user-friendly and interactive access to risk assessment of R packages. The apps functionalities include:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Summary of 2022 Case Studies</title>
      <link>/posts/news/case-studies-summary-march-2023/</link>
      <pubDate>Wed, 15 Mar 2023 00:00:00 +0000</pubDate>
      <guid>/posts/news/case-studies-summary-march-2023/</guid>
      <description>&lt;p&gt;Last year, the R validation hub recently initiated a three-part presentation series on case studies in which eight pharmaceutical companies shared their experiences on building a GxP framework with R. These case studies highlighted both easy and challenging aspects of implementing risk assessment for R packages in a GxP environment. In this blog post we attempt to summarize common themes, difference in approaches, and challenges.&lt;/p&gt;&#xA;&lt;p&gt;All implementations followed the risk validation process for R packages outlined in the white paper. There was a common theme of categorizing package quality into two or three risk categories. Test coverage was identified as a high-importance assessment metric, and the R Foundation was determined to be a trusted resource. Core R and recommended packages were treated as a collective of &amp;ldquo;low-risk&amp;rdquo; packages, with some organizations extending this to the tidyverse.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ASA Biopharmaceutical report, Fall 2022</title>
      <link>/posts/news/2022-12-05-asa-biopharmaceutical-report-fall-2022/</link>
      <pubDate>Mon, 05 Dec 2022 00:00:00 +0000</pubDate>
      <guid>/posts/news/2022-12-05-asa-biopharmaceutical-report-fall-2022/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m pleased to share that the R Validation Hub&amp;rsquo;s efforts have been recognised in the ASA &lt;a href=&#34;https://higherlogicdownload.s3.amazonaws.com/AMSTAT/fa4dd52c-8429-41d0-abdf-0011047bfa19/UploadedImages/BIOP%20Report/BioPharm_fall2022FINAL.pdf&#34;&gt;Biopharmaceutical report, Fall 2022&lt;/a&gt;.  Within the edition you can find our paper, Risk Assessment of R Packages: Learnings and Reflections.  This paper reflects on our white paper; provides an overview of our {&lt;a href=&#34;https://pharmar.github.io/riskmetric/&#34;&gt;riskmetric&lt;/a&gt;} package and &lt;a href=&#34;https://github.com/pharmaR/risk_assessment&#34;&gt;Risk Assessment&lt;/a&gt; application; and summarises our 2022 case studies (which you can now find on our &lt;a href=&#34;/casestudies/&#34;&gt;Case Studies&lt;/a&gt; page).&lt;/p&gt;&#xA;&lt;a href = &#34;https://higherlogicdownload.s3.amazonaws.com/AMSTAT/fa4dd52c-8429-41d0-abdf-0011047bfa19/UploadedImages/BIOP%20Report/BioPharm_fall2022FINAL.pdf&#34;&gt;&#xA;&lt;img src=&#34;/img/banners/asa.jpg&#34; alt=&#34;source: American Statistical Association&#34;&gt;&#xA;&lt;/a&gt;</description>
    </item>
    <item>
      <title>External R Package Qualification Implementation at Merck</title>
      <link>/posts/case-studies/merck-case-study/</link>
      <pubDate>Wed, 21 Sep 2022 00:00:00 +0000</pubDate>
      <guid>/posts/case-studies/merck-case-study/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;There has been a growing interest in pharmaceutical industry to use R for clinical trial data analysis and reporting (A&amp;amp;R). Using R for regulatory submission purposes requires careful qualification of R packages given that the open-source packages differ in their quality of development. Many cross-industry initiatives including R Validation Hub and TransCelerate have published framework for qualifying R packages to be used in a regulatory setting (Nicholls, Bargo, &amp;amp; Sims, 2020) (Amoruccio, Lee, &amp;amp; Woodie, 2021). Our organization has been exploring the use of R in a regulatory setting for the past few years. A framework has been developed internally for qualifying external R packages that incorporates elements from both R Validation Hub and TransCelerate framework. This framework is currently being used to qualify both internally developed and externally sourced R packages for use in clinical trial A&amp;amp;R. In this document, we demonstrate this risk-based package qualification framework using the GGally R package. We provide the workflow as well as relevant details regarding the package qualification process used to qualify GGally as a moderate risk R package. We hope this inspires other organizations to use R in a regulatory setting as well as generate discussion to improve our existing framework.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update May 2022</title>
      <link>/posts/news/status-update-may-2022/</link>
      <pubDate>Fri, 20 May 2022 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-may-2022/</guid>
      <description>&lt;p&gt;It’s time to bring another update to you on the current status of the R validation hub:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The &lt;strong&gt;&lt;code&gt;riskmetric&lt;/code&gt; R package&lt;/strong&gt; has been stable on CRAN. Recent work has focused on structuring &amp;ldquo;cohort metrics&amp;rdquo; &amp;ndash; metrics that are conditioned on the package library or execution environment available to R. In R, package behaviors are often dependent on the rest of the R installation, and this new feature will help to make metrics more inspectible and reproducible, as well as allowing us to ask new questions like, &amp;ldquo;What would be the effect of installing a new package into an R environment?&amp;rdquo;. Within &lt;code&gt;riskmetric&lt;/code&gt;, cohorts will represent our way of capturing this information to help make the context of each metric more explicit. Eric Milliman has been leading this effort, representing the next major feature enhancement for the &lt;code&gt;riskmetric&lt;/code&gt; package.&lt;/p&gt;</description>
    </item>
    <item>
      <title>R Package Risk Assessment at Novartis</title>
      <link>/posts/case-studies/novartis-case-study/</link>
      <pubDate>Mon, 09 May 2022 00:00:00 +0000</pubDate>
      <guid>/posts/case-studies/novartis-case-study/</guid>
      <description>&lt;p&gt;&lt;strong&gt;1 INTRODUCTION&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Whereas data validation is already a standard precursor to any form of scientific analysis in drug development and the validation of in-house built source code used to generate quantitative deliverables follows standard practices as well, the increasing popularity of open source programming languages like R in this context have created a new type of challenge: the validation of the R packages which are imported and used in the drug submission/ approval projects. Such packages are distributed freely, almost always without any warranties, and may be of varying quality. Therefore, Novartis has been working on defining a package risk-based validation approach qualifying R packages. Its risk assessment was designed based on the two business use cases, which reflect current business activities.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automated R Package Validation at Roche</title>
      <link>/posts/case-studies/roche-case-study/</link>
      <pubDate>Fri, 22 Apr 2022 00:00:00 +0000</pubDate>
      <guid>/posts/case-studies/roche-case-study/</guid>
      <description>&lt;p&gt;This case study walks through the automated R package validation process at Roche that utilizes a human-in-the-middle component to reconcile any gaps that arise in the automated metadata checks. The approach balances automation with risk mitigation and encourages in-house package development and iteration by introducing transparency to the validation process. The result reinforces best practices in R programming and package development while ensuring high package quality for use within a regulatory environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment of R Packages at Merck KGaA/EMD Serono</title>
      <link>/posts/case-studies/merck-kgaa-case-study/</link>
      <pubDate>Mon, 14 Feb 2022 00:00:00 +0000</pubDate>
      <guid>/posts/case-studies/merck-kgaa-case-study/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Introduction&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Like many other companies, Merck KGaA/EMD Serono has embarked on their journey to enable the use R for regulatory submissions. Following the framework introduced by the R validation hub (Nicholls et al., 2020), we started to develop an algorithm to qualify a CRAN package as a Merck standard package in our GxP environment. In a nutshell: Given the R Foundation&amp;rsquo;s effort to ensure the validity of base and recommended R packages, these packages are classified as level 1. If an additional R package passes the installation qualification and successfully executes available tests, the package will be made available to the user and (temporarily) classified as level 3 package. Then, an automated risk assessment of R packages is performed based on the test coverage score (more is better) and the riskmetric score generated from the meta-information (smaller is better). If pre-defined thresholds are fulfilled, the package is qualified as Merck standard package (i.e., promoted to level 2), otherwise an explicit (manual) risk assessment is needed. This 3-tier model provides a useful framework for the users to define a risk-based quality control of outputs when using R. In this document, we introduce our pathway to a risk-based assessment of R packages at Merck. We provide relevant details on the statistical analysis which led to the definition of thresholds supporting a robust classification of CRAN packages as Merck standard packages. We want to inspire other companies and seek feedback from the community.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment App Update</title>
      <link>/posts/news/2022-02-03-risk-assessment-app-update/</link>
      <pubDate>Thu, 03 Feb 2022 00:00:00 +0000</pubDate>
      <guid>/posts/news/2022-02-03-risk-assessment-app-update/</guid>
      <description>&lt;p&gt;&lt;strong&gt;This is a re-post.  The original post from the R Consortium can be found &lt;a href=&#34;https://www.r-consortium.org/blog/2022/02/03/risk-assessment-shiny-app-update-from-r-validation-hub&#34;&gt;here&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Recent update by Marly Gotti on the Risk Assessment Shiny App. Marly is an executive committee member of the R Validation Hub where she advocates for the use of R within a biopharmaceutical regulatory setting, and Senior Data Scientist at Biogen.&lt;/p&gt;&#xA;&lt;p&gt;The Risk Assessment App is an interactive web application serving as a front end application for the riskmetric R package. riskmetric is a framework to quantify risk by assessing a number of metrics meant to evaluate development best practices, code documentation, community engagement, and development sustainability. The app and riskmetric aim to provide some context for validation within regulated industries.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some Considerations on Trusted Resources</title>
      <link>/posts/news/trusted-resources/</link>
      <pubDate>Fri, 07 Jan 2022 00:00:00 +0000</pubDate>
      <guid>/posts/news/trusted-resources/</guid>
      <description>&lt;p&gt;There is a large variety of contributed R packages, which can be overwhelming when performing their accuracy assessment. These packages can be developed by anyone and may differ in accuracy. The &lt;a href=&#34;https://www.pharmar.org/white-paper/&#34;&gt;white paper&lt;/a&gt; mentions the possibility to define “trusted resources” to simplify the assessment for some of the R packages.&lt;/p&gt;&#xA;&lt;p&gt;The idea follows vendor assessments / audits to explore the internal validation practices of the vendor for proprietary software. For open-source software such audits are not logistically feasible. However, based on information available in the open-source domain, it may still be possible to perform a virtual audit of a vendor and their practices. In this context, we encourage the publication of software development life cycles (SDLC) documents, which support the process of risk assessment and provide evidence of software trustworthiness.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update: R Validation Hub at R/Pharma 2021</title>
      <link>/posts/news/status-update-r-pharma-2021/</link>
      <pubDate>Tue, 19 Oct 2021 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-r-pharma-2021/</guid>
      <description>&lt;p&gt;Our favorite meeting of the year is approaching: &lt;a href=&#34;https://rinpharma.com/&#34;&gt;R/Pharma 2021&lt;/a&gt; will be held virtually November 2-4th, 2021. Also watch out for workshops the week before.&#xA;Since the R validation Hub is closely associated with R/Pharma, we would like to highlight some of the presentations inspired by the R validation Hub, partner initiatives, or generally related to the topic of validation.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tuesday: November 2, 2021&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;11:00am “R Package Validation at Roche” by Coline Zeballos, Roche&lt;/li&gt;&#xA;&lt;li&gt;11:20am “Statistical Analysis and Pathway to a Risk-based Assessment of R packages at Merck KGaA/EMD Serono” by Juliane Manitz, EMD Serono&lt;/li&gt;&#xA;&lt;li&gt;1:50 PM “Panel Discussion – Validation” with representatives of the R validation Hub”&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Wednesday: November 3, 2021&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update: MSA Framework by TransCelerate </title>
      <link>/posts/news/status-update-transcelerate-msa-framework/</link>
      <pubDate>Thu, 20 May 2021 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-transcelerate-msa-framework/</guid>
      <description>&lt;p&gt;TransCelerate has published &lt;a href=&#34;https://www.transceleratebiopharmainc.com/wp-content/uploads/2021/04/MoA-Initiative_MSAFramework_April-2021.pdf&#34;&gt;&amp;ldquo;Modernization of statistical analytics (MSA) Framework&amp;rdquo;&lt;/a&gt;.&#xA;With goals similar to the R Validation Hub, the TransCelerate MSA framework seeks to demonstrate software reliability by establishing principles of accuracy, traceability, and reproducibility for a modern analytical software environment.&lt;/p&gt;&#xA;&lt;p&gt;The MSA framework is centered around risk-assessment and mitigation practices to demonstrate reliability of software.&#xA;This framework suggests assessing the accuracy of a software library via a confidence measure built on risk metrics such as published source code, issue management, usage, maturity, etc. If confidence does not meet the highest standards, additional testing is recommended. In addition, the intended use of a particular software library and the impact to the broader business outcome determines the requirement for additional testing. Altogether, the MSA framework is in line with the suggestions published in the &lt;a href=&#34;/white-paper/&#34;&gt;R Validation Hub 2020 white paper&lt;/a&gt; for R.&#xA;While the TransCelerate authors suggest their principles apply to a broad range of software, e.g. SAS, R, Python, Julia, etc, they do not provide specific suggestions for the implementation of their framework. The R Validation Hub can support the implementation of MSA inspired features with the &lt;a href=&#34;https://github.com/pharmaR/riskmetric&#34;&gt;R package riskmetric&lt;/a&gt; and the respective &lt;a href=&#34;https://github.com/pharmaR/risk_assessment&#34;&gt;shiny app&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update: CRAN Release of `riskmetric`</title>
      <link>/posts/news/status-update-riskmetric-cran/</link>
      <pubDate>Fri, 02 Apr 2021 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-riskmetric-cran/</guid>
      <description>&lt;p&gt;We have reached a major milestone. The R package &lt;a href=&#34;https://pharmar.github.io/riskmetric/&#34;&gt;&lt;code&gt;riskmetric&lt;/code&gt;&lt;/a&gt; has been released and is now available on CRAN.&lt;/p&gt;&#xA;&lt;h3 id=&#34;what-is-riskmetric&#34;&gt;What is riskmetric?&lt;/h3&gt;&#xA;&lt;p&gt;&lt;code&gt;riskmetric&lt;/code&gt; is a collection of risk metrics to evaluate the quality of R packages following the framework suggested by the R validation hub (see our &lt;a href=&#34;https://www.pharmar.org/white-paper/&#34;&gt;white paper&lt;/a&gt; for details).&#xA;Various quality metrics are provided which evaluate best practices of software development, code documentation, community engagement and development sustainability. This package serves as a starting point for exploring the heterogeneity of code quality, and begin a broader conversation about the validation of R packages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update: Conferences 2021</title>
      <link>/posts/news/status-update-conferences-2021/</link>
      <pubDate>Fri, 12 Mar 2021 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-conferences-2021/</guid>
      <description>&lt;p&gt;The new year is starting with some good news for the R validation hub. We will be able to present our work at a number of different meetings in 2021:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.niss.org/events/niss-merck-meet-open-source-software-pharma&#34;&gt;National Institute of Statistical Sciences&lt;/a&gt; (NISS; April 21, 2021): NISS-Merck Meet-Up on Open Source Software in Pharma&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://psiweb.org/conferences/about-the-conference&#34;&gt;Annual Meeting of Statisticians in the Pharmaceutical Industry&lt;/a&gt; (PSI; June 21-23, 2021): Contributed session accepted&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://ww2.amstat.org/meetings/jsm/2021/&#34;&gt;Joint Statistical Meetings&lt;/a&gt; (JSM; August 7-12, 2021): Topic-contributed session accepted&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update: A summary of 2020</title>
      <link>/posts/news/status-update-a-summary-of-2020/</link>
      <pubDate>Wed, 13 Jan 2021 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-a-summary-of-2020/</guid>
      <description>&lt;p&gt;2020 was a busy year for the R Validation Hub.  We released our &lt;a href=&#34;/white-paper/&#34;&gt;white paper&lt;/a&gt; describing our current thinking on a risk based approach to using R for regulatory work.  We started to support the implementation of the white paper with tools such as &lt;a href=&#34;https://github.com/pharmaR/riskmetric&#34;&gt;&lt;em&gt;riskmetric&lt;/em&gt;&lt;/a&gt; and our &lt;a href=&#34;https://github.com/pharmaR/risk_assessment&#34;&gt;risk assessment application&lt;/a&gt;. And we started a new sub-team with the aim of producing a follow-up white paper on testing.  Throughout,  we have continued to share and gain feedback on our proposed approach, presenting at &lt;a href=&#34;https://youtu.be/WUVUjdqifJ8&#34;&gt;User!&lt;/a&gt;; running a workshop at &lt;a href=&#34;https://pharmar.github.io/rpharma2020/&#34;&gt;R/Pharma&lt;/a&gt;; and speaking at an &lt;a href=&#34;/presentations/eu_prog_heads.pdf&#34;&gt;EU Programming Heads meeting&lt;/a&gt; in June.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment Application</title>
      <link>/posts/news/risk-metric-application/</link>
      <pubDate>Wed, 05 Aug 2020 00:00:00 +0000</pubDate>
      <guid>/posts/news/risk-metric-application/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;Towards the end of 2019, the R Validation Hub received an additional grant from the R Consortium to progress the next phase of our road map and produce a risk assessment app to complement the &lt;a href=&#34;/blog/2020/06/09/2020-06-02-riskmetric-intro-jun-2020/&#34;&gt;riskmetric package&lt;/a&gt;.  In early 2020, &lt;a href=&#34;https://www.fissionlabs.com/&#34; target=&#34;_blank&#34;&gt;Fission Labs&lt;/a&gt; were selected as our partner to build the first iteration of the application.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/blog/2020-08-05-risk-assessment-application_files/fission.png&#34; alt=&#34;&#34; /&gt;&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;em&gt;Fission Labs is a software product development services company delivering product life-cycle management and high-end scalable technology solutions. Our mission is to deliver complex products through simple and efficient engineering.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update July 2020</title>
      <link>/posts/news/status-update-july-2020/</link>
      <pubDate>Mon, 20 Jul 2020 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-july-2020/</guid>
      <description>&lt;p&gt;It’s time to bring some updates to you on the current status of the R validation hub and we are have plenty of great developments.&lt;/p&gt;&#xA;&lt;p&gt;Fission has finished their work on the R package risk assessment app and made the source code is &lt;a href=&#34;https:/github.com/pharmaR/risk_assessment&#34;&gt;available on github&lt;/a&gt;. It is an interactive web application providing a front end for the collection of metrics for R packages via &lt;code&gt;riskmetric&lt;/code&gt; package including visualizations and comparison metrics.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Status Update May 2020</title>
      <link>/posts/news/status-update-may-2020/</link>
      <pubDate>Thu, 07 May 2020 00:00:00 +0000</pubDate>
      <guid>/posts/news/status-update-may-2020/</guid>
      <description>&lt;p&gt;In these uncertain times, we would like to provide you with some good news and update you on the progress from the R validation hub. It has been a little while since you heard from us, but that doesn’t mean we were less active.&lt;/p&gt;&#xA;&lt;p&gt;Communication: You may have realized that there are no further re-occurring meetings scheduled for the R validation hub since February. Following previous discussions, we are planning regular update releases via the website and newsletters instead. Meetings for the validation hub will be scheduled less frequently as needed. However, we are dependent on your input and continue to encourage volunteers to collaborate on all the different parts of the project.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Risk-based Approach for Assessing R package Accuracy within a Validated Infrastructure: White Paper Summary</title>
      <link>/posts/news/a-risk-based-approach-for-assessing-r-package-accuracy-within-a-validated-infrastructure-white-paper-summary/</link>
      <pubDate>Thu, 30 Jan 2020 00:00:00 +0000</pubDate>
      <guid>/posts/news/a-risk-based-approach-for-assessing-r-package-accuracy-within-a-validated-infrastructure-white-paper-summary/</guid>
      <description>&lt;p&gt;In this article I summarise some of the key themes from the R Validation Hub’s white paper, &lt;a href=&#34;/white-paper&#34;&gt;A Risk-based Approach for Assessing R package Accuracy within a Validated Infrastructure&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h1 id=&#34;what-is-the-r-validation-hub&#34;&gt;What is the R Validation Hub?&lt;/h1&gt;&#xA;&lt;p&gt;The R Validation Hub is a cross-industry initiative whose mission is to enable the use of R by the Bio-Pharmaceutical Industry in a regulatory setting, where the output may be used in submissions to regulatory agencies.  The group was initially formed in 2018 by members of PSI’s AIMS SIG but has now expanded to include just under 100 members from multiple organisations across the pharmaceutical sector.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/community-meetings/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/community-meetings/</guid>
      <description>&lt;h3 id=&#34;about-community-meetings&#34;&gt;About Community Meetings&lt;/h3&gt;&#xA;&lt;p&gt;Our community meetings are an initiative we began in 2023 to help foster&#xA;stronger cross-industry connections for those working in biopharma and&#xA;champion the use of R in the industry. Each meeting centers around a&#xA;particular discussion topic, such as approaches for assessing R&#xA;packages’ risk, updates about our R Validation Hub tools, or&#xA;implementation of GxP R environments within companies.&lt;/p&gt;&#xA;&lt;h3 id=&#34;when-are-community-meetings&#34;&gt;When are Community Meetings?&lt;/h3&gt;&#xA;&lt;p&gt;Traditionally, these meetings take place every three months. For updates&#xA;on when the next community meeting is taking place, join our &lt;a href=&#34;https://lists.r-consortium.org/g/RConsortium-Validation-Hub&#34;&gt;mailing&#xA;list&lt;/a&gt; or&#xA;watch out for announcements of the meetings on the R Consortium LinkedIn&#xA;page. As this initiative gains greater momentum, the goal is to make&#xA;these meetings more frequent.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/members-and-workstreams/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/members-and-workstreams/</guid>
      <description>&lt;h3 id=&#34;our-structure&#34;&gt;Our Structure&lt;/h3&gt;&#xA;&lt;p&gt;The R Validation Hub champions a level structure, comprised of many&#xA;workstreams that contribute toward their focus areas and activities.&#xA;Find each workstream’s duties below as well as the members that support&#xA;them.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;If you wish to contribute to any of our efforts, please visit our&#xA;&lt;a href=&#34;https://www.pharmar.org/contribute/&#34;&gt;Contribute&lt;/a&gt; page.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;strategic-workstream&#34;&gt;Strategic Workstream&lt;/h3&gt;&#xA;&lt;p&gt;The &lt;strong&gt;Strategic Workstream&lt;/strong&gt; has the responsibility of aligning on&#xA;longer-term strategic goals. The intention is that this workstream is to&#xA;become a floating set of representatives from each of our workstreams.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/minutes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/minutes/</guid>
      <description>&lt;p&gt;The R Validation Hub operates in the public domain and all meeting&#xA;minutes are made available here. Workstreams meet routinely and compile&#xA;their minutes at their respective links below.&lt;/p&gt;&#xA;&lt;h3 id=&#34;executive-meeting-minutes&#34;&gt;Executive Meeting Minutes&lt;/h3&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/pharmaR/pharmaR/issues?q=is%3Aissue+is%3Aopen+label%3Aminutes&#34;&gt;GitHub&#xA;Link&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;riskassessment-application-workstream-minutes&#34;&gt;&lt;code&gt;{riskassessment}&lt;/code&gt; Application Workstream Minutes&lt;/h3&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/pharmaR/riskassessment/labels/Meeting%20Minutes&#34;&gt;GitHub&#xA;Link&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;communications-workstream-minutes&#34;&gt;Communications Workstream Minutes&lt;/h3&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/pharmaR/communications/tree/main/minutes&#34;&gt;GitHub&#xA;Link&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/participating-orgs/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/participating-orgs/</guid>
      <description>&lt;p&gt;The R Validation Hub is comprised of participants from across the&#xA;pharmaceutical industry. Participants contribute to the effort through&#xA;our regular group meetings, as well as supporting the various&#xA;workstreams that make up the project. Feel free to explore &lt;a href=&#34;https://www.pharmar.org/contribute&#34;&gt;contribution&#xA;opportunities&lt;/a&gt; and subscribe to &lt;a href=&#34;https://lists.r-consortium.org/g/RConsortium-Validation-Hub/&#34;&gt;our&#xA;mailing&#xA;list&lt;/a&gt; to&#xA;stay up-to-date on our progress.&lt;/p&gt;&#xA;&lt;hr /&gt;&#xA;&lt;p&gt;&lt;em&gt;If you are a member and your organization does not appear on this list,&#xA;please let us know!&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/posts/news/2020-06-02-riskmetric-intro-jun-2020/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/posts/news/2020-06-02-riskmetric-intro-jun-2020/</guid>
      <description>&lt;!--## Introduction --&gt;&#xA;&lt;p&gt;Many contributed R packages lack documentation expected in software&#xA;qualification, which is required within pharma and other regulated&#xA;industries. For pharma, there are various regulations, which require&#xA;documentation that demonstrates software is used appropriately and works&#xA;as expected. Thus, industry needs to establish appropriate requirements&#xA;for R packages using selected metadata and useful risk metrics.&lt;/p&gt;&#xA;&lt;p&gt;In context of the R Validation Hub, the R package&#xA;&lt;a href=&#34;https://github.com/pharmaR/riskmetric&#34;&gt;&lt;code&gt;riskmetric&lt;/code&gt;&lt;/a&gt; has been&#xA;developed, which seeks to take the first steps in identifying metrics&#xA;and best practices to quantify the quality of R packages. It provides a&#xA;framework for retrieving package metadata, assessing package metrics,&#xA;and summarizing the risk that the package might not provide accurate&#xA;results. A corresponding Shiny app, that can be used to generate package&#xA;reports using riskmetric, is under development.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>/posts/news/2020-09-21-status-update-sept-2020/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/posts/news/2020-09-21-status-update-sept-2020/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://ropensci.org&#34;&gt;rOpenSci&lt;/a&gt; is an organization devoted to&#xA;“transforming science through data, software and reproducibility.” One&#xA;of rOpenSci’s focal activities is peer review of R packages,&#xA;historically focusing on packages that cover the &lt;a href=&#34;https://devguide.ropensci.org/policies.html#aims-and-scope&#34;&gt;data management&#xA;lifecycle&lt;/a&gt;.&#xA;This has historically excluded software implementing statistical&#xA;methods, for which standards and review require addressing a different&#xA;set of challenges. This year, we have begun tackling these so as to&#xA;expand our peer review system to explicitly encompass statistical&#xA;software, under&#xA;&lt;a href=&#34;https://ropensci.org/blog/2019/07/15/expanding-software-review/&#34;&gt;project&lt;/a&gt;&#xA;funded by the Alfred P. Sloan Foundation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>2022 All-hands: Case Studies</title>
      <link>/old-pages/casestudies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/old-pages/casestudies/</guid>
      <description>&lt;h2 id=&#34;written-case-studies&#34;&gt;Written Case Studies&lt;/h2&gt;&#xA;&lt;p&gt;Written case studies are being developed and peer reviewed on &lt;a href=&#34;https://github.com/pharmaR/case_studies&#34;&gt;GitHub&lt;/a&gt;.  As per the README, &amp;ldquo;The repository contains case studies contributed from companies and individuals, who are implementing a risk-based approach to validate R packages. Feedback in form of community reviews and comments are encouraged. If you want to contribute your own case study, please create a pull request. New contributions will be highlighted in the R validation hub mailing list.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Risk-based Approach for Assessing R package Accuracy within a Validated Infrastructure</title>
      <link>/white-paper/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/white-paper/</guid>
      <description>&lt;p style=&#34;font-size: 16px; text-align: center;&#34;&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Andy Nicholls&lt;/strong&gt;, Statistics Director, Head of Statistical Data Sciences, GSK&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/p&gt;&#xA;&lt;p style=&#34;font-size: 16px; text-align: center;&#34;&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;Paulo R. Bargo&lt;/strong&gt;, Director Scientific Computing, Statistics &amp;amp; Decision Sciences, Janssen R&amp;amp;D&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/p&gt;&#xA;&lt;p style=&#34;font-size: 16px; text-align: center;&#34;&gt;&#xA;&lt;p&gt;&lt;em&gt;&lt;strong&gt;John Sims&lt;/strong&gt;, Director, Analytical Systems Architect &amp;amp; Data Science - Pfizer Vaccine Research&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/p&gt;&#xA;&lt;p style=&#34;font-size: 16px; text-align: center;&#34;&gt;&#xA;&lt;p&gt;&lt;em&gt;On behalf of the &lt;strong&gt;R Validation Hub&lt;/strong&gt;, an R Consortium-funded ISC Working Group&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/p&gt;&#xA;&lt;p style=&#34;text-align: center;&#34;&gt;&#xA;&lt;p&gt;&lt;em&gt;January 23, 2020&lt;/em&gt;&lt;/p&gt;&#xA;&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;View and/or download the PDF version of this white paper &lt;a href=&#34;https://github.com/pharmaR/pharmaR.github.io/blob/master/content/presentations/r_packages-white_paper.pdf&#34;&gt;here&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Us</title>
      <link>/old-pages/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/old-pages/about/</guid>
      <description>&lt;h2 id=&#34;our-mission&#34;&gt;Our Mission&lt;/h2&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;R Validation Hub is a collaboration to support the adoption of R within a&#xA;biopharmaceutical regulatory setting&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;The R Validation Hub is supported by the R Consortium and works closely with&#xA;many neighboring efforts in the pharmaceutical space and broader R ecosystem.&lt;/p&gt;&#xA;&lt;h2 id=&#34;executive-committee&#34;&gt;Executive Committee&lt;/h2&gt;&#xA;&lt;p&gt;&lt;em&gt;R Validation Hub&lt;/em&gt; is governed by an executive committee. Here is the committee,&#xA;as of August 2023:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Doug Kelkhoff (Chair)&lt;/li&gt;&#xA;&lt;li&gt;Joe Rickert (R Consortium)&lt;/li&gt;&#xA;&lt;li&gt;Preetham Palukuru (R Consortium)&lt;/li&gt;&#xA;&lt;li&gt;Juliane Manitz (Communications Workstream Lead)&lt;/li&gt;&#xA;&lt;li&gt;Coline Zeballos (Repositories Workstream Lead)&lt;/li&gt;&#xA;&lt;li&gt;Eric Milliman (&lt;code&gt;riskmetric&lt;/code&gt; Workstream Lead)&lt;/li&gt;&#xA;&lt;li&gt;Aaron Clark (&lt;code&gt;riskassessment&lt;/code&gt; App Workstream Lead)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Thank you to previous committee members for helping to drive the R Validation&#xA;Hub forward:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Accomplishments</title>
      <link>/accomplishments/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/accomplishments/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;/img/page_under_construction.png&#34; width=&#34;432&#34;&gt;&lt;/img&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact Us</title>
      <link>/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/contact/</guid>
      <description>&lt;h2 id=&#34;stay-up-to-date-and-join-our-mailing-list&#34;&gt;Stay up-to-date and join our mailing list&lt;/h2&gt;&#xA;&lt;p&gt;For occasional news updates, you can join our &lt;a href=&#34;https://lists.r-consortium.org/g/RConsortium-Validation-Hub&#34;&gt;mailing&#xA;list&lt;/a&gt;. This will&#xA;enable you and your colleagues to receive notifications of key updates/software&#xA;releases, blog posts and &lt;strong&gt;invites to all-hands Hub meetings&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;interested-in-getting-more-directly-involved&#34;&gt;Interested in getting more directly involved?&lt;/h2&gt;&#xA;&lt;p&gt;If you would like to contribute to this&#xA;collaborative effort &lt;a href=&#34;mailto:Rconsortium-main+owner@lists.r-consortium.org&#34;&gt;please email us&#xA;directly&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contribute</title>
      <link>/contribute/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/contribute/</guid>
      <description>&lt;h2 id=&#34;join-our-mailing-list&#34;&gt;Join Our Mailing List&lt;/h2&gt;&#xA;&lt;p&gt;For occasional news updates, you can join our &lt;a href=&#34;https://lists.r-%20consortium.org/g/RConsortium-Validation-Hub&#34;&gt;mailing&#xA;list&lt;/a&gt;.&#xA;This will enable you and your colleagues to receive notifications of key&#xA;updates/software releases, our latest news and blog posts, and invites&#xA;to all-hands Hub meetings.&lt;/p&gt;&#xA;&lt;p&gt;Once you&amp;rsquo;ve joined, you can &lt;a href=&#34;https://lists.r-%20consortium.org/calendar&#34;&gt;subscribe to our&#xA;calendar&lt;/a&gt; to keep tabs on&#xA;all of the R Validation Hub&amp;rsquo;s all-hands meetings.&lt;/p&gt;&#xA;&lt;hr /&gt;&#xA;&lt;h2 id=&#34;contribute-to-a-working-group&#34;&gt;Contribute to a Working Group&lt;/h2&gt;&#xA;&lt;p&gt;If you are willing and able to commit more time to the R Validation&#xA;Hub&amp;rsquo;s mission, then there are several options depending on your skills&#xA;and interests. If you do not feel you have the necessary technical&#xA;skills to contribute then please don&amp;rsquo;t let that stop you from getting in&#xA;touch and sharing ideas to support the implementation of a risk-based R&#xA;package assessment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Example Package Assessments</title>
      <link>/old-pages/examples/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/old-pages/examples/</guid>
      <description>&lt;br&gt;&#xA;&lt;p&gt;Welcome!&lt;/p&gt;&#xA;&lt;p&gt;Here, we aim to illustrate examples of different validation framework implementations that are used to interpret metrics considered when assessing R packages. Any examples are intended only as a guide to consider how your organization might adopt a solution to the &amp;ldquo;validation problem&amp;rdquo;.&lt;/p&gt;&#xA;&lt;br&gt;&#xA;&lt;h2 id=&#34;get-started-with-risk-based-software&#34;&gt;Get Started with risk-based software&lt;/h2&gt;&#xA;&lt;p&gt;Looking for curated examples on how package metrics might be assessed and interpreted using &lt;code&gt;{riskmetric}&lt;/code&gt;? We&amp;rsquo;d suggest reviewing the &lt;code&gt;Get Started&lt;/code&gt; vignettes for either &lt;a href=&#34;https://pharmar.github.io/riskmetric/articles/riskmetric.html&#34;&gt;&lt;code&gt;{riskmetric}&lt;/code&gt;&lt;/a&gt; or the &lt;a href=&#34;https://pharmar.github.io/riskassessment/articles/riskassessment.html&#34;&gt;&lt;code&gt;{riskassessment}&lt;/code&gt;&lt;/a&gt; application. Both take the user on a highly informative package assessment journey using their respective software.&lt;/p&gt;</description>
    </item>
    <item>
      <title>General Guidances</title>
      <link>/general-guidances/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/general-guidances/</guid>
      <description>&lt;h2 id=&#34;the-accuracy-of-r-packages&#34;&gt;The Accuracy of R Packages&lt;/h2&gt;&#xA;&lt;p&gt;When assessing the accuracy of R packages, the R Validation Hub differentiates R packages by the following types (see German et al, 2013&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;base and recommended (core) packages - developed by the R Foundation and shipped with the basic installation&lt;/li&gt;&#xA;&lt;li&gt;contributed (open source) packages - developed by anyone, and may differ in popularity and accuracy&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/overview/German-et-al.png&#34; alt=&#34;source: German et al (2013): The Evolution of the R Software Ecosystem&#34; /&gt;{alt=&amp;ldquo;source: German et al (2013): The Evolution of the R Software Ecosystem&amp;rdquo;}&lt;/p&gt;</description>
    </item>
    <item>
      <title>Glossary</title>
      <link>/glossary/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/glossary/</guid>
      <description>&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Term&lt;/th&gt;&#xA;          &lt;th&gt;Definition&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Open Source Software&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;Software or language designed for collaboration that has source code available for community review, usage, and modification&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;System Qualification&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;The process including the execution of Installation, Operational and Performance tests on a system that ensures the reproducibility of expected results.&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;strong&gt;Validation&lt;/strong&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;em&gt;Per the FDA&amp;rsquo;s Glossary of Computer System Software Development Terminology&lt;/em&gt; -&amp;ldquo;Establishing documented evidence which provides a high degree of assurance (accuracy) that a specific process consistently (reproducibility) produces a product meeting its predetermined specifications (traceability) and quality attributes.&amp;rdquo;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;</description>
    </item>
    <item>
      <title>Looking Forward</title>
      <link>/looking-forward/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/looking-forward/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;/img/page_under_construction.png&#34; width=&#34;432&#34;&gt;&lt;/img&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meeting Minutes</title>
      <link>/old-pages/minutes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/old-pages/minutes/</guid>
      <description>&lt;p&gt;The R Validation Hub operates in the public domain and all meeting minutes are made available here.&lt;/p&gt;&#xA;&lt;h3 id=&#34;2022-all-hands-case-studies&#34;&gt;2022 All-hands: Case Studies&lt;/h3&gt;&#xA;&lt;p&gt;For the 2022 case studies, please see &lt;a href=&#34;/casestudies/&#34;&gt;here&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;historical-minutes&#34;&gt;Historical minutes&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20210518.pdf&#34;&gt;18 May 2021&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20210216.pdf&#34;&gt;16 Feb 2021&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20201020.pdf&#34;&gt;20 Oct 2020&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20200218.pdf&#34;&gt;18 Feb 2020&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20200121.pdf&#34;&gt;21 Jan 2020&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20191119.pdf&#34;&gt;19 Nov 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20191015.pdf&#34;&gt;15 Oct 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190917.pdf&#34;&gt;17 Sep 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190716.pdf&#34;&gt;16 Jul 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190618.pdf&#34;&gt;18 Jun 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190521.pdf&#34;&gt;21 May 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190402.pdf&#34;&gt;02 Apr 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190228.pdf&#34;&gt;28 Feb 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20190122.pdf&#34;&gt;22 Jan 2019&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20181115.pdf&#34;&gt;15 Nov 2018&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/minutes/R_Validation_Hub_Meeting_minutes_20181002.pdf&#34;&gt;02 Oct 2018&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Our Origins &amp; Mission</title>
      <link>/origins-and-mission/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/origins-and-mission/</guid>
      <description>&lt;h2 id=&#34;origins&#34;&gt;Origins&lt;/h2&gt;&#xA;&lt;p&gt;The R Validation Hub was formed in 2018 by the &lt;a href=&#34;https://psiweb.org/sigs-special-interest-groups/aims&#34;&gt;PSI AIMS Special Interest Group&lt;/a&gt; and is supported by the R Consortium. We work closely with many neighboring efforts in the pharmaceutical space and broader R ecosystem.&lt;/p&gt;&#xA;&lt;h2 id=&#34;mission&#34;&gt;Mission&lt;/h2&gt;&#xA;&lt;p&gt;Our mission is to leverage the open-source and collaborative nature of R while supporting its adoption within the biopharmaceutical setting.&lt;/p&gt;&#xA;&lt;p&gt;Since our inception, we have worked on developing several resources in hopes of their utilization industry-wide. Our solutions for the validation of R packages assist your work by quantifying the &amp;ldquo;risk&amp;rdquo; of R packages with several meaningful metrics (see {riskmetric}) and providing a user-friendly, full-fledged R Shiny app as a central hub to gauge the &amp;ldquo;risk&amp;rdquo; of packages for your organization (see {riskassessment}). These solutions are useful for a variety of roles, like individual contributors who are curious about a package&amp;rsquo;s risk or an organization&amp;rsquo;s administrator(s) for Posit Package Manager, for example.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Partner Initiatives</title>
      <link>/partner-initiatives/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/partner-initiatives/</guid>
      <description>&lt;p&gt;&lt;em&gt;We have partner initiatives with three main entities: the R Consortium, PHUSE, and Statisticians in the Pharmaceutical Industry (PSI).&lt;/em&gt;&lt;/p&gt;&#xA;&lt;hr /&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/partners_files/rconsort.png&#34; width=&#34;180&#34; height=&#34;41&#34;&gt;&lt;/img&gt;&lt;/p&gt;&#xA;&lt;p&gt;The R Validation Hub is an &lt;a href=&#34;https://www.r-consortium.org/projects/isc-working-groups&#34;&gt;R Consortium Working Group&lt;/a&gt;. The R Consortium supports several related working groups. These working groups have a similar overall objective (to support the use of R within the biopharmaceutical industry) but the working groups are complementary: each has its own distinct deliverables; and many of the R Validation Hub&amp;rsquo;s members are also members of the other working groups.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Presentations</title>
      <link>/present/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/present/</guid>
      <description>&lt;h2 id=&#34;2024&#34;&gt;2024&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;May&#xA;&lt;ul&gt;&#xA;&lt;li&gt;PharmaSUG: &lt;a href=&#34;https://github.com/pharmaR/events/blob/main/pharmaSUG_2024/PharmaSUG_SI269_Slides.pptx&#34;&gt;Validating R for Pharma&lt;/a&gt;, &lt;em&gt;Anuja Das&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;2023&#34;&gt;2023&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;October&#xA;&lt;ul&gt;&#xA;&lt;li&gt;R/Pharma: &lt;a href=&#34;https://github.com/pharmaR/events/blob/main/Rpharma2023/slides/RPharma2023.html&#34;&gt;Updates from the R Validation Hub: Toward a Pharma Repository&lt;/a&gt;, &lt;em&gt;Juliane Manitz, Coline Zeballos&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;September&#xA;&lt;ul&gt;&#xA;&lt;li&gt;posit::conf(2023): &lt;a href=&#34;https://pharmar.github.io/events-positconf2023/#/title-slide&#34;&gt;R Validation Hub Status Report and Workshop&lt;/a&gt;, &lt;em&gt;Doug Kelkhoff&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;June&#xA;&lt;ul&gt;&#xA;&lt;li&gt;AZ R Conference: &lt;a href=&#34;https://github.com/pharmaR/events/tree/main/AZ_R_conf_2023&#34;&gt;It&amp;rsquo;s time to integrate the R into PhaRma&lt;/a&gt;, &lt;em&gt;Lyn Taylor&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;March&#xA;&lt;ul&gt;&#xA;&lt;li&gt;ShinyConf 2023: &lt;a href=&#34;https://github.com/pharmaR/events/blob/main/shinyConf_2023/riskassessment_ClarkAaron_shinyConf2023.pdf&#34;&gt;{riskassessment} for R-Package Validation&lt;/a&gt;, &lt;em&gt;Aaron Clark&lt;/em&gt;&lt;/li&gt;&#xA;&lt;li&gt;R Adoption Series: &lt;a href=&#34;https://github.com/pharmaR/events/blob/main/R_Adoption_Series_2023/Manitz_RvalHub_case_study_summaries_2023.pdf&#34;&gt;Learnings and Reflection from RvalHub Case Studies&lt;/a&gt; (&lt;a href=&#34;https://github.com/pharmaR/events/tree/main?tab=readme-ov-file&#34;&gt;recording&lt;/a&gt;), &lt;em&gt;Juliane Manitz, Doug Kelkhoff, Uday Preetham Palakuru, Eric Milliman&lt;/em&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;2022&#34;&gt;2022&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;June&#xA;&lt;ul&gt;&#xA;&lt;li&gt;useR! Conference: &lt;a href=&#34;https://github.com/pharmaR/events/blob/main/useR_2022/Manitz_useR_2022.pdf&#34;&gt;Implementation of Risk Assessment for R Packages: Learnings and Reflection&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;2021&#34;&gt;2021&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;November&lt;/p&gt;</description>
    </item>
    <item>
      <title>R</title>
      <link>/r/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/r/</guid>
      <description>&lt;p&gt;R is a free programming language and software environment that is used for statistical computing. R was first created in 1993, and is now supported by the R Foundation for Statistical Computing.&lt;/p&gt;&#xA;&lt;p&gt;For more information, see &lt;a href=&#34;https://www.r-project.org/about.html&#34;&gt;What is R?&lt;/a&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;base-r&#34;&gt;Base R&lt;/h3&gt;&#xA;&lt;p&gt;As of May 31, 2019, Base R is comprised of 14 packages, with an additional 15 packages included as “Recommended Packages.” These 29 packages compose the core of R and are included with basic R installations. Functionalities of this basic installation include:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Regulations</title>
      <link>/regulations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/regulations/</guid>
      <description>&lt;h3 id=&#34;regulations-overview&#34;&gt;Regulations Overview&lt;/h3&gt;&#xA;&lt;p&gt;Key guidance documents are provided by different regulatory entities, which oversee activities within their respective domains:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals in Human Use (ICH)&lt;/li&gt;&#xA;&lt;li&gt;The United States Food and Drug Administration (FDA)&lt;/li&gt;&#xA;&lt;li&gt;European Medicines Agency (EMA)&lt;/li&gt;&#xA;&lt;li&gt;Japanese Pharmaceuticals and Medical Devices Agency (PMDA)&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr /&gt;&#xA;&lt;h3 id=&#34;ich-e9-statistical-principles-for-clinical-trials&#34;&gt;ICH E9 Statistical Principles for Clinical Trials&lt;/h3&gt;&#xA;&lt;p&gt;At the international level, ICH provides regulatory guidance for the pharmaceutical and medical devices industry. In the &lt;a href=&#34;https://www.fda.gov/regulatory-information/search-fda-guidance-documents/e9-statistical-principles-clinical-trials&#34;&gt;ICH E9 guidance on Statistical Principles for Clinical Trials&lt;/a&gt;. Regarding &amp;ldquo;Integrity of Data and Computer Software Validity&amp;rdquo;, it states:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Regulatory Metrics Repository</title>
      <link>/repository/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/repository/</guid>
      <description>&lt;style&gt;&#xA;:root {&#xA;  --rvh-blue: #467fbf;&#xA;}&#xA;&#xA;.showcase-content-container {&#xA;  display: flex;&#xA;  position: relative;&#xA;  justify-content: center;&#xA;  width: 100%;&#xA;  overflow: hidden;&#xA;}&#xA;&#xA;.showcase-content {&#xA;  box-shadow: 0 0 3em #0008;&#xA;  width: 90%;&#xA;}&#xA;&#xA;@media (min-width: 768px) {&#xA;  .showcase-content {&#xA;    width: 60%;&#xA;  }&#xA;}&#xA;&#xA;.embedded-video {&#xA;  height: auto;&#xA;  aspect-ratio: 16/9;&#xA;}&#xA;&#xA;.flex-row {&#xA;  display: flex;&#xA;  flex-direction: row;&#xA;}&#xA;&#xA;.card &gt; h3 {&#xA;  margin: 0;&#xA;  margin-bottom: 0.8em;&#xA;}&#xA;&#xA;.card {&#xA;  padding: 2em 0em;&#xA;}&#xA;&#xA;.card-body {&#xA;  display: flex;&#xA;  flex-direction: column;&#xA;  margin: 0 !important;&#xA;  padding: 0em 2em;&#xA;  height: 100%;&#xA;}&#xA;&#xA;.card-body :last-child {&#xA;  margin-top: auto;&#xA;}&#xA;&#xA;.card + .card .card-body {&#xA;  border-left: 2px solid #0001;&#xA;}&#xA;&#xA;.card-button {&#xA;  display: inline-block;&#xA;  background: var(--rvh-blue);&#xA;  color: white;&#xA;  padding: 0.5em 1.0em;&#xA;  margin-bottom: 0.75em;&#xA;  font-size: 1.3em;&#xA;  font-weight: bold;&#xA;  border-radius: 0.125em;&#xA;}&#xA;&#xA;.card-button:hover {&#xA;  text-decoration: none;&#xA;  color: white;&#xA;  background: #265f9f;&#xA;}&#xA;&#xA;.card-button * {&#xA;  padding: 0;&#xA;  margin: 0;&#xA;}&#xA;&#xA;.bg-gray {&#xA;  background-color: #dcdcdc;&#xA;}&#xA;&#xA;.bg-light-gray {&#xA;  background-color: #f0f0f0;&#xA;}&#xA;&#xA;.drop-shadow {&#xA;  -webkit-filter: drop-shadow(0 0.125em 0.2em rgba(0, 0, 0, .25));&#xA;  filter: drop-shadow(0 0.125em 0.2em rgba(0, 0, 0, .25));&#xA;}&#xA;&#xA;.pointer:hover {&#xA;  cursor: pointer;&#xA;}&#xA;&#xA;.ready {&#xA;  padding: 1em; &#xA;  border-radius: 1em;&#xA;}&#xA;&#xA;.ready:hover {&#xA;  background-color: #EEE;&#xA;}&#xA;&#xA;.DRAFT {&#xA;  position: absolute;&#xA;  width: 100%;&#xA;  height: 100%;&#xA;}&#xA;&#xA;.DRAFT::after {&#xA;  content: &#34;DRAFT&#34;;&#xA;  top: 50%;&#xA;  font-weight: bolder;&#xA;  color: #F00B;&#xA;  transform: scale(18) rotate(-20deg);&#xA;  display: block;&#xA;  font-size: 100%;&#xA;  position: absolute;&#xA;  left: 50%;&#xA;}&#xA;&lt;/style&gt;&#xA;&lt;div style=&#34;padding-bottom: 2em;&#34;&gt;&#xA;&lt;div class=&#34;showcase-content-container bg-light-gray&#34;&gt;&#xA;&lt;iframe&#xA;class=&#34;showcase-content embedded-video&#34;&#xA;src=&#34;https://www.youtube.com/embed/wyg2R9YSF9I?si=8Oy5CTba6NKBJx2j&#34;&#xA;title=&#34;R Validation Hub Workstream Updates&#34;&#xA;frameborder=&#34;0&#34;&#xA;allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34;&#xA;referrerpolicy=&#34;strict-origin-when-cross-origin&#34;&#xA;allowfullscreen&#xA;&gt;&lt;/iframe&gt;&#xA;&lt;/div&gt;&#xA;&lt;/div&gt;&#xA;&lt;h2 id=&#34;an-open-solution-to-regulatory-quality&#34;&gt;An open solution to regulatory quality&lt;/h2&gt;&#xA;&lt;div class=&#34;row&#34;&gt;&#xA;&lt;div class=&#34;col-sm-8&#34; style=&#34;font-size: 1.25em;&#34;&gt;&#xA;&lt;p&gt;Every regulatory submission requires evidence that the software used meets&#xA;quality standards appropriate for the type of work. The &lt;em&gt;&lt;strong&gt;R Validation Hub&lt;/strong&gt;&lt;/em&gt;&#xA;proposed standards for this process in our &lt;a href=&#34;/white-paper&#34;&gt;2020 White Paper&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Risk Assessment</title>
      <link>/risk/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/risk/</guid>
      <description>&lt;p&gt;The R Validation Hub has develops &amp;amp; maintains useful tools that make the risk assessment approach proposed in our published &lt;a href=&#34;https://www.pharmar.org/white-paper/&#34;&gt;white paper&lt;/a&gt; much easier to adopt for R packages.&lt;/p&gt;&#xA;&lt;h2 id=&#34;open-source-tools&#34;&gt;Open-source tools&lt;/h2&gt;&#xA;&lt;p&gt;Though these tools likely won&amp;rsquo;t encapsulate every aspect of your organization&amp;rsquo;s end-to-end validation pipeline, we are constantly seeking to fill known gaps in the process. Thanks to partnerships with a sleuth of pharma organizations, these tools were designed to leverage &lt;a href=&#34;https://www.pharmar.org/casestudies/&#34;&gt;industry consensus&lt;/a&gt; and provide flexibility for customization when needed. We&amp;rsquo;re proud that both &lt;code&gt;{riskmetric}&lt;/code&gt; and &lt;code&gt;{riskassessment}&lt;/code&gt; have claimed membership in the &lt;a href=&#34;https://pharmaverse.org/&#34;&gt;{pharmaverse}&lt;/a&gt; suite of packages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Roadmap</title>
      <link>/roadmap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/roadmap/</guid>
      <description>&lt;h2 id=&#34;process-and-communication&#34;&gt;Process and Communication&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Publish website [Complete]&lt;/li&gt;&#xA;&lt;li&gt;Agree high level process [Complete except for finalising diagram]&lt;/li&gt;&#xA;&lt;li&gt;Develop white paper [Target: October]&lt;/li&gt;&#xA;&lt;li&gt;Ensure content reflected accurately in website&lt;/li&gt;&#xA;&lt;li&gt;Tools at pilot implementation stage [August 20th]&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;validation--qualification-suite&#34;&gt;Validation / Qualification Suite&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Release metrics package&lt;/li&gt;&#xA;&lt;li&gt;Release Shiny app and reporting tools for risk assessment [Target: January/Q1]&lt;/li&gt;&#xA;&lt;li&gt;Share test suite&lt;/li&gt;&#xA;&lt;li&gt;Build test execution tool&lt;/li&gt;&#xA;&lt;li&gt;Provide an example deployment&lt;/li&gt;&#xA;&lt;li&gt;Agree criteria used to determine whether a package is fit for the Pharma Repository&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;repository&#34;&gt;Repository&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Build Pharma R Repository&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>The {riskassessment} App</title>
      <link>/riskassessment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/riskassessment/</guid>
      <description>&lt;h2 id=&#34;about-the-app&#34;&gt;About the App&lt;/h2&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/risk/riskassessment_logo.png&#34; width=&#34;130&#34;&gt;&lt;/img&gt;&lt;/p&gt;&#xA;&lt;p&gt;The app&amp;rsquo;s &lt;strong&gt;main goal&lt;/strong&gt; is to help those making &amp;ldquo;package inclusion&amp;rdquo; requests for validated GxP environments. So, the highest and best of &lt;a href=&#34;https://bit.ly/raa_gh&#34;&gt;&lt;code&gt;{riskassessment}&lt;/code&gt;&lt;/a&gt; revolves around two things:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Empower members of your organization to embrace their responsibility to assess package risk themselves, prior to making uninformed IT requests like: &amp;ldquo;please add package xyz to our validated environment&amp;rdquo;.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Establish guide rails that adopt to your organizations validation strategy and use of &lt;code&gt;{riskmetric}&lt;/code&gt; which culminates in a report for IT that summarizes each package&amp;rsquo;s adherence to those inclusion requirements.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The {riskmetric} Package</title>
      <link>/riskmetric/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/riskmetric/</guid>
      <description>&lt;h2 id=&#34;about-the-package&#34;&gt;About the Package&lt;/h2&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/risk/riskmetric_logo.png&#34; width=&#34;130&#34;&gt;&lt;/img&gt;&lt;/p&gt;&#xA;&lt;p&gt;Contributed R packages are developed by anyone &amp;amp; everyone, and may differ in popularity and accuracy. As such, the R Validation Hub developed an R package titled &lt;a href=&#34;https://pharmar.github.io/riskmetric/articles/riskmetric.html&#34;&gt;&lt;code&gt;riskmetric&lt;/code&gt;&lt;/a&gt; whose goal is to assess the risk of contributed R packages.&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;{riskmetric}&lt;/code&gt; has four groups of metric criteria:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Unit testing metrics - includes unit test coverage and composite coverage of dependencies&lt;/li&gt;&#xA;&lt;li&gt;Documentation metrics - availability of vignettes, news tracking, example(s) and return object description for exported functions&lt;/li&gt;&#xA;&lt;li&gt;Community engagement - number of downloads, availability of the code in a public repository, formal bug tracking and user interaction&lt;/li&gt;&#xA;&lt;li&gt;Maintainability and reuse - number of active contributors, author / maintainer contacts, and type of license&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Note: Even though the quality of software is sometimes measurable, sometimes it is not. For example, assessing the &lt;strong&gt;accuracy&lt;/strong&gt; of a contributed open-source R package should be done outside of &lt;code&gt;{riskmetric}&lt;/code&gt;. The term &lt;em&gt;accuracy&lt;/em&gt; refers to the risk of an error in the code that, when used, could lead to an incorrect calculation. This incorrect calculation may lead to an incorrect decision during data analysis. The relative impact of an error should be determined by the individual organisation. Thus, impact is not a part of the risk assessment performed by &lt;code&gt;{riskmetric}&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The {riskscore} Package</title>
      <link>/riskscore/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/riskscore/</guid>
      <description>&lt;p&gt;A data package for cataloging riskmetric results across public repositories.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;WARNING:&lt;/strong&gt; Right now, the &lt;a href=&#34;https://github.com/pharmaR/riskscore&#34;&gt;&lt;code&gt;{riskscore}&lt;/code&gt;&lt;/a&gt; is in a PoC stage that is not fully operational. With that said, there are several use cases that make the concept of {riskscore} valuable, including (but not limited to) the following: it &amp;hellip;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Guides more effective discussion around how to summarize risk&lt;/li&gt;&#xA;&lt;li&gt;Helps communicate changes to &lt;code&gt;{riskmetric}&lt;/code&gt;&amp;rsquo;s summarizing algorithm or interpretations of assessment data&lt;/li&gt;&#xA;&lt;li&gt;Aids the &lt;code&gt;{riskmetric}&lt;/code&gt; dev team in identifying &amp;ldquo;edge cases&amp;rdquo; for analysis and code refinement.&lt;/li&gt;&#xA;&lt;li&gt;Provides a channel to distribute handy tools for building &lt;code&gt;{riskmetric}&lt;/code&gt; result data (ie, mimicking how our process for external packages could serve as a useful template for when comparing to internal or private repos).&lt;/li&gt;&#xA;&lt;li&gt;Allows everyone to report risk scores in terms of a &amp;ldquo;CRAN percentile&amp;rdquo; instead of just some arbitrary numeric value.&lt;/li&gt;&#xA;&lt;li&gt;Establishes a central repository for package scores, which can be used for many applications, like generating badge scores or trending in a package&amp;rsquo;s score over time to measure performance.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;hr /&gt;&#xA;&lt;h4 id=&#34;are-you-interested-in-supporting-package-development&#34;&gt;Are you interested in supporting package development?&lt;/h4&gt;&#xA;&lt;p&gt;We could always use extra help/feedback! Please consider one of the following options:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Validation Overview</title>
      <link>/overview/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/overview/</guid>
      <description>&lt;p&gt;For statistical analyses, the process of validation ensures quality output.&lt;/p&gt;&#xA;&lt;p&gt;According to the FDA&amp;rsquo;s &lt;a href=&#34;https://www.fda.gov/iceci/inspections/inspectionguides/ucm074875.htm&#34;&gt;Glossary of Computer System Software Development Terminology&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Validation:&lt;/strong&gt; Establishing documented evidence which provides a high degree of assurance (&lt;em&gt;accuracy&lt;/em&gt;) that a specific process consistently (&lt;em&gt;reproducibility&lt;/em&gt;) produces a product meeting its predetermined specifications (&lt;em&gt;traceability&lt;/em&gt;) and quality attributes.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Since the &lt;a href=&#34;https://www.fda.gov/media/109552/download&#34;&gt;FDA does not require use of any specific software for statistical analyses&lt;/a&gt;, the programming language R can be used if the R installation incorporates all of the following elements:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
