I'm currently discussing the integration of MS Access with AllScripts, and they are currently trying to work with a CCR to accomodate non-AllScripts users of eRx. I've suggested doing an ODBC link (comes FREE with MS Office), but they told me that the table structure is proprietary, which is c-r-a-p. They only need to open 2 tables at most (patient info and medications). Here is my latest letter to them:
----------------------------------------------
[Ruth Hummel <erxnowsupport@allscripts.com>]
[tel 888.379.6691, contact us:
http://www.nationalerx.com/contact-us.htm]
Dear Ruth:
The only problem that I see with the CCR is that with the many dozens of prescriptions that are sent out daily, having to do the extra step to export the data to my EMR could make the use of CCR impractical. An ODBC connection would be more practical, and can be achieved without compromising the table structures of AllScripts.
For example, the prescription data can be sent automatically to a couple of tables outside of AllScripts (ie the patient data and prescription data tables) which can be mapped using the free Microsoft ODBC to enter it into MS Access. There are several folks over at Amazing Charts that likewise would be very interested in this approach.
Sincerely,
Dr. Borges
----------------------------------------------
I hope that this idea catches on...
Al