Possible collaborate based on notast blog #178
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rmarkdown for blogpost found on https://notast.netlify.com/post/what-s-that-disease-called-overview-of-icd-package/. I have used I used `icd9_chapters` and a few `tidyverse` scripts instead of the manually mapping chapter names
Owner
|
Thanks so much for this. Much appreciated. I have a lot on my plate right now - not forgotten. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Jack
I'm Benjamin and I'm the user behind notast. Instead of manually mapping the
3_digitidentifier range for each chapter as I have done so on the blog, I have used I usedicd9_chaptersand a fewtidyversescripts. (lines 141- 158).It is possible to extract the
major,sub_chapterandchapterfrom the dataset usingicd::chapters_to_map. However, there are two disadvantages.[1] This technique may be longer than what I have done. In the blog, I simply merge the ICD-9 data with my dataset to extract all of the above.
[2] It does not provide me with the
3_digitidentifier range for each chapter. I'm keen to use the3_digitidentifier range instead of the full chapter name because it looks neater as a legend for the visualizations.