I just want to comment about the concept of putting lines of code into the various revenue-generating packages in VistA.  I think that should be avoided as much as possible.  In RPMS the approach has been to put a special cross reference onto the Visit file (file 9000010) that flags the visit as having not been checked by billing.  Every night during off hours a background program runs to check all of the new and changed visits and checks all of the data elements in the various package that keep data that might be billable items.  Bills are generated in that way without requiring mods to the clinical packages.
 
Jim Gray
----- Original Message -----
Sent: Sunday, February 05, 2006 9:45 AM
Subject: [Hardhats-members] Billing Module for VistA

When VistA is installed in commercial hospitals and environments, how is billing handled?  Are there some examples that could be provided where a billing package was successfully added to VistA?
 
I would be interested in the approach taken by the billing softwares added to VistA by varous non-VistA projects.  I assume the approach taken is to...
 
*  Ad a billing package to accumlate data, create reports, and bills...
*  Place hooks (lines of code) in the various revenue-generating packages in VistA to populate the billing module.
 
If anyone knows, what strategies to billing have been taken by non-VistA users of VistA?
 
(If this has been discussed on other messages or other locations, and I can't imagine it has not, please just provide links.)
 
Thanks!

Reply via email to