Stream: implementers
Topic: Upgrading between FHIR versions
David Hay (May 26 2016 at 21:04):
Interesting question from a colleague. If a messaging endpoint receives a fhir message, how does it know what FHIR version it conforms to?
Jason Walonoski (May 26 2016 at 21:15):
I would guess that you'd have version specific endpoints, and integrating partners would negotiate which endpoints to use out of band.
David Hay (May 26 2016 at 21:47):
yeah - but it doesn't feel the 'tidiest' of solutions though - and not that robust...
Grahame Grieve (May 26 2016 at 22:28):
it's a very natural solution for rest, but probably not so natural for messaging
Grahame Grieve (May 26 2016 at 22:28):
but it's the easiest for now.
Jason Walonoski (May 27 2016 at 11:43):
Well, the provider could have multiple conformance statements which have fhirVersion info, so the different messaging endpoints could be discoverable. I've never heard of a single messaging endpoint that handles breaking version changes in a robust way.
Grahame Grieve (May 27 2016 at 21:31):
common in the v2 world. In fact, I had one interface which seemed to send a random version - I could never figure out the pattern anyway. But as far as I know, this is a v2 pecularity
Jens Villadsen (May 27 2016 at 21:32):
+1
Last updated: Apr 12 2022 at 19:14 UTC
