The submitter SHALL match a system and code specified by the Data Consumer (coordinated out-of-band or in an implementation guide specific to a use case).

The value SHALL be unique for the submitter.

System of http://hl7.org/fhir/event-status, code of in-progress (default if parameter is omitted), completed or stopped. Once a request has been submitted with a submissionStatus of stopped or completed, additional requests SHALL NOT be submitted for that submitter and submissionId combination. At least one of the submissionStatus and manifestUrl parameters SHALL be populated.

Url pointing to a Bulk Export Manifest with a pre-coordinated FHIR data set. Files in multiple submitted manifests with the same submitter and submissionId SHALL be treated by the Data Consumer as if they were submitted in a single manifest. This parameter MAY be omitted when the operation is being called to set the submissionStatus to completed or stopped. The value SHALL be unique for all manifests that share a submitter and submissionId combination. At least one of the submissionStatus and manifestUrl parameters SHALL be populated. When this parameter is populated, the fhirBaseUrl parameter SHALL also be populated.

The url of a previously submitted manifest that has the same submissionId and submitter as this request. When provided, Data Consumer SHALL replace the data in the referenced manifest with the one in the current request. If the url is invalid or the Data Consumer is unable to replace the data, it SHOULD respond to the request with an OperationOutcome describing the error.

The format for the Bulk Data files in the manifest. The MIME-type MAY include a MIME-type parameter of fhirVersion as described in the FHIR specification to indicate which version of FHIR the resources in the Bulk Data files are based on. When omitted, defaults to application/fhir+ndjson (Newline Delimited JSON) with a version of FHIR determined by the Data Consumer. All of the resources in a submission SHALL use the same version of FHIR.

Base url to be used by the Data Consumer when resolving relative references in the submitted resources. When the manifestUrl parameter is populated, this parameter SHALL be populated.

HTTP headers that the Data Consumer SHOULD use when requesting a data file from the Data Provider.

Location that a Data Consumer can use to obtain the information needed to retrieve files protected using OAuth 2.0. The url SHALL be the path to a FHIR Authorization Endpoint and Capabilities Discovery file or another OAuth 2.0 Protected Resource Metadata file that is registered in the IANA Well-Known URIs Registry.

Encryption key information for the Data Consumer to decrypt retrieved data files from the Data Provider.

If omitted, defaults to a system of http://hl7.org/fhir/uv/bulkdata/ValueSet/file-encryption-type and code of jwe.

For the system of file-encryption-type and code of jwe, populate with the JSON Web Encryption structure to deliver a Content Encryption Key for the Data Consumer to decrypt retrieved data files from the Data Provider.

Child parameters can be added under this parameter to pass pre-coordinated data relevant to the submission from the Data Provider to the Data Consumer. Each child parameter name SHALL be an absolute URL. Specific child parameters are defined in implementation guides for particular use cases.

An absolute URL identifying this metadata parameter.

The value for this metadata parameter.

Child parameters MAY be added under this parameter to pass pre-coordinated options relevant to how the data will be processed from the Data Provider to the Data Consumer. For example, a Data Consumer might allow the Data Provider to specify whether or not existing data should be replaced with the data in the submission. Each child parameter name SHALL be an absolute URL. Specific child parameters are defined in implementation guides for particular use cases.

An absolute URL identifying this import parameter.

The value for this import parameter.