Stream: implementers
Topic: FHIR Version 3.0.1
Jefferson (Nov 04 2020 at 16:16):
I have my FHIR server setup to use FHIR Version 3.0.1 but I see its now deprecated. Is there any problem with upgrading to Version 3.0.2? And would it be better to go to v4.0.1?
David Pyke (Nov 04 2020 at 16:22):
Moving to 3.0.2 will have minimal impact. Moving to 4.0.1 would be a complete change as there are many large changes between STU3 and R4.
Jefferson (Nov 04 2020 at 16:25):
Thanks why would one need to upgrade to R4?
John Moehrke (Nov 04 2020 at 16:26):
It would be better to move to R4.. yes. R4 has some of the core resources as Normative, meaning they will not be changed in a breaking way anymore.
Jefferson (Nov 04 2020 at 16:29):
what would happen if we never upgrade to R4
David Pyke (Nov 04 2020 at 16:30):
If you are in the US, ONC has mandated R4 for providers, CMS for payers .
David Pyke (Nov 04 2020 at 16:30):
If never updated, all users and designers will slowly lose interoperability
Jefferson (Nov 04 2020 at 16:32):
Thanks for the information.
Jefferson (Nov 04 2020 at 16:39):
Does it make sense to make the interim update to 3.0.2 to avoid using a deprecated version? Or do we hold on that and invest our time to go straight to R4?
David Pyke (Nov 04 2020 at 16:41):
THat would depend heavily on your resources but updating to 3.0.2 is a trivial changeset.
Lloyd McKenzie (Nov 04 2020 at 16:45):
3.0.2 is just some technical corrections to fix some tooling stuff. The spec itself is unchanged. 4.0 makes breaking changes. In most cases, upgrading from 3.0.1 to 3.0.2 is just changing the value in your CapabilityStatement - no other impact. I.e. minutes or hours to go 3.0.1 to 3.0.2 while you're looking at months or more to go from 3.x to 4.x.
Jefferson (Nov 04 2020 at 16:52):
Thanks
Brian Postlethwaite (Nov 04 2020 at 22:35):
Updating to R4 also depends on what resources you're using, you'd have to check the changes in each of the resources that you're working with for the diffs.
Last updated: Apr 12 2022 at 19:14 UTC
