|
tkFP changes
|
Alexander Caldwell
|
Oct 23, 2008 08:14 PDT
|
I guess it's winter coming on, because I have been getting the urge to do some programming changes on tkFP. The Moka5 virtual PC version of tkFP that I made using Moka5 and Grafpup is available from the Moka5 site http://www.moka5.com/ It is in their demo library of virtual PCs on page 7 of the library. I will try to keep it up to date with
the latest changes. I am using the Moka5 version daily in the exam room on a laptop connected
to my main server up in the front of the office. Moka5 is quite stable and much easier to install
and set up and maintain than the coLinux version, although, I'm still using coLinux
on my tablet PC. Moka 5 takes care of all the networking issues that have to be set up by hand in config files in the coLinux version.
I recently fixed an issue where the list of fax recipients that is in the choice menu
on the prescription page was only loading from the local machine instead of getting
the data from the central server. This has been fixed in the Moka 5 version. You can
add new fax recipients and their fax no's by right clicking on the fax recipient button
making the addition to the file and saving. The data will be saved to the main server
if you are on a network client tkFP machine.
The new CMS 1500 forms print out nicely. I have been having it print both the new
NPI number required and the old legacy provider PIN in box 24 E but will likely
remove the old PIN from the printouts soon, as Medicare does not want them
included any longer.
Another small item recently fixed was the incoming faxes listbox would not refresh
if you deleted a fax and there were any fax file names with a + character in them. This
is pretty rare, but I did have somebody send me a fax with a series of +++ in the number
and it caused a problem because the + symbol is special to the regular expression
pattern matching that is used to compare file names. It would raise an error and the
listbox would not refresh after deleting a fax(s) from the inbox. There might be other
symbols that if somebody put into their return fax no could cause the same problem,
such as possibly a . but if we run into any of those, it should be easy to fix using
the same technique used to fix the + problem. But I only ran into the + problem after
quite a few years of faxing, so it should not be too likely to crop up.
Alex Caldwell
|
|
 |
|
