Stream: implementers
Topic: extending extensions
René Spronk (May 04 2020 at 09:32):
Does anyone have a good (i.e. real life) example of the use of extensions within an extension ?
Neeraj Ojha (May 04 2020 at 10:28):
Yup, we would like to see that too? Real life example of nested extensions
Michele Mottini (May 04 2020 at 12:54):
Something like http://www.hl7.org/fhir/smart-app-launch/StructureDefinition-oauth-uris.html ?
James Agnew (May 04 2020 at 14:41):
The US Core race and ethnicity extensions are the example I always use: http://hl7.org/fhir/us/core/stu1/StructureDefinition-us-core-race.html
René Spronk (May 04 2020 at 15:02):
us-core-race is OK as an example, but may not go down too well in some settings because of the subject area. oauth-uris is also OK, but the subject area is 'too exotic' to use in a presentation. I can make something up, if we have a widely used standard extension (some xx-core extension, or std-hl7 extension) that has a particular [strong] valueSet binding, and one needs codes from some other valueSet, then that's a prime example of having to extend an extension.
Lloyd McKenzie (May 04 2020 at 15:26):
Simplest is to throw a "data absent reason" in the middle of something else
Jay Lyle (Jun 08 2020 at 14:30):
We have an information collection method, which is used for race and ethnicity (Observer, Proxy, Self-Identification, Unknown). I'm looking at creating an extension http://va.gov/fhir/StructureDefinition/raceEthnicityCollectionMethod. Our naming convention would normally prepend the resource context, but the context is not one but two extensions, so we will leave it un-prepended. If we were to find other contexts we would generalize the name.
Would that look like this?
context type = extension
context expression = http://hl7.org/fhir/us/core/StructureDefinition/us-core-race
Lloyd McKenzie (Jun 08 2020 at 14:36):
That looks right to me
Last updated: Apr 12 2022 at 19:14 UTC
