Stream: conformance
Topic: Binding a VS to an Extension
Chris Moesel (Oct 14 2020 at 17:14):
We're working on GoFSH, a tool to convert SDs to FHIR Shorthand. We often use US Core as a use case. In our testing we discovered that US Core patient has this in the differential:
{
"id" : "Patient.extension:birthsex",
"path" : "Patient.extension",
"sliceName" : "birthsex",
"min" : 0,
"max" : "1",
"type" : [
{
"code" : "Extension",
"profile" : [
"http://hl7.org/fhir/us/core/StructureDefinition/us-core-birthsex"
]
}
],
"mustSupport" : true,
"binding" : {
"strength" : "required",
"description" : "Code for sex assigned at birth",
"valueSet" : "http://hl7.org/fhir/us/core/ValueSet/birthsex"
},
"mapping" : [
{
"identity" : "argonaut-dq-dstu2",
"map" : "Patient.extension"
}
]
}
I was under the impression that binding could only be used if the type was codeable -- but in this case, the type is Extension. Surely the intent is that the binding should apply to Patient.extension:birthsex.value[x], but is this shortcut allowed? I noticed it does not actually get transferred into the snapshot.
Lloyd McKenzie (Oct 14 2020 at 17:53):
That's an error. The binding should have been declared on Extension.value
Lloyd McKenzie (Oct 14 2020 at 17:54):
Can you submit a tracker item?
Chris Moesel (Oct 14 2020 at 18:56):
Done: https://jira.hl7.org/browse/FHIR-29262
Eric Haas (Oct 16 2020 at 20:26):
I've looked back to see why we did that and it was done a long time ago I am guessing to make the binding show up in the differential view. Thanks for catching that error!
Chris Moesel (Oct 16 2020 at 20:48):
NP!
Last updated: Apr 12 2022 at 19:14 UTC
