Friday, November 14, 2014

F32: New Windows Reference Platform

Between F31 and F32, Windows XP ceased to be supported. In order to keep our customer's data safe and to keep our systems up-to-date, we retired all of our XP boxes. Since our previous windows reference platform was a 32-bit Windows XP desktop, we had to retire it as well.

Our new Windows reference platform is a 64-bit Windows 7 environment running on a 64-bit processor.

To ensure backwards compatibility, we have included a 32-bit Windows 7 environment in our testing group.

To the best of our knowledge, there is no issue here but please let us know if we are wrong about that.

Wednesday, November 12, 2014

F32 New ICD9 Codes

To quote the official CMS site (,

There are no new ICD-9-CM code updates effective October 1, 2014.

F32 Support

This year's release has not gone well. It should be ready first thing tomorrow, Thursday, November 13, 2014, which is the latest we have ever released a grouper, and there is a known issue with the release (we are confident that the known issue will not matter to any of our customers, but we feel the need to document it none the less.)

First, we had to dust off our ICD9 technology which we had expected to have retired by now. Many aspects of this technology are different and out of date and resurrecting the development environment was more challenging than we had expected.

Then our lead engineer ended up in the hospital for a week just before our big release push, which has us scrambling do to the release. This caused the initial delay.

Finally, after the programming was done, our QA testing turned up the following issue: while our DRG Assignment Engine (DAE) returns the correct DRG in all test cases, sometimes it does not return the expected error code.

Specifically, our DAE does not distinguish shares of Hospital Acquired Condition (HAC) errors; it returns 9 when sometimes the CMS grouper returns 9, 11 or 15. So if you need to know more precisely how the HAC rules were violated, we currently cannot help you.

(If we discover from customer feedback that we are wrong and these distinctions matter, we will do a release to replicate the CMS error handling.)