Notifications
Clear all
Topic starter
Received an email on Friday that Service Pack 3 for CPS 12 has been released. I don't recall SP1 or SP2, but I think they released those for EMR 9.8 (not CPS) so maybe a weird naming convention or something?
Anyway, it promises to fix issues with printing preferences not being remembered, problem search, super long clinical visit summaries, and a whole bunch of stuff with CQR and CCDA (if you've been able to get it implemented unlike us).
I hope to get it applied at least to a test database within the next few days and verify if these things are true.
Anyone else apply it yet?
Posted : June 8, 2014 1:33 pm
we just did it over the weekend. Search for problem crashes cps every time. very unhappy doctors. working with GE to resolve this issue...
Posted : June 9, 2014 2:01 am
Topic starter
Not sure if this is the issue you are having, but I have seen similar.
See the "Known Issues" in the release notes.
I've broken ours on multiple occasions and I've had to do the uninstall/re-install dance with the website/JBoss to get it back to a working state. Of course then I have to put back in patient portal content, HTML CCC-Basic content, Document Management content, etc so it is kind of a pain. I am unsure if the other workaround they listed will work, but maybe you can test it out and report back. I will try to determine whether it works or not the next time I break ours.
The other thing I did that broke our Problem Search was I edited the "Caption" line in the config.xml file of the <websitename>.war directory. We have done this for years and years dating back to the Millbrook days to put the name of the practice in the title bar of the Centricity client windows. It was helpful for us since we have users in our central office with multiple Centricity practices open at once. Now it is kind of a pain telling them apart since I am unable to do this anymore. I am not sure this was ever truly supported, but it's something we did for a long time that definitely caused a problem on CPS 12 with the Problem Search. Hoping maybe the ability to set that without breaking stuff will return in this service pack or a future one.
Posted : June 9, 2014 4:32 am
Yes that's exactly our issue. We had to reinstall jboss in the past. you figure by now it should resolved.
Posted : June 10, 2014 5:24 am
Topic starter
Finally had a chance to get this installed on a test copy of one of our databases and I can confirm that two fairly large issues are fixed in this service pack so far:
1.) The ability to save printer preferences between user sessions (and also have it display in the Preferences Dialog Box properly) has returned!!!
2.) The problem search is much improved over anything seen previously in version 11 or 12. I am not sure if it is 100% what people are looking for yet, but if you put in something like "pain" you will get anything that CONTAINS the word "pain" and not only the things that BEGIN WITH "pain." I still think there is probably more work for them to do with regard to synonyms or something so it is easier to find what you are looking for, but what they've done here is at least helpful. In my opinion, searching for a problem in the chart should nor rely on the code being loaded on the PM side. Right now, it seems like anything that is not loaded in PM is set to "inactive" in the chart and that is kind of lame for providers. We don't have many instances of that, but we've had a few.
Just these two things alone make this a fairly high priority for us to get applied to our databases. There are also literally dozens of things related to CCDA and CQR that are supposedly fixed, but I can't really test those.
One other fix I tested was with the FixGroupIDs script that you are supposed to run after the upgrade to 12 to prepare for CQR. With the first release, we had it work on two databases (one with an empty EMR and the other a very small practice) and fail on two databases (larger dbs with lots of EMR data). Support gave the not helpful answer of "it must be something wrong with your database" and we've been waiting for an answer for a month. It turns out that the condition that caused the failure was if you had documents "filed in error" and the script has been modified to select just the top 1 to avoid the failure condition. It now completes on a database that it had previously failed.
-Matt
Posted : June 11, 2014 12:04 am
Matt, we are having the same issue with the inactive problems, and wanted to ask how we get them loaded on the PM side. I assumed they were already there. Thanks in advance!
Posted : June 11, 2014 1:00 am
Topic starter
redde said:
Matt, we are having the same issue with the inactive problems, and wanted to ask how we get them loaded on the PM side. I assumed they were already there. Thanks in advance!
Loading Diagnosis codes into the PM side is a two step process (and it's in addition loading the latest knowledgebases on the chart side) - one is more of a systems administrator (IT) task done in "Server Setup" on the JBoss server and the other part is done in the CPS Application itself.
The IT part involves downloading the latest codes from https://engage.gehealthcare.com/community/en/cps/downloads#codes , extracting that, and then going into Server Setup on the application server and executing the appropriate script to install the latest codes into the database.
The part that we usually leave to our billing lead (and I suspect this part is what you might need to do) is to go into the CPS application and into Administration | Codes | Billing System | Load Diagnosis Codes. Then on the right side, you would search for the missing code (or range of codes), select the code(s) you want to load, check the specialty or specialties that you might be using, and hit Load.
If you want to check if a code is loaded into the PM system, you could go to Administration | Home Tab | Charge Maintenance (along the top ribbon) | Diagnosis and then search for the code that your provider is having difficulty finding.
In our case, we've always only loaded the codes that we actually use into the PM system. Maybe there is an argument to be made for loading them all. perhaps someone else has some advice on that.
-Matt
Posted : June 11, 2014 1:23 am
I applied it to my test server and tested the printer thing (most important to us for now) and it is OK.
Since reading another message in this thread about crashing in a problem search, I figured I may as well test that too. That seems to work OK for us so I guess it is hit/miss.
I also ran into the jboss issue when I applied the SP. It would not let me login at all, even as superuser but after two uninstalls/reinstalls (and even an install on the SQL VM) it finally worked. Really weird as you guys seem to be discussing this as a known issue but I have not run into that in the past. I will say that I was surprised that my jobs.txt, and source folder were not wiped out at first but then after my second reinstall they were gone. So having the previous jobs.txt and source folder contents was probably a bad sign.
Our upgrade is still on for 6/19. I feel a lot better now that this SP is out because I think the printer issue would be a big problem for us.
Mike Zavolas
Tallahassee Neurological Clinic
Posted : June 11, 2014 5:01 am
We installed SP3 and the search function is still bad. When you type in pain you get 11 folders to chose from, then you have to drill down. Let me tell you this make my physicians very happy! An almost direct quote I will leave out the choice words, "if I wanted to be a coder I would not have spend 10 years going to med school." I really hope they keep working on 12 in general, there are a lot of things that seem half done.
Posted : June 11, 2014 6:23 am
Topic starter
What you are getting with 12.0.3.1383 when you type in "pain" is any diagnosis where the description contains the word "pain." This is a huge improvement over what it used to do in 11 and 12.0.0.1329 which is only give you the ones where the description begins with the word "pain" which is pretty much nothing. This is where we actually had to tell providers to use Google or something to look up the code.
If he wants to narrow it down further, he should add words to his search like "pain leg" or "pain arm." There are a LOT of diagnosis that contain the word pain and he is getting a list of all of them that are loaded when he searches active problems and all of them that are not loaded when he searches inactive problems. As he types in more words, it narrows down the list. With ICD1, "pain leg" yields one code, but with ICD10, it yields a whole bunch more so he might need to go "pain right leg" or "right leg pain" which should produce the exact same list.
Now all they need to do is get some synonyms working (like pulmonary=heart for example) and it could really start working nicely.
-Matt
Posted : June 11, 2014 7:13 am
