|
| 1 | +--- |
| 2 | +name: | |
| 3 | + Kind Regards, \ |
| 4 | + \ |
| 5 | + The R Consortium R Submission Pilot 5 Project Team |
| 6 | +recipient: | |
| 7 | + Food and Drug Administration \ |
| 8 | + Center for Drug Evaluation and Research 5901-B Ammendale Road \ |
| 9 | + Beltsville, MD 20705-1266 |
| 10 | +sent: "TBD, 2025" |
| 11 | +header-image: "rconsortium.png" |
| 12 | +format: |
| 13 | + letter-typst: default |
| 14 | +--- |
| 15 | + |
| 16 | +Dear Sir/Madam: |
| 17 | + |
| 18 | +This letter serves as an introduction to the R Consortium R Submission Pilot 5, focusing on the submission of data submitted in the JavaScript Object Notation (JSON) format. The objective of this portion of the R Consortium R submission Pilot 5 Project is to test the concept that a R-language based submission package is aligned with FDA requirements and meets the expectations of the FDA staff, including assessing code review and analyses reproducibility. All submission materials and communications from this pilot will be shared publicly, with the aim of providing a working example for future R language based FDA submissions which include Shiny applications. This is an FDA-industry collaboration through the non-profit organization R Consortium. |
| 19 | + |
| 20 | +The R Consortium R submission Pilot 5 submission package follows the eCTD folder structure and contains the following module 5 deliverables: |
| 21 | + |
| 22 | +- A cover letter |
| 23 | +- Data files in JSON format generated using R |
| 24 | +- R code to generate 5 ADaM datasets which were used to generate the outputs from the Pilot 1 R submission |
| 25 | +- Outputs that were regenerated from Pilot 1 using these R ADaM datasets generated in this project |
| 26 | +- An Analysis Data Reviewer's Guide (ADRG) |
| 27 | + |
| 28 | +In this pilot, we aimed to provide a working example of R submission in eCTD format to the pharmaceutical industry in compliance with the FDA Electronic Submissions Gateway requirements. Based on the submission package, FDA Staff can review and reproduce submitted R codes. More specifically, we expect the FDA Staff to |
| 29 | + |
| 30 | +- Receive electronic submission packages in eCTD format |
| 31 | +- Install and load open source R packages used in this submission |
| 32 | +- Reproduce the JSON datasets and analysis results |
| 33 | +- Share potential improvements to the submission deliverables and processes via a written communication |
| 34 | + |
| 35 | +All data, code, material and communications from this pilot will be shared publicly. |
| 36 | + |
| 37 | +Different open-source packages were used to create the Shiny application. Evaluating FDA’s acceptance of system/software validation evidence is not in the scope of this pilot. |
| 38 | + |
| 39 | +On behalf of the R Consortium R Submission Working Group, we hope the R submission Pilot 5 can establish a working example to guide the industry for future submission using the R language. |
0 commit comments