Hi
I have been lurking on this site for a few years....you post a lot as an expert...I am a pretty expert doc with Medisoft and Medilync, now struggling exploring 2kmobile. They have an EMR Spring Charts...any experience? I have done post-docs in physics at UCI and have had my work recently validated by the quantum computer at Los Alamos (google VIGOR-ZIERK) BUT if their IT people want to keep us barefoot and pregnant (eg by not telling us what the new registration key is every time the battery on the PDA needs to be changed, unless we pay them $200/hour-- or not telling us we need to download HCFAFILE.exe or HCFA11.exe) we might as well be barefoot and pregnant. I am going to be setting up several facilities and need to find out who has got the best PDA interface out there now that Medilync has been de-certified. Let me know if you want to exchange info. THANKS and Happy Holidays.
Carey M Vigor MD COHC
cell 586 615 4323
I'm having another go at this .. trying to access Medisoft v14 tables with ODBC but no luck so far.
It was said above that these tables are protected by a username and password, but I was able to use a shareware database browser called fast doc viewer to look at the tables with no problems. But I guess it doesn't use ODBC.
Graham http://www.synapsedirect.com/ Synapse - the EMR for smart users
gchiu: I'm having another go at this .. trying to access Medisoft v14 tables with ODBC but no luck so far. It was said above that these tables are protected by a username and password, but I was able to use a shareware database browser called fast doc viewer to look at the tables with no problems. But I guess it doesn't use ODBC.
What does this say about the security involved in this program? It's laughable enough that anyone who clicks on a silly trojan email could easily give up the information in that database to your basic unfriendly Romanian or Russian hacker.
martalli:What does this say about the security involved in this program? It's laughable enough that anyone who clicks on a silly trojan email could easily give up the information in that database to your basic unfriendly Romanian or Russian hacker.
Let me guess, you're got a random phrase generator to post replies to this board??
Here's a walkthru written by eriaac on how to setup the odbc connection and connect to MS Access.
I don't have Access, and I downloaded the ODBC drivers from the Sybase.com website. I was connecting to Medisoft V14 tables.
gchiu: Let me guess, you're got a random phrase generator to post replies to this board??
You may have missed his point, but perhaps he is a computer doctor.
But an unrelated question is if you have a program which randomly hacks vendor databases :-) Still 2 years is a long time to get it working lol.
caultonpos: But an unrelated question is if you have a program which randomly hacks vendor databases :-) Still 2 years is a long time to get it working lol.
Yeah .. 2 years is a long time, but priorities keep changing. If I can't get something working in 30 mins, I move on.
And the Medisoft tables are protected by a userid and password ...
Graham,
They may be password protected for OLEDB type interfacing, but you can still access the tables with a binary read.
Also, remember passwords in Medisoft are always uppercase.
Matt
Are you sure about that? I tried uppercase and it would not authenticate, but lower case works fine.
Now although I can get the demo data I created with Medisoft to work, I am getting this error with the user's real data ... using Access 2003.
Is this an indication of database corruption?
When we did read the database using OLEDB, I discovered that the password, no matter how it was entered from the keyboard, had to programmaticaly be changed to uppercase. That was some time ago. We had too much trouble reading the database in a consistent fashion and so I created a binary read. It skips the authentication/password protection issue. It's very fast. Essentially, there is an offset to the first record, a length to each field, and a total record length. If I remember correctly, there is also an issue with something like 64KB boundaries, but I would have to look at my code. The offset to the first record and record length for each version is different, but essentially the same code. It takes just a couple of hours of sluething to enable reading of another version. We handle 4 versions currently.
Nice work then
You can use ODBC or OLEDB. You will find the drivers for these on the Medisoft disk. Regardless of which way you go, you must log in with a username and password. Accessing by field offset would certainly be a hard way to go when you have a data dictionary and OLEDB at your fingertips.
Gavin S. Walker
MedTech Medical Management Systems
3113 S. Pickwick Place
Springfield, MO 65804
417-890-6777
www.medtechsys.net
The Best is Yet to Come
I think my problems happened because the software is somewhat flaky.
If you don't have the right combination of odbc drivers and local server, you can get into problems. Or maybe because it's because my test machine is using Vista business.
I did a fresh install onto a clean XP machine and then had no problems accessing the data thru ODBC.
And essentially that is the problem we had. We needed reliability from any machine on the network and we needed that reliability without having to call in a network admin to download drivers and fiddle around to get it right. Thus, we created our binary read. Sure it took some work on our part, but we don't charge extra for support and so, had to go with reliability over ease.
I've written a little test program that opens up an existing ODBC DSN named "medisoft" and prints 10 records to the screen. It also then tests the synapse odbc connection ... but you can ignore that.
It works on Medisoft 14 ... anyone wish to try it on earlier version?
It can be downloaded from here.
If your ODBC DSN is not setup correctly, then of course it won't work.