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

Making sense of v19, v20, SP3, SP4, etc.

General Discussion

Last Post by Lee 5 years ago

5 Posts

4 Users

0 Reactions

65 Views

RSS

dignatovski

(@dignatovski)

Posts: 3

Active Member

Topic starter

C'mon Athena, you're killing me here. All of a sudden we have these abrupt changes, re-brandings, upgrades with horrible documentation and my organization is left to not really know what the next steps to take here are.

We are running CPS 12.3.2.116 , I guess "SP2"..

Let's start with the basics, is v19 just another version number for SP4?

What is v19 compared to SP4?

Are there major differences from SP3 to SP4?

From what I read, v20 is only the transition from ESM to cloud RX management right? Or is it an entirely other CPS version?

Obviously, you can see I'm lost here. Thanks.

Posted : March 6, 2020 9:38 am

gibsonmi

(@gibsonmi)

Posts: 827

Prominent Member

The order is SP3 (12.3.3.x), SP4 (12.3.4.x), Then v19 (as in 2019), then v20 (as in 2020). They recently decided to change the versioning to coincide with the year, with the plan of releasing one major version per year. They missed for 2019 by a few months so we will see how long that lasts...

For you SP3 and SP4 are going to be the same thing you already have with some "fixes" depending on your workflows and what features you use, they may or may not be all that helpful to your organization. Both are installed the same as a full version upgrade, if you want to go that route you should do SP4 and forget about SP3.

V19 is a major release, the highlights being primarily AUC (Appropriate use criteria), but it also has the web based basic chart view they call Centricity Now, and some other more subtle "improvements". You will need to have Azure AD setup for v19, if your organization needs AUC you should look at this release, it is now available on the portal.

v20 is the next major release, currently everyone is saying it will be available in June, which usually means October. The highlight of this one is the new medication module. If your organization does any sort of ePrescribing, you are REQUIRED to complete this upgrade by December 1st.

Hopefully that helps.

Posted : March 9, 2020 12:07 am

mjharunk

(@mjharunk)

Posts: 191

Reputable Member

I think the requirement for v20 goes beyond e-prescribing. The way I understand it the ability to manage medication lists goes away without v20 since Dr. First is taking over the entire medication workflow. I don't think MEDISPAN updates will be included in the KB moving forward.

Posted : March 9, 2020 2:42 am

dignatovski

(@dignatovski)

Posts: 3

Active Member

Topic starter

Thank you for the very helpful answer gibsonmi. Finally some clarification.

Posted : March 9, 2020 3:13 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

Agree with the above. To add clarity:

Radiology orders for higher end exams (CatScan/MRI/etc.) will require an AUC code to accompany the order. There are other methods one could use to obtain these codes, but they are not 'free' to use and require external workflows (not ideal). Your radiology department may already have a process in place to 'translate and obtain' the code, so you might opt to check with them first since they cannot be paid for services unless they have one. This requirement should be the primary decision point for upgrading to v19.

A secondary decision point would be the desire to 'ramp up' on boarding with Azure AD. You could use this version to iron out the kinks so that the v20 install goes a bit smoother (one less moving part).

If you do not need AUC or are not interested in enabling Azure AD early, then you should be able wait for v20 without much impact on your day to day (note this is a general statement - your needs may actually vary - recommend checking with support if you are unsure). However, as mentioned, if you prescribe, not just e-prescribe, v20 is mandatory for all sites due to major changes in the medication functionality of the EMR. Without v20, there will be no Medispan updates and reference lists will quickly become outdated/obsolete.

An interesting question will be the impact on medication identifiers. I've not yet seen an answer to what the primary driver will be in the system. Currently, the DDID is the primary and most commonly used number, however that ID system is proprietary to MediSpan. I am uncertain if the new system will translate for legacy or if all custom code in clinical content will need to be updated. Having a heads up to this answer is a bit critical, I would think. If anyone already knows or learns about it, it would be helpful to inform the user base here. 🙂

Posted : March 9, 2020 7:42 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 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