Stream: implementers
Topic: FHIR Batch/Transaction files over SFTP
Igor Sirkovich (Apr 26 2018 at 19:34):
I'm wondering if anyone knows about any initiative that uses FHIR Batch/Transaction as JSON files submitted over FTP/SFTP rather than over HTTP.
We might need to add a SFTP channel for some legacy client applications that are unable to use our HTTP API and I just wanted to see if anyone else has already done this.
nicola (RIO/SS) (Apr 26 2018 at 20:00):
We use this approach but with kafka topics
Igor Sirkovich (Apr 26 2018 at 20:13):
I'm not familiar with Kafka yet, though we plan to test it soon. I'm wondering if you've created a specification for your clients describing structure and naming convention for the files, folders where they should submit their files to, etc. Is there any industry standard around this?
I'm also wondering if you treat this as a batch/transaction or as a message (using MessageHeader as the first resource in the bundle). My feeling is that messaging paradigm might be a better fit for this use case.
Nick Hatt (Apr 26 2018 at 21:26):
I think it would depend on whether or not it's a Message - there is some additional baggage that comes along with them. MessageDefinition, EventDefinition etc. would be part of the messaging flow.
Jeff Graham (May 02 2018 at 01:31):
We also use kafka to stream data and think it would be a great approach for bulk fhir. There are a lot of interesting options that fhir could benefit from -i.e. avro/protobuf.
Łukasz Dywicki (May 02 2018 at 22:02):
I suppose it needs some additional care due to Kafka nature. One and only one mode brings certains overhead which can't be ignored and if Kafka is forced to work in such mode its performance (supposingly) is no different from other messaging platforms.
Last updated: Apr 12 2022 at 19:14 UTC
