Home Forums Discussions Problems X-Link caution

Have owned x-link license for about 18 months; well before we started using AC. Purpose was to link our previous EHR with our practice management software, Advanced MD. Started with Version 8. Cost about $1000 for a 1 provider license, plus extras for continued tech support. In the end, we discontinued the use of that first EHR and x-link both due to a variety of technical and stability issues.
Along comes AC, which has apparent x-link compatibility. Dusted off my Version 8, only to discover that it was obsolete; I needed version 9. Few more hundred $$ for the new version and for 60 days of tech support. (this is pricing for only 1 provider; tech support beyond the 60 days is more money.) Interface was installed and worked as desired (one way from advanced md to AC) for a while. Small version changes would break the interface, but they have an online upgrade function that overcomes that if you do the upgrade every couple of weeks. That capability is also time-limited: 6 months. After that you have to buy continued access to that service.
Now for the last straw. Advanced MD does a significant version upgrade - the interface is broken. X-link online upgrade doesn't fix it. Find out I need the next version: #10. Another few hundred $$ These guys are making microsoft look good.
Talked with AC since they offer the software and support. Asked about pricing. Got a straight answer for support: they will provide supprt for the "current" version as part of the annual tech support fee. What about upgrade costs? Not sure; we'll get back to you... haven't heard, but note that the version upgrade (9 to 10) is priced at $500 on the AC licensee web site (and I think that's per-provider.)
In our setting fortunately we only need limited demographics for the AC records, which we can accomplish with only a little more work by the receptionist. So , I've taken down x-link. It's a money pit; the software that keeps on taking both money and time. Wanted to share my cautionary tale.

This constant up date by one vendor or the other that then colapses or upset the balance of these interfaces is a common tale of of horror that I've heard many times before. That is why the only true solution to these issues is to have one seamlessly intergrated program that incorporates both needs in one package. A single vendor knows both sides of his/her product and can and must keep them properly compatible with each other. Jon said that this was going to be his next major job after completing the release of what we all have now. So I would hope that after taking a bit of a well needed breather after bringing out 3.69, that is what he will start attacking. So I would gather that a PM will most probably be the next Beta that comes down the pyke. Thanks for sharing your cautionary story and experiences. These are the type of things we all need to share to better our experiences here.

OK. Now I know not to use X-link for anything. Ever. Thanks for the warning.