Stream: bulk data
Topic: Shall server metadata have $export operation
Yunwei Wang (Aug 30 2019 at 13:27):
Logically bulk-data server shall have $export operation in metadata. But I don't find such statement in Bulk Data IG and smart-it reference server does not have $export operation in metadata.
Any idea?
@Josh Mandel @Dan Gottlieb
Dan Gottlieb (Aug 30 2019 at 13:40):
The metadata is described in the IG here: http://hl7.org/fhir/uv/bulkdata/STU1/CapabilityStatement-bulk-data.json.html .
Dan Gottlieb (Aug 30 2019 at 13:41):
@Vladimir Ignatov it looks like the capability statement on the bulk data server is a little behind the spec
Yunwei Wang (Sep 05 2019 at 13:27):
@Dan Gottlieb When I read IG capability statement, I saw that group-export operation is declared in the rest level. Should that be under group resource? According to the IG, group level export endpoint is GET [fhir base]/Group/[id]/$export.
Dan Gottlieb (Sep 05 2019 at 16:39):
Yup, looks like an error in the conformance statement. @Josh Mandel do you know the mechanism for doing these sort of corrections in a balloted IG?
Josh Mandel (Sep 05 2019 at 18:22):
Thanks for catching this! I've added GF#23864 to track.
Josh Mandel (Sep 15 2019 at 16:13):
I've also added GF#24434 to track a set of issues for technical correction.
Sam Sayer (Sep 15 2019 at 16:24):
@Dan Gottlieb OK, I'll stop over after lunch. Would like to discuss using Parameter resources
Nick Robison (Sep 15 2019 at 17:43):
Just chiming in, I think the STU3 Capability Statement doesn't support listing operations at the rest level, any recommendations for dealing with this? We have our listed in the sever operations. Possible I'm missing something.
Josh Mandel (Sep 15 2019 at 19:03):
In STU3 it's just http://hl7.org/fhir/STU3/capabilitystatement-definitions.html#CapabilityStatement.rest.operation -- so you can only list at the REST (i.e., top) level, and not at the resource-type level. So you'd just document everything there, I suppose.
Patrick Cosmo (Sep 15 2019 at 19:33):
GCP Fhir Store with $export
This is probably a bit too late for most, but in case you're interested to try this, it is now available:
1. To get an access token:
curl -X POST https://pcosmo72-eval-prod.apigee.net/fhir/oauth2/accesstoken -H 'Accept: application/json' -H 'Authorization: Basic VUZHSGhGdnJzb0d4Z0RRRkI0anpNdXVHVGp1UDczR1Y6anBIODBDWGdiblpYSmp5NQ==' -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -d '{ "grantType" : "client_credentials", "scopes" : "user/*.read" }'
This call will return an access token which you will need to use in the Authorization Bearer header for calls to the following FHIR store.
2. FHIR Path: https://pcosmo72-eval-prod.apigee.net/fhir/stu3
For example, export (replace <your name> so that the export goes into your own specific bucket sub-directory, and don't forget to replace <access token> as well):
curl -i -X GET https://pcosmo72-eval-prod.apigee.net/fhir/stu3/\$export?gcsDestination=gs://fhirexport/**<your name> -H 'Accept: application/fhir+json' -H 'Authorization: Bearer <access token>**' -H 'Cache-Control: no-cache' -H 'Content-Type: application/fhir+json;charset=utf-8' -H 'Prefer: respond-async'
Note that the operation ID will be returned as the last value of the Content-Location header that is returned. The Content-Location value itself is wrong because the FHIR store is behind a proxy, however, the operation ID is correct, for example:
Content-Location: projects/pcosmo-test/locations/us-central1/datasets/connectathon/fhirStores/test001/exports/7011541669862440961
You can use this operation ID to get the operation status:
curl -X GET https://pcosmo72-eval-prod.apigee.net/fhir/stu3/exports/**7011541669862440961** -H 'Accept: application/fhir+json;charset=utf-8' -H 'Authorization: Bearer NEVOpfc4fhGAbfp15c7vvZA8u4II' -H 'Cache-Control: no-cache' -H 'Content-Type: application/fhir+json;charset=utf-8'
In order to get access to the GCS bucket send me (pcosmo@google.com) the email for your GCP account and I'll give you read access.
Last updated: Apr 12 2022 at 19:14 UTC
