1. FHIR R4 APIs with Bulk Data Access
  2. Tasks
  3. Bulk Export

Get file URLs to download the exported resources

get

/bulk-export/files/{File_ID}

Note: The FHIR API endpoints described below are currently pending production deployment for electronic health record (EHR) environments. Developers are welcome and encouraged to develop against the specifications in anticipation of production availability, which will be announced at a later date.

Once an export is complete, the status request returns file URLs that you can use to download the exported resources. See the x-complete example response for the bulk export operation.

GET <File URL from status response>

Note:

  • An exported ndjson file contains only a single resource type and the same resource type can have multiple files.
  • Files expire after 30 days.

Retrieval of Attachments

  • Binary resources are not returned by bulk data operations.
  • Attachment references must be retrieved separately using the Binary resource URL from the DocumentReference.content.attachment and DiagnosticReport.presentedForm fields from the export files.

Request

Path Parameters
Header Parameters

  • The media type to be requested. Refer to what the resource's operation produces for what is supported.

    Example: application/fhir+json

  • Contains the credentials to authenticate a consumer to the service. This should be the OAuth2 Bearer Token.

There's no request body for this operation.

Back to Top

Response

Default Response

Example Request: 
GET https://fhir-ehr.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/bulk-export/files/<File_ID>
Example Response: 
Status: 307 Temporary Redirect
Location: https://cerner-opensvc-bulkfhir-processed.s3.us-west-2.amazonaws.com
Headers
  • Indicates the redirect URL that must be followed to download the files.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the opc-request-id, if present.
Back to Top