We've recently upgrade to CPS 12, and we are slowly starting to notice a few patients won't load whenever we go to view their chart summary. It just has the loading symbol over the banner and all the windows say "Sorry. There was an error loading this data." Doing a MELTrace, UI Trace, and SQL Trace didn't really give anything out of the ordinary. Has anyone else seen this? I'm opening a ticket with GE and will try post what the resolution is if they find one.
I'm a little late to this post, but we have had the same issue. Our vendor found something in the database that was set to "Null" for each patient we were having this issue with. They created a script that took care of the issue. We still have to have them run it every so often though.
We use this script to fix it:
SELECT PID FROM PatientProfile WHERE PatientId = 'patient id here'
FindChartOpenIssues @Pid = (put the result of the select above here) //If something returns when running this script, run the next script.
UPDATE DOCUMENT SET confType = 0 WHERE confType IS NULL AND PID = (result from first query)
FindChartOpenIssues is a Stored Procedure that we had to create on our database.
Is the store procedure still avaiable?
Yeah, I posted it here:
I've used this script many times and has worked like a charm (much appreciated mikeseale). Today however, I ran the script and the chart still does not open. Does anyone have any other scripts up their sleeves that may work for the error; Sorry. There was an error loading this data?
Thanks in advance.
I have had one or two instances of this caused by some extra space or garbage characters in one of the registration fields. In our case, I believe it was the zip code. Also had a malformed zip code cause some problems with statement files being parsed by Emdeon - that was fun to troubleshoot.
So go to registration for this patient, delete everything out of the zip code (and try some other fields if zip doesn't do the trick) and then repopulate it. I am not sure how this situation comes about, but I have seen it more than once so it seems like zip code data is not properly validated at entry time or something happens to it later.
Turns out it was an error that had to do with flags. The following script fixed the issue:
select searchname, pid from patientprofile
where patientID = '' -- enter Patient ID
select * from FLAG where CONTEXTID1 = -- enter PID
update FLAG set STATUS = -1 where ID = -- enter ID where status is null
I will definitely check the zip code/registration fields when this error inevitably shows up again.
Thanks for the advice mdoak.
Probably unrelated to the zip code in your case if that was the script that fixed it. Very disconcerting that some stupid flag status prevents a chart from opening. I'm afraid to ask how long it took to get that resolved with GE. 🙂
I initially had a ticket in with GE but cancelled it because the head of our department had the script on hand so much time was saved.