Design and implement submissions via SFTP

[arnejduranovic]

User Story

As a sender of NSSP reports with only SFTP capabilities, I want to submit my reports via SFTP, so that I can submit NSSP reports according to my technical capabilities.

Description/Use Case

Prior to our next conversation with NSSP, it has been deemed a high priority to have an SFTP bucket(s) created and the ability to automatically submit ADT files put into that bucket(s) into ReportStream's Universal Pipeline. At this time, no functionality past ingesting into ReportStream successfully is needed.

• Pilot brief with known information
• Product Requirements for this ticket as of 10/7/2024:
  • SFTP locations for "test" files (non-PII) and "production" files (with PII) as part of this initial effort
  • SFTP locations are accessible by the Oklahoma hospital system (user outside of the CDC network)
  • A mechanism to automatically pull new HL7 v2.5.1 files from the SFTP into ReportStream
  • Files from the SFTP locations are received into ReportStream Staging ("test" files) and Production ("production" files) on a new topic specific to ADT data

Risks/Impacts/Considerations

Dev Notes

Michael and Victor were able to set up one of the Storage Accounts to act as SFTP.

For automated connection, look into using Azure File Store trigger

Acceptance Criteria

• [x] SFTP location(s) are set up and meet the above requirements
• [x] ReportStream can automatically ingest the files in the SFTP locations after they are uploaded
• [x] SFTP location addresses and how to access them are documented for a external users
• [x] How the automated submission engine works and where it is located is documented for a internal users

[MichaelEsuruoso]

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @david-navapbc @jack-h-wang @JFisk42 @kant777 @mkalish @thetaurean

[MichaelEsuruoso]

Please add your planning poker estimate with Zenhub @jalbinson