Stream: bulk data
Topic: Experimental query parameters
RB Johnson (Sep 10 2020 at 14:47):
In the v1.2 export spec section 5.1.5, Query Parameters, _elements and includeAssociatedData are both marked as experimental and included in the list of query parameters. Below them though is section 5.1.7, Experimental Query Parameters, which explains the _typeFilter parameter that isn't listed in section 5.1.5. What is the thought behind this separation, or is it a hold over from the v1.0 spec?
Dan Gottlieb (Sep 10 2020 at 15:23):
It's a holdover and should probably be moved up to the parameters table. In my mind _typeFilter is more experimental though since it has a complex syntax with potentially confusing semantics while _elements and includeAssociatedData are more straight forward. I'm not sure if this matches how others think of the parameters though, or how to indicate this in the IG.
Dan Gottlieb (Sep 10 2020 at 15:24):
Does anyone have thoughts on this? Also, is anyone using _typeFilter in production (and if so, what has been your experience)?
Michele Mottini (Sep 10 2020 at 15:27):
We just added _typeFilter to our server and we are going to use it in production - previously we added some custom extra parameters to do filtering but in the end we bite the bullet and implemented full _typeFilter
Michele Mottini (Sep 10 2020 at 15:28):
It was easy enough
Michele Mottini (Sep 10 2020 at 15:28):
I think we'd like to have it in the standard as is
Josh Mandel (Sep 10 2020 at 15:29):
Wow! That's awesome @Michele Mottini
Dan Gottlieb (Sep 10 2020 at 15:31):
Agreed! @Michele Mottini did you have to exclude anything, or were you able to implement the full set of search params?
Michele Mottini (Sep 10 2020 at 15:35):
I think we pass the search parameters to our resource handlers, so all parameters that are implemented for each resource in our server work for bulk export - but let me double check
Michele Mottini (Sep 10 2020 at 15:42):
Yes, all parameters are supported
Michele Mottini (Sep 10 2020 at 15:43):
And if the client uses parameters that are not supported (or simply wrong) same behavior as a normal resource search: they are ignored or cause an error depending on a server-side option (we do not support the Prefer header for that)
Farhan A (Oct 29 2020 at 18:24):
Hi John,
I will need your input. I am not able to see the bulk export filtering working. It's returning all the rows whether state is IL or any other state
POST url is http://<servername>:<port>/$export
Here is the body:
{
"resourceType": "Parameters",
"parameter": [
{
"name": "_outputFormat",
"valueString": "application/fhir+ndjson"
},
{
"name": "_type",
"valueString": "Location"
},
{
"name": "_typeFilter",
"valueString": "Location?address-state=IL"
}
]
}
Last updated: Apr 12 2022 at 19:14 UTC
