Notifications
Clear all
Topic starter
Since we upgraded to SP11 we have had a number of incidents in which MEL code is showing up in charts, forms, and other documents. Occasionally, signing out of Centricity and signing back in will correct it, but generally it requires discarding and starting over. Anyone else experiencing this?
Thank you all,
Steve
Posted : January 8, 2016 5:17 am
sounds like you are losing connection to your CCC forms files that are required to display the CCC translations properly
Posted : January 8, 2016 5:21 am
We found out the hard way but I think acantu is right. We never uses nor installed the CCC basic so on this upgrade all our other forms including the ERX would not work until we installed the CCC basic.
Posted : January 8, 2016 5:51 am
Are these by chance custom forms created with VFE? We had a couple of odd things with a couple of our forms right after we upgraded and I think this may have been one of the issues. I ended up opening the problematic form in VFE saving it again, so that it saved against SP11, and then imported it into Centricity. I did not make any changes to the form, just saved it again. For new visits, it resolved our issues. For any existing visits with the issues, I just right clicked on the form inside the visit and clicked on "Get latest version".
Posted : January 8, 2016 6:11 am
We use all custom, we see this issue on thin client users. Resetting the profile seems to fix it temporarily. Not sure of the cause though.
Posted : January 8, 2016 6:46 am
you might need to re-import the custom forms then.
Posted : January 8, 2016 6:50 am
Topic starter
Great thanks everyone this gives me some things to check. The issue is with the CCC forms. I'm not aware of anyone having issues with our custom forms.
Posted : January 8, 2016 8:06 am
since upgrading to SP11 we have had issues with forms not importing correctly or breaking the connection with the new document template when updated. I have also seen it tell me there was "too much data and it wasn't going to sign the document" or something to the like but then I go back into the document and it is signed.
Posted : January 8, 2016 8:59 am
We've experienced this on prior versions of Centricity and also on 12.0.11. This is fixable by removing the form component (this will not remove any clinical list notes that have previously been added) and then re-adding the same form to the encounter. This will remove the improper MEL code and re-add the selected text in the note.
Posted : January 8, 2016 11:02 am
I have seen this issue on our DEV environment. I had them re-import the CCC forms and it solved the problem.
Posted : January 13, 2016 6:14 am
VFE form structure is not different from one version of the EMR to another; it is a myth that it matters in this regard. What does matter with regard to EMR version is the connection for data lists that are used in VFE and how VFE connects to retrieve them. Beyond this connection, VFE could care less which version of EMR your forms are to be used in.
The real issue is that the service pack has adversely affected several areas in the EMR itself:
1) Broken data symbols
2) Corrupted table rows
3) Changed initialization procedures
4) Refresh cycles gone wild
etc.
By 'resaving a form', as GE Support often recommends, you finish by re-importing the form, which is what 'cleans up' the corrupted table (doc template, forms, etc.). Essentially, re-importing each form 'cleans' up the' bad table row for that item, so the advice is sound with regard to re-importing.
You can typically skip the 'resave in VFE' step, unless the form is an old build, especially EFE built forms, which do not use the newer form structure and can be problematic. For those, re-saving in VFE is advised anyway so no loss of time there.
Note that the above list of items can also cause 'mel garbage' to appear in the chart note and adversely affect performance, so if re-importing does not 'clear up' the issue, you will need to look deeper in the form code and determine if it is possible to compensate for the service pack induced defect.
Hope this helps clarify, but understand that it does not remedy the issue that corrupted the table in the first place meaning it might resurface again unless GE can provide remedy.
Posted : January 14, 2016 5:08 am
Topic starter
Hi All,
Thank you for the tips. While this question pertained to the CCC forms we did find an issue with one of our custom forms where MEL code appeared. It was finally tracked down to the Entry-CCC form being added to the visit. I haven't had a chance to do more testing to see why that would cause the issue, but thought I'd post it for others.
Thank you,
Steve
Posted : January 14, 2016 5:47 am
You mention the Entry-CCC form. I do see that the Entry-CCC form is one of the forms that is fixed in the newly released CCC Basic v1.4, might be worth you looking into getting applied to your system.
Posted : January 15, 2016 8:05 am
