Stream: bulk data
Topic: Job History
Bill Harty (Jun 30 2021 at 15:05):
Hi, working with CMS / BCDA. Wondering in BULK FHIR if there exists (or under consideration) a mechanism to request a job history e.g. a bundle/listing of previously requested jobs by the client - the output would return things like job id, status, date/time, etc. We have clients, who for various reasons (auditing, reporting, lost ids, lack of automation) could use a history. I looked thru current and STU2 versions of BULK FHIR spec and didn't see anything in this regard. Any thoughts or advice on creating this call in a way that is conformant with BULK and/or FHIR would be much appreciated. Thanks!
Josh Mandel (Jun 30 2021 at 16:55):
This hasn't come up before --- it's a good question. Could perhaps be modeled with a custom operation (e.g., GET $export-jobs?status=pending, returning a Bundle of Tasks or some-such). Or if you're going to model an export job as a Task, then this could be enabled using the RESTful search API on Tasks (e.g., GET Task?code=export-job&status=in-progress).
Bill Harty (Jul 01 2021 at 13:53):
Thanks for the feedback. I had been considering using the Task resource in a bundle as one possibility, so I think we'll at least poc that approach. thx again
Last updated: Apr 12 2022 at 19:14 UTC
