I am trying to find the FHIR 5.0 specifications and saw that some people seem to be using the FHIR v5.0 server already. According to the official FHIR blog, the specification was supposed to be released in the 3rd quarter of this year (of course COVID could have slowed this down). Could someone point me in the right direction please?
5.0 is in development and is scheduled to start balloting in May 2021. It's not likely to publish as a final 'official' release until Q2 2022. However, there's a "continuous integration build" that shows what the current proposed content for R5 is hosted here: http://build.fhir.org. As well, we produce snapshots of the draft R5 release for connectathons and other purposes so that there's a semi-stable release people can write code against when testing for connectathon.
The current timeline has indeed been impacted by COVID, but it's also been impacted by the appetite of the community for a new release and the ever increasing amount of work involved in producing a new release.
Related
I am currently working on USD 1.0 which is of-course a very old version of USD.
We are trying to move to the newest version of USD in my organization, which i believe is USD 4.0
I have tried searching the web but other than the MSDN article i have been able to gather much detail on this version.
I am trying to figure out my possibilities in trying to adapt to this newer version. In light of it, i have a few questions listed below,
Has Microsoft released only the preview/trial version of USD 4.0 yet? Or is it made available for general public which means we can access and start developing in our production environment?
Is the new version of USD, a web based version? I have heard that
this version is not the desktop application like it was before.
Will it be safe to migrate from USD 1.0 to USD 4.0?
Microsoft has also introduced Unified Client Interface, what is it?
Is it available only with USD 4.0?
Features comparison with USD 1.0?
If Microsoft have released the preview version only, then when will
they release the stable version? (any tentative date)?
Also, if they have released the preview version just then obviously they might change it in future. Therefore, it will not be wise enough to migrate to it if it is just a preview version.
Looking forward to your answers. Any sort of videos, articles, documentations, press releases, your personal opinions are welcome.
Thanks
Most 'manual' based MSDN information has been moved to Microsoft Docs: https://learn.microsoft.com
USD 4.x is still a desktop application that loads MSD components. You can upgrade to a more recent version 3.2 quite easily:
You can upgrade a Unified Service Desk 1.x or Unified Service Desk 2.0 sample application package to Unified Service Desk 3.2 by importing the Upgrade sample application package. The upgrade will not affect the configuration data associated with the existing solution.
Follow the steps here:
https://learn.microsoft.com/en-us/dynamics365/customer-engagement/unified-service-desk/admin/upgrade-unified-service-desk-solution?view=dynamics-usd-3
From there on forward it is much more easy to compare 3.x with 4.x and answer all your remaining questions.
Neil Parkhurst also has a ton of information.
https://neilparkhurst.com/2016/06/20/usd-the-book/
We are going to run Cobalt on our device, and consider to the stability for partners' development.
We'd like to know...
The official version that Cobalt recommends.
Would Cobalt have a regular official version released? If the answer is yes, may I know the period of the release?
It would be great to know this information for partners preparing the environment for the future development.
Thank you.
The master branch at https://cobalt.googlesource.com/cobalt/+/master/ will always stay close to the internal development trunk. It will be a moving target in terms of stability, but will also see features first.
Release branches are sequentially named, COBALT_2, COBALT_3, and so on. They are named on when they branch, not when they stabilize, but in general it will be safest to port and release off of the latest stable release branch. These branches have gone through testing and released on one or more real production platforms.
Since this is still early days, there isn't a regular release schedule yet, but it is being worked towards. There will be more details on that when plans are finalized.
I have seen that yesterday Web API RTM has been released by Microsoft.
However I can't seem to find any log about what has changed from RC to RTM and any tips on what has changed.
We have a service that's ready for production next week, and I am not sure whether to roll with RC or upgrade to RTM this late in the project. What value does it add?
Thanks
Ubal
The official release notes can be found here at www.asp.net.
As #Aliostad kindly mentioned, I wrote an overview post highlighting what's changing and including some code samples and other references.
Henrik also wrote a nice overview post - and that one's also focused on the preview for the out-of-band functionalities available as NuGet packages (OData, tracing, Help page, and a formatting library for Win8).
If you ask whether you should upgrade - obviously yes. There aren't many breaking changes so it should be rather painless, and you get a mature, production-deployable product. It's well worth it imho.
I was wondering, how often does DHTMLX offer a new version and how hard do you find it to upgrade your applications to the new version. This is namely a critical part in my research, but I cant seem to find any problems with updates. This question is just to make sure that my findings are correct.
Please suffice with: version number, DHTMLX component.
I work for DHTMLX. During the past 3 years we released one major update per year. Currently we're preparing the next version which we hope will be available in beta till the end of April 2012. We try to make the new releases backwards compatible and provide the upgrade path to the latest release (like here).
I've used many controls from the dhtmlxsuite in our app for the past 5 yrs. They are pretty good at making things backwards compatible, but not always. When going from v3 to v4 just a few months ago, there was quite a lot I had to do get my code back up and running. Also there dropped a few features that were supported in v3, this is not so good in my opinion. But overall, I really like the dhtmlx controls, they are an integral part of our product which now is used all over the world by thousands of users (http://www.ecosys.net/ecosys-epc/).
It is quite intuitive that at least Gamma comes after Beta and Alpha.
But how about CTP, RTM and Preview releases? Which one comes first and last?
MEF (Managed Extensibility Framework) is currently on Preview 5 release, but I am not sure if it is a release before Alpha or after Beta, CTP or RTM. Is it OK to use preview releases in production code?
What are the differences between those releases?
I am particularly interested in knowing differences between
RTM
CTP
Beta
RC
Preview
releases.
It seems like everywhere each releases mean different things.
I've most commonly seen those terms used in the following ways
CTP (Community Technology Preview): Very much like "Show and Tell". Features are present to varying degrees and customer can get an idea of where the release is going
Beta: Features are mostly implemented but still have rough edges. Quality is fair at this point. The higher number beta, the higher the quality
RC (Release Candidate): Product believes it's ready to ship. One last chance for customers to provide feedback and find major blocking issues
RTM (Release to Manufacturing): Product is complete and ready to be shipped to customers
The stages are typically Alpha, Beta (can be broken into Internal vs. External), Release Candidate (RC), Release to Manufacturing (RTM). "Community Technology Preview" (CTP) or just plain "Preview" are, in my opinion, merely euphemisms for Beta (which implies "contains plenty of bugs").
It can vary from company to company. They are usually defined like this:
CTP - Community Technology Preview - Not beta quality, not as wide-spread. Not necessarily feature-complete. Usually intended for partners who will build on top of the product.
Preview - Usually like a CTP.
Beta - Widespread release. Expected to be mostly stable, feature complete.
RTM - Release to manufacturing. Final release of the product, the "Gold" release.
As for using previews in production code, it depends again, but is usually a bad idea. They are usually not that well supported.
The answer is "It depends".
All of these badges mean different things for different people, and things like "CTP" and "Preview" even more so.
Where relevant (e.g. frameworks) most preview/beta/ctp releases will come with information about whether they should be used in shipping code or not. Generally if they require an end-used redistributable the answer is no.