Stream: implementers
Topic: dstu
Sanu Singh (Aug 26 2016 at 17:50):
Hi, We are implementing FHIR in our development and planning to deploy in production dec-2016 .my question is which version of FHIR should we use DSTU2 or STU3 version
Andy Stechishin (Aug 26 2016 at 18:12):
@Sanu Singh if you have no code and no external dependencies and don't mind minor changes the answer is simple: STU3, if you want the version that will look more like the normative standard (when it gets there), STU3
Having said that, you need to realize that STU3 is in ballot at this moment, there will be a LARGE number of changes to STU3 between now and the end of October (possibly sooner depending on the number of ballot comments and whether Grahame will accept an IV that supplies caffiene to keep him awake 24h/day and prevents him from leaving his desk for distractions like eating). If you are comfortable with the standard changing while you use that is the decision you must make.
On the other hand DSTU2 will not change because the changes needed are what went into making STU3. Fewer and fewer people will support DSTU2 or wish to support DSTU2 going forward. You will be implementing against something that is effectively replaced. If you are only using it internally and DSTU2 supports everything that you need and stability is your most important consideration then DSTU2 might be a better choice
Sanu Singh (Aug 26 2016 at 18:46):
Thank you Andy for quick response.
Grahame Grieve (Aug 26 2016 at 20:22):
@Andy Stechishin we need to find a way to feed... coffee... to all the committees.. Though you might argue that there would be a more appropriate drug to give committees to improve the rate at which the come to agreement, not just the number of hours that they have to try
Josh Mandel (Aug 29 2016 at 15:29):
@Sanu Singh Andy's analysis is correct, of course. Though on this same analysis, I reach a different conclusion.
If you want to publish something in December 2016, I think you want to target DSTU2, because (to my mind!) it exists as an official draft. If you target STU3 right now, you'll have a moving target. In the Argonaut Implementation Program, for example, our decision has been to target "the current release of FHIR", which means DSTU2 until STU3 comes out.
Josh Mandel (Aug 29 2016 at 15:30):
My bottom line: if you want to publish services that you plan to support for 12+ months, it makes sense to stick to official published FHIR releases.
Last updated: Apr 12 2022 at 19:14 UTC
