Stream: implementers
Topic: bulk data export error content
Moin Syed (Aug 16 2021 at 08:46):
What is content for error. I understand that it will be returned as OperationOutcome pointing to a ndjson file but what will be the content that should be captured? Should it be mentioned that "Condition" for a specific "patient" could not be captured? Do we have any sample/format/resource for that?
@Dan Gottlieb @Josh Mandel
Yunwei Wang (Aug 16 2021 at 13:14):
Bulk Data IG states that
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.
Moin Syed (Aug 17 2021 at 01:28):
@Yunwei Wang Thanks for the reply. But the error was during creation of the FHIR resource, how can we send it in the same format? Say I could not generate Condition for Patient x, I do not know its id and details so what should I send in error.ndjson?
Yunwei Wang (Aug 17 2021 at 02:30):
An OperationOutcome instance (or multiple instances) in error.ndjson, like
{ "resourceType": "OperationOutcome", "id": "1", "issue": [ { "severity": "fatal", "code": [error code for your situation], "details": { "text": "could not generate Condition for patient X" } } ] }
Christian Annel (Nov 17 2021 at 16:02):
Hey all,
I am currently working on connecting our distibuted ledger database to be interoperable across standard medical platforms. FHIR documentation suggests to use $export in FHIR URL to export build data. But in response of doing so I get a "404 not found." Would anyone know of any solutions/why this error occurs? We're using the open epic test servers found here;
~~~~~~ https://fhir.epic.com/Specifications?api=10171 ~~~~~~~
----- resource for bulk data: https://hl7.org/fhir/uv/bulkdata/index.html
And the other APIs are executing perfectly fine from the test servers however the "Bulk Export" operation is returning errors. We assume it's because there isn't bulk sample data available. Our work around is supposedly bundling the api calls. We realize that parsing may be necessary with the Bulk API since it would return everything as one document
thank you!
@Josh Mandel. ??
:)
Vassil Peytchev (Nov 17 2021 at 16:34):
@Christian Annel , please start a new topic by changing the subject in your post (I think you can do that if you edit your post). That way you will get better responses.
Giving more details about what server you are using, and how the $export operation fits into that will also be helpful.
Christian Annel (Nov 17 2021 at 17:21):
Vassil Peytchev said:
Christian Annel , please start a new topic by changing the subject in your post (I think you can do that if you edit your post). That way you will get better responses.
Giving more details about what server you are using, and how the $export operation fits into that will also be helpful.
Great, will do. Thank you.
Last updated: Apr 12 2022 at 19:14 UTC
