The page says the backend that should store user-uploaded documents has left a patient video in processing 18 minutes after upload. The API is healthy, Postgres connections are available, and no worker is obviously stuck. What the on-call cannot tell is whether the browser finished sending the bytes, whether multipart assembly completed, or whether the metadata row points at an object that exists.
Short answer: store large user-uploaded documents and health media in object storage, keep ownership and workflow metadata in Postgres or MySQL, and let the client upload without proxying the bytes through the application.
That split is usually cheaper and simpler to scale than database BLOBs, but cost is not the deciding signal here. Access control, region, retention, deletion, and the processor boundary are.…