QUESTION
Hi Tech Support,
The PDF is very informative but it appears to be missing explanation of a couple of the output codes. I get ten bits of info but only first eight appear to be documented in the grouper's documentation PDF ("UNIX Embeddable Grouper API": pages 31-32). Those are .......
1. Grouper return code
2. Major Diagnostic category of assigned DRG
3. DRG assigned to patient encounter
4. DRG version number used to assign DRG
5. The weight of the DRG
6. Geometric mean length of stay for DRG
7. PorM flag
8. DRG description
The string I had returned to me by the grouper was....
0^1^57^28^0.9350^0.00^ ^DEGENERATIVE NERVOUS SYSTEM DISORDERS W/O MCC ^1^0
It's the last two fields of "1" and "0" that appear to be undocumented.
The last question I have is regarding the significance of diagnosis codes. When feeding a list of diagnosis codes into the grouper, is there a way to determine which of the diagnosis codes were significant in the grouper's decision making? I ran across something like that on page 22 (section labeled "Output") of the PDF that you folks package with the grouper.
Thanks so much for all of your assistance.
ANSWER
The lack of documentation for these fields is definitely an oversight, thank you for pointing this out. We will include these fields in the updated manual when we release it this coming October.
Those two fields are ASCII-ified bit strings of which codes were used in the DRG assignment. The first field is a string of diagnosis bits and the second string is a string of procedure bits. The strings consist of either an ASCII '1' or an ASCII '0'. A one means "this code was used" and a zero means "this code was not used."
The strings are positional: 1001 means that the first code was used, codes two and three were not but code four was.
Please check the FAQ first, it really is a list of answers to our most frequently-asked questions.
Tuesday, August 30, 2011
Friday, August 19, 2011
ICD10 Transition?
QUESTION
How are you handling the transition to ICD10, especially the years that both ICD9 and ICD10 are supported?
ANSWER
How are you handling the transition to ICD10, especially the years that both ICD9 and ICD10 are supported?
ANSWER
The prototype ICD10 grouper we built was x28 -- FY2011 ICD-10 codes and grouper logic equivalent to f28. The FY2012 ICD-10-PCS (procedure) codes are published, and the FY2012 ICD-9 MS-DRG grouper (f29) will be available in early October 2011, but the FY2012 ICD-10-CM diagnoses are not going to be released by NCHS until December 2011. Hence, no FY2012 ICD-10 MS-DRG grouper (x29) can be produced before January 2012.
The plan is that starting FY2013, there will be no changes to ICD-9 and the FY2013 ICD-10 codes will be available on or before October 1, 2012, so f30 will be the same as f29 and x30 will be available for the start of FY2013. For testing purposes, users coding in ICD-10 will have to code in the FY2011 ICD-10 and use the x28 grouper until January 2012.
Wednesday, November 3, 2010
CGI Demo Version
QUESTION
I am interested in your product CGI-DRG (f24) for Windows, but your demo does not work. Can I get a trial version before buying?
Thanks.
ANSWER
We find that keeping a CGI script working on an ISP's host is a constant struggle. We should probably give up. We are happy to send you an F10 CGI-DRG for you to try; just remember to tell us whether you are running under Windows or Unix.
I am interested in your product CGI-DRG (f24) for Windows, but your demo does not work. Can I get a trial version before buying?
Thanks.
ANSWER
We find that keeping a CGI script working on an ISP's host is a constant struggle. We should probably give up. We are happy to send you an F10 CGI-DRG for you to try; just remember to tell us whether you are running under Windows or Unix.
Friday, October 8, 2010
F28 Released
Our support for version 28 of the US Federal DRG assignment algorithm, active as of October 1st 2010, has just been released.
Monday, September 13, 2010
How Does Access-DRG Work?
QUESTION
ANSWER
Access-DRG is not really a front end, it is a self-contained app. You load data into it, you call its DRG Assignment function (which, in turn, calls our VB-callable DLL) and it does in-place DRG assignment.
If you want to read data from a database server, assign a DRG and put the results back onto the database server, you probably want to get our VB-callable DLL and write your own simple program to read, call and write. Or you can use DRGFilt and the import/assign a DRG/write method described in a DRGFilt posting.
How does the Access front-end work? (ie. Can I link into a SQL Server dataset (as an input) and have the Access-DRG spit out the results into a SQL Server dataset?
ANSWER
Access-DRG is not really a front end, it is a self-contained app. You load data into it, you call its DRG Assignment function (which, in turn, calls our VB-callable DLL) and it does in-place DRG assignment.
If you want to read data from a database server, assign a DRG and put the results back onto the database server, you probably want to get our VB-callable DLL and write your own simple program to read, call and write. Or you can use DRGFilt and the import/assign a DRG/write method described in a DRGFilt posting.
Friday, July 9, 2010
Version NN Invalid
QUESTION
We executed an unix command from PL/SQL stored procedure and got the 'Version 27 Invalid' message from DRGFilt, but executed the same command directly from unix box in putty, everything was fine. The following is the command:
'/u01/app/oracle/product/11.2.0/dbhome_1/bin/drgfilt_lnx_64 -0 f27 drgmasks.f27 /home/mhuang/DRGFilt_control.txt </home/mhuang/DRGFilt_input.txt >/home/mhuang/output.txt'
What does the 'version 27 Invalid' mean to DRGFilt? Also can we add our custom keyword in the control file? We plan add more fields into the control file.
ANSWER
re: "Version 27 Invalid"
This means that version 27 could not be initialized. Usually, this means that the drg masks file could not be found or could not be read.
re: custom keywords
No, DRGFilt does not allow custom keywords; however, you can put line comments into the file so long as those comments are preceded by a sharp sign, like this:
sex 156 1
# this is a line comment
#mykey=5
We executed an unix command from PL/SQL stored procedure and got the 'Version 27 Invalid' message from DRGFilt, but executed the same command directly from unix box in putty, everything was fine. The following is the command:
'/u01/app/oracle/product/11.2.0/dbhome_1/bin/drgfilt_lnx_64 -0 f27 drgmasks.f27 /home/mhuang/DRGFilt_control.txt </home/mhuang/DRGFilt_input.txt >/home/mhuang/output.txt'
What does the 'version 27 Invalid' mean to DRGFilt? Also can we add our custom keyword in the control file? We plan add more fields into the control file.
ANSWER
re: "Version 27 Invalid"
This means that version 27 could not be initialized. Usually, this means that the drg masks file could not be found or could not be read.
re: custom keywords
No, DRGFilt does not allow custom keywords; however, you can put line comments into the file so long as those comments are preceded by a sharp sign, like this:
sex 156 1
# this is a line comment
#mykey=5
Sunday, April 4, 2010
Length of Stay ALOS vs GLOS
QUESTION
ANSWER
I have done some digging and discovered that, as you confirmed, the ALOS is not exposed through this API. You would have to match up the DRG with its ALOS explicitly in your code.
In order to help you with that, please find attached the spreadsheet published by CMS with this information in it. [Note: file was attached to support email, but is not reachable from this blog posting.]
I have your v27 DRG grouper software and it appears that it returns the Geometric mean Length of Stay (GLOS) for each DRG. Is there any way to get the Arithmetic mean Length of Stay (ALOS)? I am using DLL calls from your software's "mhinfo" function to get the GLOS. Please let me know. Thank you.
ANSWER
I have done some digging and discovered that, as you confirmed, the ALOS is not exposed through this API. You would have to match up the DRG with its ALOS explicitly in your code.
In order to help you with that, please find attached the spreadsheet published by CMS with this information in it. [Note: file was attached to support email, but is not reachable from this blog posting.]
Subscribe to:
Posts (Atom)