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

ePrescribe Duplicate Key error message

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

7 Posts

5 Users

0 Reactions

69 Views

RSS

mcwilson

(@mcwilson)

Posts: 92

Estimable Member

Topic starter

Ever since our SP11 upgrade we have been randomly (after hours) getting flags from a user named Electronic Prescriptions with the following message:

Violation of PRIMARY KEY constraint 'PK_FMYCOVAGEDETAIL'. Cannot insert duplicate key in object 'dbo.FMYCOVAGEDETAIL'.

As an example, yesterday evening around 7 pm we received 5 of these flags.

Has anyone else seen these? Were you able to get them to stop?

Thanks,
Mike

Posted : December 30, 2015 7:01 am

JBell

(@jbell)

Posts: 285

Honorable Member

This is a known issue - here is the notification from GE. I get an email notification from [email protected] each day with this notification.

Hope this helps

Updated 12/29 - Note: Clinics may currently be getting several "Violation of PRIMARY KEY constraint 'PK_FMYCOVAGEDETAIL'. Cannot insert duplicate key in object 'dbo.FMYCOVAGEDETAIL'" flags in regard to formularies that cannot be moved from the Centricity staging tables to the production tables. No additional cases are needed to assess the concern at this point. Surescripts Enterprise Services believes the PBM (Pharmacy Benefits Manager) published a malformed formulary file, and is evaluating options including asking the PBM to stop pushing the file. Note that this does not affect the ability of your clinicians to e-prescribe, only the ability of that formulary to be updated. We will provide an update when we have more information on the cause and remedy timeframe to this situation.

Posted : December 30, 2015 7:06 am

Sibylle Freiwald

(@sibylle-freiwald)

Posts: 67

Trusted Member

I have gotten the same flags and was told by our VAR not to worry about them, to just remove the flags.

Posted : December 30, 2015 7:13 am

mcwilson

(@mcwilson)

Posts: 92

Estimable Member

Topic starter

Thanks Janet!

Posted : December 30, 2015 7:19 am

tcross

(@tcross)

Posts: 165

Estimable Member

Brian Balloon addressed this as well. It is a known issue and GE will let us know when it is corrected.

Posted : December 30, 2015 8:29 am

Marketing Committee

(@marketing_committee)

Posts: 358

Reputable Member

jbell, thanks for posting. I went from getting 1 or 2 a week to 5 or so a day. I had asked my VAR about this a couple weeks ago they thought it was fine to ignore but I was still a little considered by the the extra.

Posted : January 4, 2016 5:30 pm

JBell

(@jbell)

Posts: 285

Honorable Member

Brian Balloon is still sending out notices from GE so this still is an on going issue. Just FYI.

thanks!

Posted : January 6, 2016 7:35 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