Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

KB Update not Incrementing the Medispan Expiration or Version

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

8 Posts

5 Users

0 Reactions

57 Views

RSS

mjharunk

(@mjharunk)

Posts: 191

Reputable Member

Topic starter

Back in June we ran into an issue where the previous month's Medispan version did not get updated even though the expiration date did. We didn't notice it until we went to load the June KB and failed on version check. We were able to manually reset the version number and reload the KB and it resolved the issue.

This month's KB updated the Medispan version number, but not the expiration date. We couldn't re-load the KB because the version was incremented and it failed. I again manually reset the version number and reloaded the KB. The Medispan expiration date updated the second time around.

I'm wondering if any other sites have experienced similar issues with the KB's lately. I have a workaround, but would like to know if my environment is causing this or if it's an issue with KB package from GE. Feedback welcome.

Posted : November 13, 2017 3:40 am

petemarkey

(@petemarkey)

Posts: 373

Honorable Member

might be related, from the KB release notes.

Known issues
The following are known issues and we are working to fix them as quickly as possible.
Address issues where a JBoss restart is required
SPR70364
Issue:
After installing the Knowledgebase, JBoss Windows services may need to be restarted
in order to properly reload reference data. Specific data that needs reload includes the
Medispan data used for interaction checking and Immunization custom list editing as well
as diagnosis codes used in problem search. In all cases, restart DTS after the JBoss
servers have been restarted.
Workaround:
EMR
l Single Server 9.8.x, 9.10.1 – no restart required
l Single Server 9.10.2, 9.12 – restart JBoss windows service
l Multiple JBoss servers - restart all JBoss windows services.

Posted : November 13, 2017 4:44 am

mjharunk

(@mjharunk)

Posts: 191

Reputable Member

Topic starter

Pete,

We saw that in the release notes this time and restarted the Jboss services and DTS. That suggested fix didn't work in our case.

Posted : November 13, 2017 4:53 am

petemarkey

(@petemarkey)

Posts: 373

Honorable Member

ok, to answer your question i have not had the problem your described. maybe not all workstations are logged out? I always make sure of that.

Posted : November 13, 2017 5:39 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

We are experiencing something similar right now as well. Our version incremented, but the date now reads: Medispan Expiration Date: Unknown or invalid

What is especially bizarre about this is we didn't see this in any of our three test environments. Maybe there was a hiccup in the install in production. Do you know where to locate this information in the database?

EDIT: I also wanted to add that this is breaking our ability to use the medication interactions, which is kind of a big deal. If we can just update the expiration date somewhere, that should fix this.

Posted : November 21, 2017 4:28 am

gpincomb

(@gpincomb)

Posts: 278

Reputable Member

I have experienced something similar with our Test Environment, our KB Version number does not advance during the installation process. It has been this way for at least 6 months now and it only affects the Incremental KB Updates, as the Full Updates apparently do not check the previous version.

For CPS, the SQL query to see the KB version is:

select*

from SYMBOL s

where s.OBJECT='_MS_V01'

and s.NAME ='Version'

Posted : November 21, 2017 4:57 am

DavidShower

(@davidshower)

Posts: 1255

Noble Member

This will get you the MediSpan expiration date:

select * from ml.symbol where name like 'Exp%' and object = 'MSDI'

Posted : December 29, 2017 3:29 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Has anyone found a fix for this besides restarting JBOSS? A few times a year now, our Medispan expiration date turns into "Unknown or invalid" and we have to coordinate with all of our users so they know to expect five minutes of system downtime. This, obviously, sucks, and we want a better way to fix this, or to know why this happens.

Posted : April 11, 2019 9:40 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0