Friday, April 17, 2015 we received a bug report about Access-DRG crashing. We traced the problem to the call to our VB-Callable DLL. We had failed to propagate an update to our servers. We responded with a patch that day.
Please let us know if you are having trouble with Access-DRG so we can diagnose the problem and send you an update if appropriate.
Showing posts with label Access-DRG. Show all posts
Showing posts with label Access-DRG. Show all posts
Friday, April 17, 2015
Monday, February 4, 2013
Issue with Access-DRG and Weights
BUG REPORT
Access-DRG is showing the decimal point in the wrong place for DRG weights, eg Access-DRG reports the weight for DRG 2 as 1.1754 instead of 11.7540.
INVESTIGATION
We confirmed the issue on our Windows validation platform. We confirmed that
this bug did NOT exist on our reference platform. We checked our records and found that our initial drgmasks.f27 file had the decimal place in the wrong place for some weights which was detected as part of quality control. However, we failed to update the canonical image with the corrected file, resulting in at least some customers getting the bad masks file.
RESOLUTION
We confirmed that running the newly updated installer for the f27 masks file corrects the problem. We are sending the bug reporting customer an update right away and working to update our site as soon as possible.
Do not run the masks file "uninstall" as we have an open ticket in which a user claims that running the masks file uninstall removes all masks files, not just the one you want to remove.
If you are not sure if your installation is correct, please run the following test case through our system and see what is returned as the DRG weight; alternately, you can simply download either the Windows installer or masks file directly below.
Sex: M
Disp: 01
MDC: 05
DRG: 002
DX's: Code :E:P E=exempt flag P=present on admission flag
DX01: 4280::
Proc's: Code
SG01: 3764
SG02: 3765
MD5 digest of the bad file and the good file:
Access-DRG is showing the decimal point in the wrong place for DRG weights, eg Access-DRG reports the weight for DRG 2 as 1.1754 instead of 11.7540.
INVESTIGATION
We confirmed the issue on our Windows validation platform. We confirmed that
this bug did NOT exist on our reference platform. We checked our records and found that our initial drgmasks.f27 file had the decimal place in the wrong place for some weights which was detected as part of quality control. However, we failed to update the canonical image with the corrected file, resulting in at least some customers getting the bad masks file.
RESOLUTION
We confirmed that running the newly updated installer for the f27 masks file corrects the problem. We are sending the bug reporting customer an update right away and working to update our site as soon as possible.
Do not run the masks file "uninstall" as we have an open ticket in which a user claims that running the masks file uninstall removes all masks files, not just the one you want to remove.
If you are not sure if your installation is correct, please run the following test case through our system and see what is returned as the DRG weight; alternately, you can simply download either the Windows installer or masks file directly below.
- Link to the raw masks file for Unix users:https://www.dropbox.com/s/sqyq12ju34b18oa/drgmasks.f27
- Link to the Windows installer:https://www.dropbox.com/s/p2pspwh307fshi3/mhmasksf27.exe
- Test case
Sex: M
Disp: 01
MDC: 05
DRG: 002
DX's: Code :E:P E=exempt flag P=present on admission flag
DX01: 4280::
Proc's: Code
SG01: 3764
SG02: 3765
MD5 digest of the bad file and the good file:
2f35a9084f929e0075bcddc8d1bcaa35 badweights.drgmasks.f27
7fb9267df1268ab182126ce67700da64 drgmasks.f27
MD5 digest of the bad installer and the good installer:
7b30bb3e24904a7d04d86b4bec60e146 badweights.mhmasksf27.exe
d0995cf7d3174f01425b2fba5e6320c7 mhmasksf27.exe
Tuesday, December 4, 2012
"Expired" Bug: CGI-DRG, VB-DRG, Access-DRG
A customer recently reported a bug to us which we have tracked down and are in the process of fixing.
The bug is this: if one used "Expired" as a discharge status in VB-DRG, Access-DRG or CGI-DRG, with the case described below, a bogus error was returned: code 5, "invalid discharge status."
Test case: primary diagnosis of 41071 and a discharge status of Expired.
Obviously, Expired is a valid discharge status: we had a bug in handling it. For some reason our mapping of Expired was explicitly not done for versions higher than 25.
We have fixed the bug and expect a re-release of version 30 by February 4th, 2013.
In order to validate our product, we used a DRG assignment app from another organization:
http://cs1.claimshop.net/grouper_demo/grouper_main.aspx
The bug is this: if one used "Expired" as a discharge status in VB-DRG, Access-DRG or CGI-DRG, with the case described below, a bogus error was returned: code 5, "invalid discharge status."
Test case: primary diagnosis of 41071 and a discharge status of Expired.
Obviously, Expired is a valid discharge status: we had a bug in handling it. For some reason our mapping of Expired was explicitly not done for versions higher than 25.
We have fixed the bug and expect a re-release of version 30 by February 4th, 2013.
In order to validate our product, we used a DRG assignment app from another organization:
http://cs1.claimshop.net/grouper_demo/grouper_main.aspx
Saturday, March 3, 2012
Access-DRG Versions
In order to keep up with MS-Access, we have had to split our Access-DRG product into two different products:
Note that this product is more-or-less useless without the VB-callable DLL, but the current VB-callable DLL is included with your Access-DRG purchase.
In the normal course of events, we expect you to buy Access-DRG once and VB-DLL subsequent year. You only need to buy Access-DRG again if and when Microsoft changes MS-Access enough to require a new app.
- Access-DRG/2003, which should run under MS-Access 2000, 2002 and 2003. This is the good old ".mdb" version
- Access-DRG/2007, which should run under MS-Access 2007. This is the new-fangled ".accdb" version
Note that this product is more-or-less useless without the VB-callable DLL, but the current VB-callable DLL is included with your Access-DRG purchase.
In the normal course of events, we expect you to buy Access-DRG once and VB-DLL subsequent year. You only need to buy Access-DRG again if and when Microsoft changes MS-Access enough to require a new app.
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.
Subscribe to:
Posts (Atom)