Henry Mulder

Programmamanager |
Verandermanager |
Ecosystems Engineer |
Verbinder

Systems Engineering by the Lead User in Healthcare: From
Personal Health Architecture to Emergent Interoperable
Platforms

Bio.
Henry Mulder is a systems engineer and independent consultant working at the intersection of systems architecture, digital transformation, and healthcare innovation. He co-authored Transforming Healthcare with DevOps: A Practical DevOps4Care Guide to Embracing the Complexity of Digital Transformation (Packt, 2022), which introduced the TiSH, Transformation into Sustainable Healthcare -framework.His current work explores how systems-engineering principles can help citizens, patients, care professionals, and organisations address the practical complexity of integrated and personalised care as documented in the blog series “Systems Engineering for Patients” where reflects on the development of a personal lifestyle and health-support architecture that combines technology, AI support, and coordination with care providers.

Abstract.

Healthcare digitization has created an integration paradox.Citizens, patients, informal caregivers and professionalsincreasingly use portals, wearables, monitoring devices,personal health environments, coordination tools and AIassistants, yet the practical burden of making thesecomponents work together often shifts to the user. Thisarticle explores how Systems Engineering (SE) can beapplied by a healthcare lead user to turn thisfragmentation into a coherent personal health architecture,and how repeated lead-user efforts may contribute to anemergent interoperable platform for optimizing scarcehealth and care resources.The case is based on the AptaVivar blog series “CursusSystems Engineering voor Patiënten”, in which a patientdesigns “MijnGLI”: a personal lifestyle and health-supportarchitecture integrating data from wearables, glucosemonitoring, hospital and general-practice portals, apersonal knowledge base, AI agents and care-networkcoordination. The case is interpreted through the 30life-cycle processes of ISO/IEC/IEEE 15288 and the INCOSESystems Engineering Handbook. This mapping shows that thelead user does not merely “use technology”, but performsrecognizable SE work: mission analysis, stakeholder-needsdefinition, requirements definition, architecturedefinition, design, implementation, integration,verification, validation, operation, maintenance, riskmanagement, configuration management, informationmanagement and quality assurance.The paper contributes three insights. First, lead users inhealthcare can act as early system architects. By buildingworking arrangements around real health missions, theyreveal missing interfaces, usability barriers, data gaps,unsafe assumptions and supplier lock-ins that are ofteninvisible in top-down innovation programs. Second, the mostimportant design object is not an individual app or device,but the interstitial space between components: the dataflows, consent arrangements, semantic mappings, feedbackloops and human decision points that make coordinated carepossible. Third, many structured N=1 experiments can becomea collective learning infrastructure. When lead-userarchitectures, requirements, workarounds, risks andoutcomes are captured consistently, they can informreference architectures, procurement criteria,interoperability agreements and platform governance.The article positions this approach as an application of SEin a novel context with direct relevance to adoption andscale-up challenges in healthcare. It proposes a “Lead UserHealth Architecture Lab” as a practical mechanism toconnect citizens, care providers, suppliers, researchersand regulators. Such a lab would maintain reusable userjourneys, data-source maturity models, privacy and safetypatterns, AI-validation practices, and small-scaleevaluation protocols. The expected outcome is not anotherisolated dashboard, but a pathway toward an open,user-directed, interoperable care platform that supportsprevention, lifestyle change, professional coordination andbetter allocation of human and technological resources. Ina sector where capacity is scarce and complexity isabundant, the lead user may be the modest but decisivestarting point for platform emergence.