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

Method to block plugin updates?

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

8 Posts

3 Users

0 Reactions

59 Views

RSS

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Topic starter

We just encountered an issue where an Availity plugin was updated and prevented users from logging into CPS until their client had got the update. The database that is altered when the upgrade is run doesn't log the user that ran the update, so we have no way of knowing who did it.

In reviewing the incident, we realized that any user has access to the upgrade page, and while not everyone has permission to run the upgrade, we're not sure what point the database change is made that triggers the system wide upgrade requirement.

We are wondering if anyone else out there has locked down their upgrade pages and if so, how. We have some thoughts, like blocking the actual URL from user computers, but we're not sure how that will affect the actual system.

Any insight would be great. I'll be sure to update this thread with our decision in case anyone else has encountered this.

Posted : June 1, 2018 7:38 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

is not on the database, is on the Jboss.

A simple XML file that you can manually edit to match the previous version of the plug in and the installation page will not pop up.

Posted : June 1, 2018 7:58 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Topic starter

What is the name of the XML file? The support at our vendor said it was a database update, so I didn't even think to look in the JBOSS folder...

Posted : June 1, 2018 10:34 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

on the jboss server 12.3

\Program Files\Centricity Practice Solution\jboss\standalone\deployments\cps.client.war\install\optional

you will see a folder for every plugin you have.

inside the folder the xml fire will be with the latest installed version.

just revert the version to the version most of the computer in your network have and should do the work.

don't remember if you need to restart jboss services.

Posted : June 1, 2018 10:38 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

Hope that solve your issue.

Posted : June 1, 2018 10:55 am

clafty

(@clafty)

Posts: 37

Trusted Member

the same thing happened to me over the weekend! I can't find out who, if anyone updated 3 plugins. I spend almost 4 hours on Father's day updating all the clients throughout our system. I am trying to find out who updated them. I've never seen this happen on its own.

Posted : June 18, 2018 1:47 am

clafty

(@clafty)

Posts: 37

Trusted Member

Can you elaborate on the database update? The more I look into this, the more I'm convinced that no person updated the plugins. No one appeared to be in our system when these updates happened.

Posted : June 18, 2018 2:05 am

vrdlc

(@vrdlc)

Posts: 135

Estimable Member

Topic starter

I don't think any data is stored anywhere about who made any changes, which is stupid. I also think our vendor was mistaken, and no actual database information is changed. All that changes is the contents of the text file on your JBOSS folder that was listed above. We've tested it and changing the number in that text file to match the old version works!

Posted : June 19, 2018 5:09 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