r/HealthTech • u/oldabba • 10d ago
Question Mobile app development missing encryption standards
Major facepalm moment over here, and honestly, I'm just exhausted. We kicked off a mobile app development project for our patients, but it turns out the devs completely forgot to bake encryption standards into the architecture level. It's like they just built a regular consumer app, slapped a medical logo on it, and ignored the fact that it handles highly sensitive PHI data. Now we are stuck rewriting the entire security module from scratch, which is setting us back months and costing us a ridiculous amount of money.
I'm beyond stressed because the compliance audits are coming up, and we have nothing to show. For the HealthTech experts here, how do you actually control the development stages to prevent this kind of rookie disaster?
Do you have a specific checklist or audit process you run during the early sprints? I really need to make sure this never happens to us again, so any tips on vetting dev teams would be great.
1
u/eyanez13 7d ago
This is exactly why security needs to be part of the architecture from day one, not something added near the finish line. I'd make encryption at rest and in transit mandatory requirements before approving any development sprint. Retrofitting security is almost always more expensive.
1
u/2ndaccountofprivacy 6d ago
honestly fire that agency. basic encryption isnt an add on in healthcare, its the bare minimum. going forward never pay out milestones until code passes an independent security audit
1
u/vijayamin83 7d ago
Make security an acceptance criterion from sprint one, not a final check. Require a one-page data flow showing where PHI lives, how it moves, and who can read it, and demo encryption, logins, access roles, and audit logs every sprint. When vetting teams, ask: what did you build on your last health project, and will you sign a BAA?