<aside> 💡

Upload your work as a zip on this form. If the architecture write-up or other deliverables live in Notion or a private repo, include those links in the zip (typically in the README). For questions, email [email protected].

</aside>

Context

Parallel has just signed a new hospital. The goal is to deploy Parallel into production within 4 weeks, with the ultimate objective being to automatically export the hospital’s data & documents to Parallel.

The hospital has around 500 beds and uses a legacy hospital information system.

During the kickoff, you learn that:

• PMSI data is exported every day and deposited on an SFTP server.
• Some medical documents are only accessible inside the hospital's DPI.
• The DPI is a Windows desktop application accessible only from the hospital network.
• The hospital does not allow inbound connections to its network.
• The hospital can provide a Windows or Linux VM inside its infrastructure.
• Files received from the hospital may occasionally contain duplicate, incomplete or malformed stays.
• The IT department wants a clear description of the network flows and data exchanged with Parallel.
• The DIM would like to start a pilot within 3 weeks.
• The hospital does not have a developer available to support the project.

You are the Forward Deployed Engineer responsible for the deployment.

Your objective is to get the hospital running reliably in production.

1. Discovery

Before implementing anything, explain how you would approach the first few days of the deployment.

What information would you want to collect from: