We need to aligned with the updated FHIR bulkdata export spec to provide operationoutcomes for errors during the export just like what we did for bulkdata import.
The javabatch job needs to generate ndjson file(s) for the errors and push to COS and bulkdata operation need to add them to the "error" part of the response.
array of error file items following the same structure as the output array.
*Errors that occurred during the export should only be included here (not in output). If no errors occurred, the server SHOULD return an empty array. Only the OperationOutcome resource type is currently supported, so a server SHALL generate files in the same format as bulk data output files that contain OperationOutcome resources.
We need to aligned with the updated FHIR bulkdata export spec to provide operationoutcomes for errors during the export just like what we did for bulkdata import. The javabatch job needs to generate ndjson file(s) for the errors and push to COS and bulkdata operation need to add them to the "error" part of the response.
{ "transactionTime": "[instant]", "request" : "[base]/Patient/$export?_type=Patient,Observation", "requiresAccessToken" : true, "output" : [{ "type" : "Patient", "url" : "http://serverpath2/patient_file_1.ndjson" },{ "type" : "Patient", "url" : "http://serverpath2/patient_file_2.ndjson" },{ "type" : "Observation", "url" : "http://serverpath2/observation_file_1.ndjson" }], "error" : [{ "type" : "OperationOutcome", "url" : "http://serverpath2/err_file_1.ndjson" }], "extension":{"http://myserver.example.org/extra-property": true} }