Does anyone have experience with AthenaOne? Our practice is considering switching to it instead of just doing the Centricity v20 upgrade for EPCS. Does it work with VFE? Do the upgrades work as easily as stated?
I do not have any experience with athena One, but my understanding is that Athena One is the cloud based offering, the classic athena product. Therefore it would not support VFE forms, and the upgrades would be handles exclusively by Athena. I would love to hear the experience of anyone that has completed or started down the path of that migration though.
we explored this. we are a small practice and run on a shoestring IT budget and found it cost prohibitive.
it does not work with VFE. it is a completely different solution, and completely hosted.
they also do not migrate all of your data, only a small portion of the data. they host the rest of your data in an archived format that i didn't find too useful that is provided by a third party (ELLKAY) for as long as you want to pay for that service.
Kristi,
I'm going to answer your question the best I can, but also use it to get something off my chest. I apologize in advance for my cathartic ramblings.
Experience with Athena One: No direct experience, but several of our staff members came from a practice that used it. They all hated it, but admittedly, their evaluation was coming from the administrative side (i.e. practice management functions like scheduling, billing, etc.). Athena was built from the ground up to run in the cloud and their business model was focused on getting medical practices to outsource their billing and revenue recovery functions to them. Their marketing leaned heavily on their ability to detect claims that would likely get rejected and their "rules engine" which could magically prevent this from happening. Their EMR seemed to appeal to practices that either didn't have a strong back-office or had no interest in building/maintaining one. While their "rules engine" was touted as revolutionary (this was more sales speak than reality), it could not compete with a well-managed back-office. As far as an EMR, I suspect it captures the basic elements of a progress note via a lot of pointing and clicking and the level of customization would not be anywhere near what you can get out of Centricity. I personally have experience with a multitude of EMR systems and they all pretty much have their pros and cons, but the level of customization/configuration you can do with a cloud-based EMR will generally be significantly less than what you could achieve in Centricity's client/server system. Just to be clear, I recognize the move to the cloud is inevitable for all EMR systems, and any business application for that matter - so anyone reading this shouldn't put me in a box labeled ("fears change", "tech dinosaur", "boomer", etc.) - more on that later...
Does it work with VFE: Unfortunately, no. While Athena One may have some "configuration tools", Athena One and Athena Practice (Centricity) are two completely separate products, and VFE was actually developed by a third-party company to make some pretty sophisticated customizations (relatively speaking) accessible to a non-computer programmer. Again, the level of configurability and extensibility you will be able to achieve in Athena One will pale in comparison...that is, until Athena One provides a robust API (application programming interface) that is made accessible to end users.
Do the upgrades work as easily as stated?: Not sure what information you have read/heard, but since Athena One is a cloud-based application, upgrades are generally handled by the service provider...so yes, they should be easier on the end user. This is a god-send to anyone in IT that normally has to perform the upgrades, but also a huge curse, because you literally will have no control over the deployment of new features, AND you will have to rely almost 100% on the vendors support options. Translation: expect unhappy physicians and users that are used to in-house IT, because big VARs and parent EMR company support channels will never be able to respond as quickly and thoroughly as a strong internal team.
<begin rant>
Herein lies the issue I have with Athena Health, and for that matter, pretty much any private equity group that purchases healthcare IT vendors. I personally feel that Athena Health is not as transparent as they ought to be with their roadmap and long term strategy; not to mention their lack of customer engagement (and don't blame COVID). I've attended several of their townhalls and was at the infamous CHUG conference in 2018 when the rumors started flying about a PE purchase of Centricity. I won't go into it, but let's just say it was very poorly handled and communicated. I'm sure anyone who was there would agree if you were to ask them. No matter how many times we are told that two products will continue to be supported (in our case Athena One and Athena Practice), I can almost assure you that their end game is to get everyone on one product. To do otherwise simply wouldn't make sense to the private equity group; the PE's MO will always be to get a decent ROI within a reasonable timeframe. Maintaining two separate products, two different cultures, two different development teams, two different sales and support channels, and on and on, is just too costly. The PE firm went after Centricity and Athena likely because of the number of customers/subscribers and the potential ROI they would generate (internally or by selling to another PE firm down the road) if they could consolidate all the users on one platform. Like it or not, that's how this game is played. Predictably, the social engineering tactics have begun, and they will continue until Athena can safely announce that Athena Practice (Centricity) will no longer be supported as of (insert some date here that is only known by the private equity stakeholders). If I had to guess, I would say this will occur around the 2023 -2024 timeframe. I certainly understand why one might hold things close to the vest; fearing a mass exodus if the word ever got out. I would just argue that that "fear" is unfounded. Perhaps some customers would leave, but probably not as many as one might think, and certainly not as many if Athena did a much better job of engaging their customers in the design/development/transition process. As I mentioned earlier, I'm not upset about the move to the cloud or the innevitable changes coming down the pike; I'm all for progress, especially in an industry that is in desperate need of transformation. Deflecting or recasting the "tough" questions only exacerbates the frustration we all feel, but that's exactly what you get from Athena Health, which is no different from any other PE firm I've had the "pleasure" of dealing with :).
<end rant>
My only advice would be that if you or anyone is seriously considering transitioning from Centricity to Athena One, do yourself a favor and look at other cloud-based EMRs as well. Don't think for a minute that just because the two products are held by the same company that somehow that will magically make the transition less difficult.
Cheers and good luck,
Greg
We switched from CPS to AthenaCollector/Communicator with GE Centricity for EMR in 2013. And then made the change to AthenaOne in October 2020.
We are orthopedics, so it made it easier in some respects.
I am happy to talk to anyone who wants to discuss the experience.
I would love to talk with you more about your experience, esp from a documentation standpoint. We have a lot of efficiency built into our VFE templates and losing control over this is a big deal in my opinion. I'll reach out to you via email.
Thank you for taking the time to give such a thorough reply. It made me laugh and cry a little lol. I'm sure that cloud based systems are inevitable, but the current offering from Athena seems dismal from a documentation standpoint. We watched a demo yesterday and didn't see any hint of Centricity within the AthenaOne product. If you are correct and the end game is to phase out Centricity, I'm not sure what the purpose of acquiring it was if they are not going to build off of it or integrate it at all.
We have a lot of efficiency built into our VFE templates that does not seem possible to achieve with AthenaOne. Their "custom templates" look like little more than quick text phrases with free text blanks for variables. No one could answer my questions about how data is saved and pulled forward. I assume they do not use obs terms and therefore do not give any control over saving data/viewing like VFE allows. In my opinion, the loss of efficiency in documentation could be significant enough to cause a loss of revenue greater than the cost savings of the rest of the product.
I do not have an IT background. I'm a clinical end-user that has learned VFE and has no other programming experience, so please correct me if I'm wrong....I would assume that the move to cloud based systems will probably require any future documentation APIs to be html format? And those typically run off JavaScript? I attended a Clinical Forge class and was impressed with the product but felt like it was beyond my ability to use without further programming training. I wonder if they plan to work with AthenaOne (if allowed). I have been told that VFE would like to but it is not currently in the works.
Good to know. This detail was conveniently left out of the demo
Just an update to my original post. Here we are 5 months later and functionality of the Athena Practice EMR continues to take steps backwards in usability, reliability, extensibility, and maintainability. Our VAR (the largest reseller of Athena Practice) seems to be right on schedule with my predictions. See the email I received in my inbox today...
Bless their hearts. Thank goodness they didn't include the word/phrase "transformational" and "new normal." I think I would have had to puke.
For better or worse, our practice is married to Athena now as well. We are planning to go live early next month. I'm actually going to spend the next hour and a half trying to make sense of documentation build. Wish me luck