Provide VBA code to format data in ANSI 837-4010A for medical office billing, testing compatibility with one major payer to their acceptance of the file format.
You should already be familiar with the format, or be prepared to teach yourself. I will NOT teach you the format, explain the format to you, interpret what the format means; that's the ONLY part I'm paying you to do. All the infoI have on the format is in the zip file, in the .xls and .pdf files
Data is in a query in MS-Access97 database front end with MS-Access97 database back end. This application is up and running successfully and generates paper HCFAs.
Our major payer wants us to transfer the ANSI837-formatted data as a file on their secure website, or by direct dialup, so encryption is not needed.
Your job is to provide VB code to format the output of the existing query to ANSI 837-4010A.
I'll take care of sending the data file to the insurer for testing.? You will still be responsible for modifying the code to satisfy the insurer's requirements.?
The attached zipfile "ANSI837Open_frmParamReportsHCFA .zip" has the 'front' database with the form "frmParamReportsHCFA" that allows us to specify the charges to bill, the query that actually contains the data for the HCFAs ("qryHCFApaper") and the output format ("rptHCFApaper"). The 'Data' database is 'offiback'. The names and other identifying information have been scrambled so as to be not identifiable, but is otherwise live data.
You should know how to use the linked table manager in Access to link the two databases. Open frmParamReportsHCFA, select some claims, press the 'print selected' button and you will see the report. You can enter edit mode to examine the query and its output.
Database generally conforms to Reddick VBA naming conventions.
_1) Fully functional and commented VB code (to run behind a button on MS-Access97 database form) to create ANSI 837-4010A-formatted data file from data in (SQL) query in MS-Access97 database.
2) Testing compatibility with one major payer to their acceptance of the file format. Code should be able to handle multiple claims on one person, multiple claims on multiple dependents, etc, as specified in ANSI 837-4010A.
3) Data fields such as name and address of insurance company must be taken from query, not supplied as constants (of course). 4) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site).
END OF DELIVERABLES
Following info is FYI
_Since I'm in a one doctor office and can continue to submit claims on paper after Oct 15, I am NOT bound by the Oct 15 2003 deadline for HIPAA compliance. While I'd like to have this done sooner rather than later, I imagine the testing process is getting a little hectic right now, and the payer might not be able to do testing quickly.
_Testing with other payers would be an additional project, if necessary._
_This is the first deliverable; the next is being able to view the online claim submission reports, member eligibility, and online claim status reports, all coming back from the insurers in ANSI 837 format. It seems to me that the simplest would be to write incoming data to an appropriate MS-Access97 table and create a form to view it._
_I plan to eventually move the back end to PostgreSQL, and am considering the best eventual front end, e.g. OpenOffice. I?d like to move away from Micro$oft. This will also provide an opportunity to clean up minor problems and add functionality._
_You should be familiar with the ANSI 837 formats, or be willing to figure them out on your own. I don't mind if you aren't already familiar with them, since they are tedious but not complicated, but developing that familiarity would be on your own time. I'm not doing this myself because I think the time for me to learn the ANSI837 format could be better spent by someone who has a chance to reuse that knowlege. If you already know the ANSI837-4010A-format this should be a breeze._
_( Since you didn't develop the application, you would want to know that the database is normalized, tables have appropriate indexes and keys, many-to-many joins are broken into two one-to-many joins with the necessary linking table, etc..)_
_Runs on WinNT4