Architect’s Survival Guide to Healthcare -
summary
Healthcare software must prioritize patient safety and data portability while surviving heavy regulation and constant change. Uses Domain-Driven Design to carve bounded contexts and anti-corruption layers around regulated code, keeps regulated device logic under design controls to avoid costly revalidation, and treats integrations as volatile. Cites Guardant360 blood test used by 100,000+ patients, rerun-lab example (10× TSH error), GDPR vs US retention conflicts, Anthem breach (79M users, $115M settlement), and a predictive turnaround-time algorithm that cuts customer calls.
AI-written summary · about
chapters (11)
- 0:00Introduction and healthcare stories
- 2:51Healthcare as a business and industry
- 6:21Putting the patient first
- 12:26Ubiquitous language in healthcare
- 18:28Identifying your customers
- 23:13Navigating healthcare regulations
- 29:18Security in healthcare systems
- 31:30Continuous process improvement
- 36:28Managing change in healthcare
- 41:09Domain-driven design in healthcare
- 48:40Summary and closing
related talks
54mArchitecture & Responsible Technology
12mCode of conduct developing medical grade software
27mThe Architect's Guide to Fortifying Software Security
22mProgramming HealthCare Silos
43mStartup Architecture – How much “it depends”?
45mSecurity Architecture, An Adventure?
01h 17mSecure by Design - Security Principles for the Working Architect
42mSoftware Architecture in the Age of Agility and DevOps