You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next to the mandatory FHIR resource type you can also optionally specify a valid FHIR search query to limit downloaded resources. The query must not start with a `?` char.
216
+
If the optional resource-type is given, the corresponding type-level search will be used. Otherwise, the system-level search will be used and all resources of the whole system will be downloaded.
217
+
218
+
The --query flag will take an optional FHIR search query that will be used to constrain the resources to download.
214
219
215
220
With the flag --use-post you can ensure that the FHIR search query specified with --query is send as POST request in the body.
216
221
217
-
Using POST can have two benefits, first if the query string is too large for URL's, it will still fir in the body. Second if the query string contains sensitive information like IDAT's it will be less likely end up in log files, because URL's are often logged but bodies not.
222
+
Using POST can have two benefits, first if the query string is too large for URL's, it will still fine in the body. Second if the query string contains sensitive information like IDAT's it will be less likely end up in log files, because URL's are often logged but bodies not.
218
223
219
224
The next links are still traversed with GET. The FHIR server is supposed to not expose any sensitive query params in the URL and also keep the URL short enough.
220
225
226
+
Resources will be either streamed to STDOUT, delimited by newline, or stored in a file if the --output-file flag is given.
221
227
222
228
As soon as the download has finished you will be shown a download statistics overview that looks something like this:
223
229
@@ -247,8 +253,8 @@ The count-resources command is useful to see how many resources a FHIR server st
0 commit comments