Stream: conformance
Topic: profiling extensions
Chris Grenz (Jun 03 2016 at 20:14):
Suppose I define an extension http://example.com/fhir/my-base-extension In here I use fixedUri to fix the url element.
Then I profile that extension in SD http://example.com/fhir/my-extension-profile to make some things mandatory and define another sub-extension (with a relative URL, say <fixedUri value="mode"/>).
2 questions:
- In the resource instance when I use the extension, how do I indicate that I'm using
.../my-extension-profilerather than.../my-base-extension? I don't think I can... - In the instance, if I add the "mode" extension as a sub-extension to
.../my-base-extension, the server won't know anything about it since it doesn't know anything about.../my-extension-profile.
David Hay (Jun 04 2016 at 17:39):
I may be missing something, but why can't your instance refer to my-extension-profile in the extension url?
Grahame Grieve (Jun 05 2016 at 11:17):
well, Chris, you refernce my-base-extension for meaing. For conformance rules, your profile that invokes the extension can refer to the profile of it (eg. my-extension-profile), and so you know whether to expect the mode. But since mode is not defined in the base extension, it must be a full uri to an extension definition of it 's own
Chris Grenz (Jun 06 2016 at 14:32):
So we should have a constraint on SD that extension profiles can't add extension slices, yes?
Chris Grenz (Jun 06 2016 at 14:32):
e.g. you can't add another extension in a profile of an extension.
Grahame Grieve (Jun 06 2016 at 18:09):
well, you can, yes, but it must be a reference to a different extension
Chris Grenz (Jun 06 2016 at 18:25):
So...with an absolute fixed URL rather than a relative one.
Grahame Grieve (Jun 07 2016 at 00:39):
yes
Last updated: Apr 12 2022 at 19:14 UTC
