Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

V20 Med Management Synch Error

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

4 Posts

4 Users

0 Reactions

72 Views

RSS

cstephenson

(@cstephenson)

Posts: 33

Trusted Member

Topic starter

We are preparing for our V20 upgrade and have been working in the Medication Management module in our test environment. When trying to do anything in the module, we consistently get the following error in a popup window: "Receive medication/prescription synch failed. Please launch the medication portal window." Once you get this error, you are caught in a continual loop and can't sign or delete the document. I talked to another practice that is already live on Medication Management and they said that either Smart Sig needs to be clicked/run in the module to update meds or there is an error with an old med and it does not fully synch with the chart for some reason. I added new medications on both test patients I was working with and still got the error, so it is unlikely related to either SmartSig or old medications.

The other practice said they have to submit a ticket with Athena to get it resolved (not an option to do it themselves) so they have a lot of documents in limbo while waiting for a response. Once we go live, this error will cause a nuclear meltdown in our practice. We also use a VAR that is slow to respond to support tickets which is an additional concern.

I was wondering if anyone else has experienced this error and if you can give me any further insight.

Thanks!

Posted : May 20, 2021 2:55 am

JBell

(@jbell)

Posts: 285

Honorable Member

We are receiving the same error in our three test databases. It seems to have just started yesterday and is continuing today. I am not sure where the issue is at this point, but it seems suspicious that we are having the same issues you are in our test environment.

Posted : May 20, 2021 4:20 am

nonageyer

(@nonageyer)

Posts: 50

Trusted Member

We are slated to migrate July 1. Not looking forward to this.

Posted : May 20, 2021 10:27 am

MHSITECH

(@mhsitech)

Posts: 3

Active Member

This error occurred in a test patient while a provider was prescribing a controlled substance to make sure her token worked. We opened a ticket with Athena.

Posted : June 30, 2021 9:53 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0