We use the official CMS test data set to confirm that our DRG assignments are correct. The data set arrives as a text file which we use in a variety of ways:
- we use the text file as-is to validate DRGFilt
- we extract & pretty-print random cases to validate our interactive products
- CGI-DRG under Windows
- CGI-DRG under Linux
- Access-DRG under Windows
- C-callable DLL under Windows
- Linux DLL under Linux
- PHP shared object under Linux
- Perl shared object under Linux
- C shared object under Linux
- we reformat the text file as a CSV in order to validate Excel-DRG
It is item 3 that gave us fits this for a long-standing reason: MS-Excel's CSV import insists on stripping leading zeroes for values it imports if those values are all-numeric. This wreaks havoc on ICD9 or ICD10 codes, either of which can start with one or more zeroes and be all digits for the rest of the code.
There are tricks for formatting the code so that it appears to have its leading zeroes, but that does not help, because the actual data remains the stripped version, which is just plain wrong.
We have painfully rediscovered the only way we know of to fix this (although we welcome suggestions of better ways to do this)
- give your CSV the ".txt" extension, eg "testdb.txt" and NOT "testdb.csv"
- use the Excel Data->Import->text file function
- choose your text file from the list of available files
- in the import dialogue, specify that the delimiter is comma
- at step three, highlight any ICD9 or ICD10 columns and specify that the format is "Text"
- import and confirm
TECHNIQUES WHICH DO NOT WORK
If you are trying to use the native Excel Import function on a file with the CSV extension, eg "testdb.csv", we tried the following ideas without success. Most of these ideas were found on the Internet, free and worth every penny.
- Encasing the data in double-quotes, eg "0016071"
- Using a single-quote at the start of the code, eg '0016071
- Making the value into a formula, eg ="0016071"
- Using a leading blank and double-quotes, eg " 0016071"