Bulk Data Access IG, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 4.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/bulk-data/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/bulkdata/OperationDefinition/bulk-submit-status | Version: 4.0.0 | ||||
| Standards status: Trial-use | Maturity Level: 2 | Computable Name: BulkSubmitStatus | |||
This operation receives status updates about the submission after a Data Provider has kicked off a Bulk Submit operation. For example, the Data Consumer may indicate files it was unable to retrieve, resources that failed validation, or resources that could not be merged into an existing data set. The Data Consumer may also return processed data such as computed quality measures or de-identified versions of the submitted data. The Data Provider receives a 202 Accepted response with a Content-Location header and then polls that URL according to the FHIR Asynchronous Bulk Interaction Pattern.
Language: en
URL: [base]/$bulk-submit-status
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | submitter | 1..1 | Identifier | The submitter must match a system and code specified by the Data Consumer (coordinated out-of-band or in an implementation guide specific to a use case). | ||
| IN | submissionId | 1..1 | string | The value must be unique for the | ||
| IN | _outputFormat | 0..1 | string | The format for the generated bulk data files used to return OperationOutcome resources related to the submission status and, when applicable, other resources. Servers SHALL support ndjson, and MAY support other output formats. Servers SHALL support the full content type of |