I believe this is a bug that was fixed in version 7.1.3, then broken again in version 8.2.2.
We were told at recent Washington State Users Group meeting in Seattle that it was on the list to be fixed in version 8.2.3. They were projecting a release date for that version "hopefully in 2 or 3 weeks." That would be about now.
I am waiting impatiently for version 8.2.3 to go ahead with the ICD10-compliant upgrade. My staff wants to get their feet wet with ICD 10 and not wait until the last minute (something I'm notorious about doing). Anyone using the beta of 8.2.3, how does it look?
