If you (@schuemie and @David_Madigan) are looking for a Greek name for the WG, I offer kybernētēs which meant steersman in ancient Greek - i.e. the person who steered the ship. That fits with the idea of the book being a guide. It is also the origin of the modern word cybernetics, which is cool.
1 Like
Great news everyone! @msuchard has set up TheBookOfOhdsi GitHub repo and has set up the whole bookdown apparatus. Any changes that are pushed to the repo are automatically pushed to book.ohdsi.org.
As promised, I’ll give an overview of how to use it at the next workgroup meeting (December 11).
Cheers,
Martijn
1 Like
Would like to help on this WG - Don
Reminder - no Book of OHDSI call this week. Next call 11am Eastern, December 11th.
@David_Madigan Hi, ATC WG would also like to contribute to the OHDSI Book. We are preparing a “Cook Book” for the new drug-source-code to ATC crosswalks that provides the conventions and methods to do the mapping correctly.
Hamed
The nuances of EHR data need to be exposed in a centralized repository. More standardization and lower hurdles! Count me in 
1 Like
Repeated question what I’ve asked hundreds times was the differences between CDMs including OMOP, Sentinel, PCORnet, STDM, i2b2 and HL7.
It would be great if the “The Common Data Model” chapter deals the philosophy, ecosystem, strength, weakness etc. of each model.
One good paper on that is " Evaluating common data models for use with a longitudinal community registry":
2 Likes
Just to remind everyone that next week we’ll have a book WG meeting on Tuesday. Last week we decided that we’d discuss the following:
- @schuemie will show how the bookdown system works, how to write markdown for the book.
- A review and discussion of the outlines created for 3 chapters:
- Patient-level prediction by @Rijnbeek
- Common Data Model by @mvanzandt and @clairblacketer
- Network Studies by @gregk
To see the details for joining the meeting, or read the notes of the last meeting, see the Workgroup Wiki.
Just a reminder that we have a Book WG meeting today. The agenda (from last meeting):
-
Discuss outlines for Network Studies and Patient-Level Prediction chapters.
-
Review changes to CDM chapter outline.
This weeks notes and recordings have been uploaded to the Wiki.
I have updated our Google Doc with the book outline based on the discussions in the past 3 meetings. I’ve now set the Google Doc so anyone with the link can edit. @clairblacketer, @mvanzandt, @gregk, @Rijnbeek: could you insert your current chapter outlines here? You own these chapters so feel free to make any changes you think necessary in the document.
Also feel free to suggest changes to the outline as a whole, or discuss them in this forum.
Just a reminder that we have a Book WG meeting tomorrow. The agenda (from last meeting):
-
Revisit the CDM, Network Studies, and Patient-Level Prediction chapter outlines
-
Revisit overall book outline
Please insert your chapter outline to the Google Doc.
A friendly reminder that we have a Book of OHDSI workgroup meeting today. Last time we agreed that the respective chapter leads for our three pilot chapters would start to draft these chapters:
- Patient-level prediction
- Common Data Model
- Network studies
So the agenda for today should be reviewing these drafts. @Rijnbeek has excused himself (something about running an EHDEN kickoff meeting 
), but have the other chapter leads made any progress?
@schuemie, unfortunately I don’t have much to share with the group this week. I still need to go through and plan how our sample person’s data will look throughout the chapter.
Great Initiative … !!
Because of various (worthy) distractions we are postponing today’s call for a week. We will meet Tuesday the 29th, 11am Eastern.
@Rijnbeek has submitted a first draft of the PLP chapter to The Book of OHDSI! You can view it here.
I would like to discuss this chapter at tomorrow’s meeting.
As an aside: One thing I like about this bookdown approach is that the book is instantly available on multiple devices. Here’s a photo of the book on my laptop, iPad, iPhone, and e-reader
Not shown is that you can also download the book as PDF, and could print it if you want.
5 Likes
One question raised during this week’s meeting is whether we need to add a license to the book.
For example, R for Data Science is licensed under CC BY-NC-ND 3.0 US.
Does anyone have any knowledge about these licenses? Ideas?
what’s wrong with APL? Attribute, but then do whatever we want.