Notifications
Clear all
Topic starter
We recently upgraded from CPS 10 to CPS 11.1. My providers are now intermittently getting an error message that states "Database: INVALID ROW retry?". This happens when they go to sign their orders. According to GE this has something to do with our custom form.
Has anyone else experienced this and if so have you been to resolve the issue?
Posted : February 7, 2014 6:15 am
I had that error once, it was when I was trying to write a large file (over 4000 characters) to a document variable. The errors and exceptions log showed an error in the symbol table. I switched the variable type to a global variable and the problem went away. It may be something completely different, but your description does fit my issue. If you have a display or are saving an orders view to an observation term or anything like that, that is where I would look. Goodluck
Posted : February 7, 2014 6:32 am
mwaters said:
We recently upgraded from CPS 10 to CPS 11.1. My providers are now intermittently getting an error message that states "Database: INVALID ROW retry?". This happens when they go to sign their orders. According to GE this has something to do with our custom form.
Has anyone else experienced this and if so have you been to resolve the issue?
We have seen that error message occur in 2 scenarios when billing codes are incorrect:
1. Behavioral Health providers using any DS4 code (old codes) from patient's problem list for billing. If they billed with the DS4 code as the primary dx, CPS crashed; if the billed with this as the secondary dx, the INVALID ROW message displayed. Clicking No allowed them to sign the note but billing did not go through.
Changing the DS4 code to a comparable ICD code and then resubmiting the billing order fixed this problem.
2. Medical provider changed a dx after he had added it to the list of billing diagnoses but before he signed his clinical list changes. This also caused the INVALID ROW message when he went to sign the changes - but this time it stayed in an infinite loop and we had to end his session - which left his note 'In Progress'. We could open the note and put it back On Hold, without signing clinical list changes.
The provider then went back into his note, cleared the dx list from his orders (which contained the code he had changed so the problem was considered inactive), and reselected the updated dx.
We've also seen some strange Drug Interaction pop-ups that are preventing signing prescriptions unless the provider does an override - this did not occur in CPS 10.
Posted : February 9, 2014 9:50 pm
