Stream: implementers
Topic: Search parameter expressions that resolve to BackboneElem...
Lee Surprenant (Oct 09 2019 at 16:23):
The following SearchParameter definitions are tripping up our server:
- SubstanceSpecification-code:
"expression" : "SubstanceSpecification.code" - StructureDefinition-ext-context:
"expression" : "StructureDefinition.context"
In both cases, the expression resolves to a BackboneElement and we don't know how to properly extract the values. Is the process of extracting values from these complex types defined somewhere in the specification?
Lee Surprenant (Oct 09 2019 at 16:25):
in the case of SubstanceSpecification-code, should it just be "SubstanceSpecification.code.code" ?
Lee Surprenant (Oct 09 2019 at 16:25):
and in the case of StructureDefinition-ext-context, perhaps "StructureDefinition.context.type" ?
Paul Church (Oct 09 2019 at 16:37):
I can't figure out what StructureDefinition-ext-context is supposed to do in R4. The field 'StructureDefinition.context' was a string field in STU3.
Paul Church (Oct 09 2019 at 16:39):
SubstanceSpecification.code.code makes sense to me
Lee Surprenant (Oct 09 2019 at 16:45):
Thanks Paul. I suspect SubstanceSpecification-code has a similar story; will open a GForge ticket for these two...they are the only ones I've hit like this so far.
Lee Surprenant (Oct 09 2019 at 16:45):
wonder if its too late to make the technical correction...
Lee Surprenant (Oct 09 2019 at 16:52):
actually, looks like SubstanceSpecification-code has already been fixed in the latest build: http://build.fhir.org/substancedefinition.html#search
Lee Surprenant (Oct 09 2019 at 17:00):
opened https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=24917
Grahame Grieve (Oct 10 2019 at 06:36):
@Yunwei Wang more technical correction candidates please. If we can approve these on the call next week, I can get them in the technical correction.
Last updated: Apr 12 2022 at 19:14 UTC
