FHIR Chat · Data Consistency · versioned API

Stream: versioned API

Topic: Data Consistency


view this post on Zulip Kevin Olbrich (May 12 2018 at 13:25):

If a server supports more than one version of FHIR I think the expectation is that a resource should be representable in any supported version so long as that resource type existed in the requested version.

view this post on Zulip Kevin Olbrich (May 12 2018 at 13:27):

If a server stores data in a FHIR agnostic format and always converts to the requested format, then this is simple to achieve, but it may be difficult if the server stores data in a FHIR-specific format (this would require conversion from one version to another), perhaps using FML.

view this post on Zulip Kevin Olbrich (May 12 2018 at 13:29):

If a server cannot represent a resource in a particular version, perhaps the server should return an operation outcome with an error message that indicates this.

view this post on Zulip Lloyd McKenzie (May 12 2018 at 14:07):

That expectation can only hold if the resource is convertable between versions - which is usually the case, but not always for STU resources

view this post on Zulip Kevin Olbrich (May 12 2018 at 14:08):

Do you have any examples of cases where the resource exists in two versions but can't reasonably be converted between them?

view this post on Zulip Lloyd McKenzie (May 12 2018 at 14:17):

@Grahame Grieve can speak to that better than I as he's had to worry about transforms. I know there were some cases with R2->R3.

view this post on Zulip Grahame Grieve (May 12 2018 at 14:24):

lots of cases. elements that the committee's ideas just changed, and I couldn't think that there was any way to transform between them

view this post on Zulip Kevin Olbrich (May 12 2018 at 21:34):

Perhaps we can tag resources where the representation is suspect with 'SUBSETTED', but rules around when to apply that aren't immediately obvious to me.

view this post on Zulip Grahame Grieve (May 13 2018 at 06:27):

no agree

view this post on Zulip Brian Postlethwaite (May 13 2018 at 09:54):

From 2=>3 Practitioner resource was split into Practitioner and PractitionerRole resources, but the data is able to be converted bi-directionally ok, however they look different. So don't think Subsetted would apply here.

view this post on Zulip Brian Postlethwaite (May 13 2018 at 09:54):

Valueset had CodeSystem split out in a similar way too.


Last updated: Apr 12 2022 at 19:14 UTC