Corrections and add to wordlist

pharmaverse · Dec 21, 2023 · d3fb7d8 · d3fb7d8
1 parent 87dc357
commit d3fb7d8
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 2 deletions.
diff --git a/inst/WORDLIST.txt b/inst/WORDLIST.txt
@@ -500,3 +500,14 @@ VSDY
 VSORRES
 VSSEQ
 VSTESTCD
+analytics
+Analytics
+csp
+dS
+eventID
+frontend
+nqJsLSLd
+pageID
+QHuA
+thome
+traceRedir
diff --git a/posts/2023-12-21_end_of__year__up.../end_of__year__update_from_the__pharmaverse__council.qmd b/posts/2023-12-21_end_of__year__up.../end_of__year__update_from_the__pharmaverse__council.qmd
@@ -23,7 +23,7 @@ long_slug <- "2023-12-21_end_of__year__up..."
 
 ## 2023 Was a Big Year
 
-This was a big year for open-source work in clinical submissions in general. We saw Roche speak about shifting to an [open-source backbone for clinicaL trials](https://www.youtube.com/watch?v=nqJsLSLd39A). Novo Nordisk spoke publicly of an [R based submission to the FDA](https://www.youtube.com/watch?v=t33dS17QHuA). These are true marks of progress being made in R becoming a first class language for clinical reporting. 
+This was a big year for open-source work in clinical submissions in general. We saw Roche speak about shifting to an [open-source backbone for clinical trials](https://www.youtube.com/watch?v=nqJsLSLd39A). Novo Nordisk spoke publicly of an [R based submission to the FDA](https://www.youtube.com/watch?v=t33dS17QHuA). These are true marks of progress being made in R becoming a first class language for clinical reporting. 
 
 Back in August, Nicholas Eugenio released a [blog post](https://pharmaverse.github.io/blog/posts/2023-10-10_pharmaverse_story/pharmaverse_story.html) on this history of pharmaverse. It's funny to think about the fact that only 3 years ago, the idea of cross organization collaboration on R packages and building a community around this in the clinical world was just a conversation between friends. Since then, we have a community of more than 1200 people on Slack, 350 on LinkedIn, interest from over 150 organizations, and over 30 packages. If 2020 through 2022 was the birth of Pharmaverse, 2023 was finding our identity as a community. For the council, 2024 will be about continuing to mature and find more ways that we can continue to support the community.
 
@@ -35,7 +35,7 @@ This year our community was also able to launch new platforms to share updates a
 
 ## Where Next? 
 
-Back in October, I had the opportunity to do an interview with Michael Rimler for the [PHUSE video series](Open Source Technologies in Clinical Data Analytics) for open-source technologies in clinical data analytics. The last question he asked me was what I expect the state of data analytics in life science to be in 2 to 3 years. My response was that when that time comes, I hope I couldn't have predicted where we would be - because back in 2020 I could never have predicted where we are now. The progress we've made is unbelievable, and the pharmaverse community has played a huge role in getting us where we are today. For the pharmaverse community, I hope to see that progress continue as we move into next year. As a council, our goal is to continue to mature this community. How can we support and foster collaboration between our organizations? How can we leverage this platform to drive the industry forward?
+Back in October, I had the opportunity to do an interview with Michael Rimler for the [PHUSE video series](Open Source Technologies in Clinical Data Analytics) for open-source technologies in clinical data analytics. The last question he asked me was what I expect the state of data analytics in life science to be in 2 to 3 years. My response was that when that time comes, I hope I couldn't have predicted where we would be - because back in 2020 I could never have predicted where we are now. The progress we've made is unbelievable, and the pharmaverse community has played a huge role in getting us where we are today. For the pharmaverse community, I hope to see that progress continue as we move into next year. As a council, our goal is to continue to mature this community. How can we support and foster collaboration between our organizations? How can we leverage this platform to drive the industry forward?  
 
 For you as an individual, there's always an opportunity to get involved - and you don't have to be a package developer to contribute. You can [join a working group](https://pharmaverse.org/contribute/wg/), write [examples](https://github.com/pharmaverse/examples), or author a [blog post](https://github.com/pharmaverse/blog). Furthermore, you can get started with the pharmaverse packages, provide feedback via issues, and advocate for their use within your own organization. The pharmaverse community doesn't exist without you, and we're happy to have you all here to help us build this together.