Stream: IG creation
Topic: Double-binding on Extension w/ valueCodeableConcept
Chris Moesel (Oct 02 2019 at 16:23):
In the mCODE IG, we have an obf-SpecimenType-extension that has a CodeableConcept value bound to v2 Specimen Type value set w/ example strength.
pasted image
In our GenomicReport profile, we include this extension, but we override the value set in the extension with a new one (GeneticSpecimenTypeVS w/ extensible binding). This is done by expanding the obf-SpecimenType-extension inline in the profile and overwriting the binding.
When the IG Publisher renders that profile page, however, it renders both the old value set (from the original extension definition) and the new value set (applied in the profile):
pasted image
This doesn't seem right.
One interesting tidbit is that for a short period, the IG Publisher apparently did not work this way, as this is a screen shot from the build.fhir.org, which was built on Aug 2:
pasted image
But the previous screen shots (w/ double-bindings) are from the latest build IG Publisher jar.
Lloyd McKenzie (Oct 02 2019 at 19:09):
The bindings are declared at two different levels I think? @Grahame Grieve
Chris Moesel (Oct 02 2019 at 20:38):
In the StructureDefinition JSON files, the binding is on the valueCodeableConcept element in both cases (the original extension and the profile). E.g.:
From obf-SpecimenType-extension extension:
{
"id" : "Extension.valueCodeableConcept",
"path" : "Extension.valueCodeableConcept",
// snipping out irrelevant stuff
"type" : [
{
"code" : "CodeableConcept"
}
],
// snipping out irrelevant stuff
"binding" : {
"strength" : "example",
"valueSet" : "http://terminology.hl7.org/ValueSet/v2-0487"
}
}
From onco-core-GenomicsReport profile:
{
"id" : "DiagnosticReport.extension:specimentype.valueCodeableConcept",
"path" : "DiagnosticReport.extension.valueCodeableConcept",
// snipping out irrelevant stuff
"type" : [
{
"code" : "CodeableConcept"
}
],
// snipping out irrelevant stuff
"binding" : {
"strength" : "extensible",
"valueSet" : "http://hl7.org/fhir/us/mcode/ValueSet/onco-core-GeneticSpecimenTypeVS"
}
}
Chris Moesel (Oct 07 2019 at 15:13):
Just checking in on this. @Grahame Grieve -- any idea what might be going on here?
Grahame Grieve (Oct 07 2019 at 15:13):
still on my todo list. I'm running behind
Chris Moesel (Oct 07 2019 at 15:26):
OK. NP. I just wanted to be sure it wasn't falling through the cracks. Would it be helpful for me to create a tracker?
Grahame Grieve (Oct 08 2019 at 00:13):
I don't think it will help right now.
Grahame Grieve (Oct 18 2019 at 03:22):
Is this still a problem @Chris Moesel ?
Chris Moesel (Oct 18 2019 at 13:55):
@Grahame Grieve -- I suspect it is, but I haven't tried with a new build for a little while, so we'll try w/ the latest publisher to confirm.
Chris Moesel (Oct 18 2019 at 18:17):
Good news. This doesn't seem to be an issue anymore with the extension rendering in the latest IG Publisher jar. Thanks, @Grahame Grieve!
Grahame Grieve (Oct 18 2019 at 18:47):
great thanks
Last updated: Apr 12 2022 at 19:14 UTC


