FHIR Chat · Inline References · shorthand

Stream: shorthand

Topic: Inline References


view this post on Zulip Nick Freiter (Jul 09 2020 at 11:42):

Etienne Cantineau said:

Hello, i have problems with the inline reference correction. if I use Reference(OrganizationEx01), instead of having Organization/OrganizationEx01, now i get #OrganizationEx01 which is not resolvable by the publisher

Hey @Etienne Cantineau , I'm moving this over to a new thread so this conversation isn't mixed up with the one happening where this was originally posted. Is OrganizationEx01 declared with Usage: #inline in SUSHI? That is the only situation in which the # should be used, and if the OrganizationEx01 example is actually #inline, then SUSHI will not generate an independent JSON file for that resource, so that resource can only exist in the context of another resource, and it isn't proper to reference it as Organization/OrganizationEx01, since that resource does not exist independently.

view this post on Zulip Etienne Cantineau (Jul 09 2020 at 11:52):

@Nick Freiter Yes my examples are bundles with each entries as inline resources. I had no error in QA with sushi 0.13.2 and gets now 332 with 0.14.0 saying REF-1 error and unable to resolve resource for each of my references to inline resources

view this post on Zulip Nick Freiter (Jul 09 2020 at 12:18):

We were under the impression from this thread that resources which don't have an independent existence should be referenced using #id. But it looks like that does not account for Bundles, so we've created a new bug that will need to be fixed, sorry if this is holding you up.

view this post on Zulip Chris Moesel (Jul 09 2020 at 12:43):

I think the rule is (probably) that if the referenced resource is in contains, you should use #id -- otherwise use a normal reference.

view this post on Zulip Etienne Cantineau (Jul 09 2020 at 12:51):

No problem, thank you for quick answers!


Last updated: Apr 12 2022 at 19:14 UTC