Included Health’s Post

As a software/data engineer, I have been faced with these exact issues in code. When I engineered my first autonomous client data ingress and egress system. I was faced with many desperate systems with many federate layers. This cause a lot of unreliable data reports and undetectable failures with my system. I identified where the problem was, kept pointing out the issues between contracted dev teams and third party vendors, by stepping back and saying the similar phrase "does it bring joy" instead "does simply give me data". That thinking brought more simplified minimalistic processes that was readable, reusable, and was easier to maintain. I've always heard "less is more", never thought it would work in coding.

Akin Oyalowo, I could not agree more. A disciplined approach to process engineering and redesign is crucial in the cross-functional world that is healthcare delivery. Slapping technology on top will hide the mess a little better but it won’t achieve optimal outcome. How do we avoid taking shortcuts? By relentlessly asking the question “are we serving our members better with this?” which is the core to our mission. Concretely, a process engineering method to start with that I have liked in the past is Value Stream Mapping. Happy to chat about it one of these days. Thanks for raising this important topic.

Yes! to subtracting. Well put, Akin.