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

FormularyStagingToProduction

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

2 Posts

2 Users

0 Reactions

69 Views

RSS

jennifertyson

(@jennifertyson)

Posts: 26

Eminent Member

Topic starter

Received this failure flag this morning. I havent received any formulary failures before. Can anyone explain what this is and how I can fix? Thanks for your help.

Failed FormularyStagingToProduction: Move formulary data from staging to production table failed.;
Data source file = BCBSIL_20180801_20180801_P00000000020147_COV_QL ;

Posted : August 16, 2018 4:53 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

We figured out what was going on. I'm putting it here because it was really frustrating to come to CHUG and see a question with no comments/answers about the issue we were having. Figure putting our solution here helps everyone. Rising tide and all that.

I spoke with our vendor and she told us that this is a flag from the eScripsMessenger update that happens nightly. What likely happened was there was something else happening in our database at the time that caused a conflict. Our flag was sent at 2:32 AM, which is around when we backup our databases, so what probably happened was something took longer than it should have, and the schedules were thrown off.

Most importantly, she told us that if we hadn't seen the error since then, there wasn't a problem. Each night, the new import will pick up anything missed from the previous attempt and include it, so we didn't lose any information.

Hopefully you aren't still having the problem, but if you are, it was recommended to us that we work with our vendor to tweak our schedules to prevent future conflicts.

Hope this helps someone in the future!

Posted : December 10, 2018 5:19 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