5 Things I Learned Working With A Lead BA On A Cross-Border EHR System

As a dev, there is nothing I hate more than spreadsheets of "enterprise digital transformation" or 40-page PDFs of "perfect world" scenarios that sound smart in a meeting but totally lack actual logic. We’ve all seen those requirements: "System should magically sync legacy data with the new cloud DB." That usually results in hours of Slack argument threads. ALL. DAY. 😫 Too many times, the BA writes the "dream," and the technical nightmares are left for the devs to figure out. That was my baseline until I got pulled into a high-stakes HealthTech build with Mai Anh Le, our Lead BA at Sun*. After watching her navigate a cross-border EHR modernization project, I’ve had to completely rethink what a BA actually does. 👇 Here is what I learned from a global scaling EHR integration project with a BA who actually knew what "business logic" she needed to analyze and what requirements should be delivered to the tech team: 1. Map the physical user movement before designing the schema I used to grab