-
Notifications
You must be signed in to change notification settings - Fork 60
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
incorporate annual changes to the ICD-9 specifications #6
Comments
This is mostly fixed in release 1.2, but it is not yet possible to specify which ICD-9 version to be used in all functions. |
This document: Need to read Quan papers carefully to see how they handled ICD specification changing over time. Did they set up a list of codes and apply it blindly to all past cases regardless of specification changes (most likely), or did they translate codes before updating? If they did it blindly, then it is probably reasonable to do the same, especially as there have been few changes in recent years. |
There are only 5 changes listed after 2011. I've been slowly working on On Sat, May 16, 2015 at 6:33 AM Jack Wasey notifications@github.com wrote:
|
Good to know, thanks. Now I've included code that parses all the billable code lists, all the raw materials are there to compare and icd9Explain the differences from year to year. It would be great to also have the above PDF machine readable, and to see whether the results match up: perhaps this could be codified in the form of some testthat action, and a function to read in your hand-written data from the PDF. |
This is partially implemented. Ideally, ICD coding data should reference the ICD-9 code table for the year it was entered. Assuming most or all changes involved adding code, using the last published ICD-9-CM codes will work well. Earlier versions are available in icd9. E.g.
|
This is a thorny issue. There have been small updates to ICD-9 each year, until recently.
Furthermore, AHRQ have updated their version of Elixhauser ICD-9 to co-morbidities annually.
A thorough implementation would optionally accept year or date with every ICD-9 code, and treat it appropriately.
The text was updated successfully, but these errors were encountered: