V30 Bug

This post is an overview of an issue with the v30 DRG Assignment Engine (DAE) and our response to it. Related posts will have the label "v30 bug" in order to make them easier to find. This post will be updated as the status changes.

Current status (Oct 24 2:27pm Eastern)
The issue in regression testing under 32 bit Linux was hard enough to resolve that we upgraded the 32 bit Linux reference platform instead (for details, go here). While we were upgrading reference platforms, we also upgraded the Windows reference platform (for details, go here).

We have finished the in-house rebuild and revalidation of our products. We are currently rebuilding the products built using  a porting lab, at which point we will be ready to update our web site and start sending out free updates to customers. We have already begun sending out free updates to customers with standing orders.

History of Bug Fix

On October 11 at about 10am
Customer Service received a bug report:

One of our customers asked about a change in V30 that maps a dx of 487.0 with one 1 of 11 secondary pneumonia dx's to DRGs 177-179. In previous versions this combo would map to DRGs 193-195. She claims this change is in the specs of the final release. Our grouper is mapping this combo to the old DRGs of 193-195.

October 11 at about 10:30am
Tech Support punted this issue to Development.

October 12 at about 6pm
Development delivers a fix to Tech Support:

The problem was in the CC exclusion logic, requiring a change to the DAE, so all DRG assigning products will have to be re-released.

When the DAE was delivered the first time, you noticed that the test file did not do a very good job of covering the DRGs, and we said we would look into finding the latest one with better cover. which we did. When we ran against the new test file, there were over 200 mismatches. These turned out to be cases with more than 15 diagnoses or procedures. So we upped our limit to 25 which required changes to DRGFilt and it control file, cntl.f30.

Note that drgmasks.f30 did NOT change so you only have to redeliver the DAE itself (drgfilt, dll, shared object, etc).

October 13, various
Tech Support drew up their roll-out plan:

1. create this overview post
2. document a test case or two so users can confirm DAE status
3. revalidate product line with new DAE and new test DB
4. update our manual's "What's New" to reflect this bug
5. have Customer Service approve documentation changes
6. update web site with new products
7. send updates for standing orders
8. send updates for orders from the web site

Plan approved; plan execution begins.

October 14, various
Tech Support  continues executing plan.