Stream: implementers
Topic: support for multiple implementation guide versions
Siarhei Bartoshyk (Sep 23 2020 at 03:58):
Hi there,
I have a question about IGs(Implementation guide) and versioning for it.
Our company wants to implement a server for US Core IG and rely on a particular version of IG. But it is essential that time to time a new version can be published.
Let's assume that changes in IG are breaking and we don't want to force external 3-rd party applications to migrate on the newest version.
So the question - how can we introduce supporting of two versions for IGs? What is the best practice over the industry?
Grahame Grieve (Sep 23 2020 at 06:53):
that depends. If that changes are consistent, you should be able to support multiple versions at once. But that will depend on the details of the changes. But I think that's the intent with US Core
Siarhei Bartoshyk (Sep 25 2020 at 05:33):
yep, I agree it the changes are not breaking and the backward compatible you are right. But what should I do if we have our own IG and it has breaking changes for any reason? In this case, I have to differentiate what exactly I'm calling IG v1 or IG v2. There are multiple options in FHIR protocol, for instance, we can specify a profile name for each version of IG. But it is very strange.
Last updated: Apr 12 2022 at 19:14 UTC
