Why Mississippi Baptist a Version 13 Pilot did not go live

[Steve Stanic]

All,

As one of the larger if not largest Paragon installs many of you have reached out and e-mailed me as to why we as a version 13 pilot did not go live let's just say we tried.  We tested version 13 through 15 kits and over 4300 hours of test time. So in response to the question from today's inpatient  focus call answered by Jay D'lugin we did not test just a few things we went through at least 5 integrated full suite tests of the WHOLE product.  And for us it came down to basic functionality.  We lived in the Horizon world where things like flow sheets and MARS where available so we can care for the sickest of sick patients.   

McKesson tried to deliver some of these things in 13, but missed the mark functionality wise.  Many of you asked me why Holzer another pilot is happy and went live and we didn't.  The answer in my mind...but please ask Holzer is quite simple.  We are on version 12.1.1 and had medication reconciliation in place already. Holzer went from 12.0 right to 13, that one improvement would be significant. 

At this time McKesson is committed to address the issues we have...in 9 months.   For smaller 250 or less bed systems Paragon version 13 probably is a good fit, I'm not saying we are the biggest or best but with a large Dialysis unit and two  large ICU's we care for really sick patients.  And we need a lot of patient data presented in a useful format.  Once Paragon gets there we will upgrade.We remain committed to Paragon at this time. But in the end our Physician Advisory group felt that version 13 need some significant improvement.

[Greg Slattery, CIO CHWC]

Steve,

Thank you for the post.   I am curious about the comment about being on V12.1.1 and 'having med recon in place already'?  We too are on V12.1.1 and it sounds like we lose something in that area when going to V13.   I give you and Baptist credit for sticking to your guns and not moving forward until McKesson provides the needed fixes and functionality.  That will help all Paragon installs.   Can you comment on the quality of V13 as far as new code working and NOT breaking things that worked before?  Regression testing has always been a big problem IMHO for Paragon.

Thank you,

Greg

[Steve Stanic]

Greg,

When we went through the pilot process each kit would break something in the kit before it.  When we got to kit 13 and 14 it did become better.  We will test the go live kit next week and I'll keep you in the loop.  As for the issues we found with regards to lack of functionality we probably will not go live on 13 until version 13.0.2 which is slated for September time frame.

Stev

[David Witton]

Steve

Thanks for the explanation - I'm from a 50 bed hospital, it helps to hear how the big guys think. Perhaps you could do an Insight session on "What Paragon Clinicals still lack"

--
You received this message because you are subscribed to the Google Groups "Paragon CIO" group.
To unsubscribe from this group and stop receiving emails from it, send an email to paragon-cio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

David Witton

[SSt...@mbhs.org]

I'm not sure McKesson would appreciate that 😀

Sent from my iPhone

You received this message because you are subscribed to a topic in the Google Groups "Paragon CIO" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/paragon-cio/zuPJyorSCug/unsubscribe.
To unsubscribe from this group and all its topics, send an email to paragon-cio...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Click here to report this email as spam.