FHIR Chat · Handling canonical references in STU3 · implementers

Stream: implementers

Topic: Handling canonical references in STU3


view this post on Zulip Richard Kavanagh (Oct 06 2021 at 13:46):

I appreciate canonical referenced did not appear until FHIR R4 but from a backwards-compatibility perspective, I'm trying to work out what the expected behaviour would be from an STU3 FHIR server when it encounters one.

Currently on the Firely Vonk server if you post an STU3 reference with a canonical URL construct the response does not look correct to me.

So for example posting the following

image.png

Yields the following

image.png

The canonical references have been interpreted as relative URLs rather than absolute URLs- is that the correct behaviour?

view this post on Zulip Matthijs van der Wielen (Oct 08 2021 at 13:36):

When looking in to this it seems to be caused by the use of pipe versioning in the reference. When you remove the |33 the reference is stored correctly. I am not sure why the pipe versioning is include in the reference, but Firely Server does seem to handle this incorrectly. The pipe version should not influence the behavior and should be ignored.

view this post on Zulip Lloyd McKenzie (Oct 08 2021 at 16:24):

I don't think you can use the piping mechanism with a contained reference. A contained reference is absolute and can't be further qualified.


Last updated: Apr 12 2022 at 19:14 UTC