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

To much data in the field error

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

8 Posts

5 Users

0 Reactions

64 Views

RSS

Adam Daniel

(@adaniel)

Posts: 524

Prominent Member

Topic starter

We are hearing about users getting an "To much data in the field" error, we can't seem to duplicate it. We are hearing it is happening in the orders module. Anyone out there know what causes this or has seen it?

Posted : October 29, 2014 3:17 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

I have one user with the same issue, been like that for months.

and GE has been unable to solve this issue.

Posted : October 29, 2014 3:57 am

jhuckaby45

(@jhuckaby45)

Posts: 65

Estimable Member

I have multiple providers that receive this when entering orders. GE has said it's a known issue the spr is CISDB00059398. It seems to happen when they have several orders in for that update. Once the error occurs you can't remove the orders and try again you have to open a new update and put in your orders. If you're having this issue please open a ticket with GE and get attached to the SPR. The more practices attached to an SPR the more attention it gets.

Justin

Posted : October 29, 2014 4:10 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

I have had this issue since we upgraded to CPS 12 6 month ago.

GE have not come around with a solution neither have spoke to me about that SPR CISDB00059398

Posted : October 29, 2014 4:12 am

Adam Daniel

(@adaniel)

Posts: 524

Prominent Member

Topic starter

Thank you! Saves me a call to tech support now I we will just make sure they add us to the SPR.

Posted : October 29, 2014 4:14 am

lic08

(@lic08)

Posts: 286

Reputable Member

we have this issue since cps12 upgrade which was about 6-8 months ago. No solution yet. I found a user who had the same issue. They modified one of the field in the db to accept null which solved their problem but GE step in and said that field was changed in cps12 to not accept null on purpose. not sure why though.

Posted : October 30, 2014 4:01 am

vmackenzie

(@vmackenzie)

Posts: 4

New Member

We are having this issue as well, but for us it seems to be prompted by the past use of DSM codes in the ICD-9 field. The codes are formatted with DS4-##### which seems to be too long for the ICD-9 field in 12. Removing the old code and adding the correct ICD-9 problem codes corrected the issue for us.

Posted : January 15, 2015 8:41 am

lic08

(@lic08)

Posts: 286

Reputable Member

Hi vmackenzie,

This is still a major issue for us. If you can further explain and maybe show me step by step on how you resolve this issue or maybe lead me to the right direction that would be great. Thanks.

Posted : January 15, 2015 11:47 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