Notifications
Clear all
Topic starter
A few times a year, totally separate from our KB updates, our Medispan date in the "About Centricity" window turns into "Unknown or Invalid". This breaks the Medication Interactions, which is a HUGE patient safety issue. Our only known solution is to restart the JBOSS service (not server), which takes down our system for 2-5 minutes. We have about 300 users on at any given time, so coordinating these restarts is not easy. The last time this happened, last week, it happened twice in one day.
We reached out to our vendor to ask them to communicate this issue to Virience, and while we don't expect to hear back, we at least wanted them to know it's a thing that happens.
Has anyone else experienced this?
We have a lead, but unfortunately we won't be able to confirm anything until this happens again, which could never even happen again. When we reviewed the logs from the last event, we noticed that each time one of our servers restarted. Once it was our JBOSS server, the other time it was our DATA server.
Our theory is that these sudden restarts has caused drift between some internal CPS date and the actual date in the database. We don't know where the database field actually is, so we can't validate how precise it is (is it day, hour, minute, second, millisecond, time since 1970?).
Our inability to find this has also prevented us from manually forcing a solution. We did find the date in the SYMBOLS table, but changes to that field aren't reflected in the About window.
Anything anyone may know/think/believe would be really helpful. Or, at least, it wouldn't hurt!
Posted : April 19, 2019 5:14 am
Hello,
We just encountered the same thing twice in the last month. It hadn't happened for over a year, and then suddenly, we had no Medispan date.
It has not affected us too often, but when it does, it is a huge headache. I am sorry we don't have any leads for you, but it is certainly a known 12.2.2 issue.
Posted : April 22, 2019 3:56 am
It happened to us right after a KB update and we weren't able to fix it so we called support. GE/Virence made some changes to our jboss setting and since we were good.
Posted : April 22, 2019 6:15 am
Topic starter
Don't take this the wrong way, but I'm THRILLED this has happened to someone else!
Are you able to look at your server logs for those days your Meidspan date disappeared? If so, can you check to see if there was a server crash at/around that time? We had this happen after a JBOSS crash/reboot and after a DATA crash/reboot.
Posted : April 22, 2019 6:23 am
Topic starter
Any idea what they did?
Posted : April 22, 2019 6:25 am
They made some changes to the standalone.xml file under jboss\standalone\configuration folder.
Posted : April 22, 2019 6:42 am
I will see if our Database Admin can check the logs for the day's it happened. I would be interested if we find out what lic08 had done as well if they have a fix. 🙂
And don't worry, I will not take that the wrong way. It's good to find that your're not alone in suffering right? 😉
Posted : April 22, 2019 6:56 am
