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

Repeatable Chart crash that goes away the next day

Bugs, Known Issues, Open Cases

Last Post by Anonymous 1 second ago

5 Posts

5 Users

0 Reactions

64 Views

RSS

dougmcilvaine

(@dougmcilvaine)

Posts: 7

Active Member

Topic starter

Hi, We are on 12.0.6, but this crash has been around back to CPS 11 anyway. Chart crashes when trying to sign a document with “Application crash Error occurred in class , method CEndUpdateDlg::OnHold The parameter is incorrect.” Support says it is a know defect SPR 56411 to be fixed in 12.1. This crash goes away the next day without doing anything. What occurs overnight to “fix” the crash is a mystery. One support engineer mentioned they thought the daily – centricityps job fixes the environment, but that was debunked by another engineer. Anybody else getting this scenario? It is tough telling a clinician to just wait a day and the problem will fix itself!! Thanks.

Posted : December 5, 2014 7:07 am

suefox51

(@suefox51)

Posts: 113

Estimable Member

Our providers are getting it all the time - we are on 12.0.5. We too have been told it's a known defect with no fix date set. And, yes, the next day they can sign it - we were told the work around was to wait a day and then sign. No one can explain why this works!
I feel your pain!

Sue

Posted : December 5, 2014 8:56 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

it goes away because the database Agent run the stored daily stored procedure.

either one of the bold text is doing the work for you.

i think either one of the clean or purge jobs is doing this for you..

1   Check expiration dates.
2   Clean temporary print tables
3   Record high water mark
4   Clean flag table
5   Reports

6   Collections
7   Payment Plan
8   Cleanup Search Tables
9   Remove Old Slots
10   Purge PI Log Table
11   Prune Errorlog table
12   Clean CEM Event Queue
13   Clean CEM Message Log
14   Inconsistent_ClinicalData
15   Disable Statisics On GT Tables
16   Job History

---------------------------------------------------------------------

1 Reset Cache

Posted : December 9, 2014 5:08 am

clafty

(@clafty)

Posts: 37

Trusted Member

Anyone hear anything more about this? We just upgraded to 12.0.6 and we're getting this with one of our providers. GE just told me the same thing above. He didn't know when the fix was being completed.

Posted : December 18, 2014 8:12 am

denabottoms

(@denabottoms)

Posts: 12

Eminent Member

We are on CEMR 9.8.6, and we have been getting the Paremeters are Incorrect error since our upgrade. I was given the same answer with waiting 24 hours and then try to sign. This worked once, the rest of the time I call platform and they have to unlock a master lock that has been placed on the chart due to this error. I also found that it usually involves a medication that was duplicated or changed during the office visit. I also found that if you have a different authorizing and signing provider on a prescription, you will also get this error. Once the master lock has been taken off, the provider usually can sign without any issue. A few times, I have had platform set the document as unsigned and then the provider can sign the update. I only do this if they cannot sign after the masterlock was removed.

Posted : February 17, 2015 9:21 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