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

eSM 3.3.2

General Discussion

Last Post by Anonymous 12 years ago

11 Posts

5 Users

0 Reactions

75 Views

RSS

srock

(@srock)

Posts: 81

Estimable Member

Topic starter

Has anyone installed eSM console version 3.3.2? Were there any pitfalls that we should be aware of prior to this upgrade?

Posted : November 19, 2012 5:43 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

make sure you upgrade to 3.3.2.6168.

Posted : November 19, 2012 6:02 am

srock

(@srock)

Posts: 81

Estimable Member

Topic starter

I'm a nurse.....would you explain a bit more?

Our IT department will actually perform the installation and I'm sure they will ask me why 3.3.2.6168?

Our IT department is outsourced and they often do not value the information we provide.

Thanks so much for your help!

Posted : November 19, 2012 6:08 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

6168 is the build number for the upgrade. upgrades with prior build numbers fixed some issues, but introduced new issues. 6168 is the latest version.

Posted : November 19, 2012 6:24 am

srock

(@srock)

Posts: 81

Estimable Member

Topic starter

Super! Thank you so much for your help.....just 1 more quick question. Did you notice an "new issues" with 6168 that I should be on the lookout for?

Posted : November 19, 2012 6:34 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

not yet...crossed fingers...

Posted : November 19, 2012 6:36 am

srock

(@srock)

Posts: 81

Estimable Member

Topic starter

And when did you do the upgrade to 6168?

Posted : November 19, 2012 6:49 am

jjordet

(@jjordet)

Posts: 545

Honorable Member

10/9/12

Posted : November 19, 2012 6:50 am

Sam

(@sam)

Posts: 371

Honorable Member

Ditto on all that jjordet said. We upgraded as soon as it was available and have not had any issues since the 6168 release.

Posted : November 19, 2012 8:40 pm

jamesedward

(@jamesedward)

Posts: 257

Reputable Member

We upgraded to 6168 on 10/19. It has been a solid release.

Posted : November 20, 2012 6:08 am

Anonymous

(@Anonymous)

Posts: 0

New Member Guest

We upgraded to 6168 on 10/19. It has been a solid release.

EXCEPT that when you "test all" features from the ESM console, it'll say that RXHub doesn't work. This is a confirmed bug, and they "think" it'll get fixed in the next release.

Posted : November 21, 2012 12:20 am

Share:

24 Forums
9,942 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