Stream: shorthand
Topic: extension names
David Hay (Feb 22 2020 at 18:37):
Still having issues with extension 'name clashes'. In the following definition I'd really like to use 'country' as a 'child' extension, but there is already an extension defined using that name, so sushi tries to use that one...
...
* extension contains
countryXXX 0..1 and
placeOfBirth 0..1 and
source 0..1
// definitions of sub-extensions
* extension[countryXXX].url = "countryXXX"
* extension[countryXXX] ^definition = "The birth country."
* extension[countryXXX].value[x] only CodeableConcept
* extension[countryXXX].valueCodeableConcept from http://hl7.org/fhir/ValueSet/iso3166-1-2 (preferred)
Chris Moesel (Feb 24 2020 at 13:44):
Thanks for the reminder, @David Hay. We're still trying to determine how best to handle this -- and whether it should address this exact situation or be more general. One thing we're considering is making it so that you have to use a URL (or an alias to a URL) to refer to any external entity. If we go with that, we need to determine how best to combine that w/ allowing the user to specify their own slicename (when referencing an external extension). We also need to figure out what to do w/ base FHIR resources, because I doubt people want to reference Observation as http://hl7.org/fhir/StructureDefinition/Observation -- but we also know there are people who want to name their profiles the same as the resource they profile (e.g., a Patient profile named Patient), so we need to support that too.
Chris Moesel (Feb 24 2020 at 13:45):
We have a few ideas kicking around. Will try to propose something this week.
David Hay (Feb 24 2020 at 17:15):
thanks chris... (though naming a profile the same as the resource type does seem a bit confusing to me :) )
Last updated: Apr 12 2022 at 19:14 UTC
