HealthShare Foundation is changing its name (slightly)

[David Loveluck]

As many people will already know, from 2013.1, HealthShare Foundation is changing its name.

 

It is now a component of HealthShare and not a separate product. This will make very little difference for existing HealthShare Foundation customers. There are no license implications or functional implications or platform implications. It is like any other version upgrade. You just use  a HealthShare kit instead of a HealthShare Foundation kit.

 

This change will make it much easier for end user customers who start with the foundation and then want to use  more HealthShare components and is part of a process to get HealthShare components to customers more quickly.

 

So if you are a HealthShare Foundation user, when you see an announcement that HealthShare 2013.1 is available (hopefully very soon) it applies to you.

 

For more information see the HealthShare 2013.1 release notes or the compatibility blog (http://blog.intersystems.com/compatibility/)

 

Dave

 

 

[Andrew Makinson]

David we are on the verge of a fresh major install of 2012.2 on around 9 production nodes.

Any indication of when 2013.1 is definitely available?

What known impacts/issues are there moving from 2012.2 to 2013.1? 

Thanks

Dom

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.