Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

codes.json missing entire section of ICD9 codes #1

Open
22csnyder opened this issue Mar 10, 2016 · 6 comments
Open

codes.json missing entire section of ICD9 codes #1

22csnyder opened this issue Mar 10, 2016 · 6 comments

Comments

@22csnyder
Copy link

If you look at the list [child.code for child in tree.children] it contains the following in sequence:

680-709
710-739
760-779
780-789

Notably, it is missing 740-759 (congenital disorders). I think I can fix that I'm just wondering why it's excluded.

@ChenNiu
Copy link

ChenNiu commented Jun 26, 2017

I also missing 280-289. how did you fix it @22csnyder

@haoransh
Copy link

haoransh commented Jul 7, 2017

I'm also wondering why these codes are missing. Seems that the html page structure is tidy so it should be crawled correctly. Could you share your fix? @22csnyder Thanks very much.

@22csnyder
Copy link
Author

I looked into it and it doesn't look like I ever fixed it.

@haoransh
Copy link

haoransh commented Jul 8, 2017

I checked the source code, and found that the first levelFactory only considers 'lvl1.chapter',ignoring the 'lvl1.tabular'. And the format of source website is inconsistent, which is the reason why '740-759' is not crawled. The hierachy level in the page http://icd9cm.chrisendres.com/index.php?action=child&recordid=7440 is 'lvl1' and 'lvl3', leading to the scraper cannot extract any information. In addition, the content of 744-759 is not complete. I'm afraid this repo cannot be used as a tool immediately. @ChenNiu @22csnyder

@pavelzimin
Copy link

Also when I ran [child.code for child in tree.find('800-999').children] I seem to miss the 910-919 codes.

@hardvester
Copy link

same issue here, did some of you find a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants