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.

Healthcare digitization has created an integration paradox. Citizens, patients, informal caregivers and professionals increasingly use portals, wearables, monitoring devices, personal health environments, coordination tools and AI assistants, yet the practical burden of making these components work together often shifts to the user. This article explores how Systems Engineering (SE) can be applied by a healthcare lead user to turn this fragmentation into a coherent personal health architecture, and how repeated lead-user efforts may contribute to an emergent interoperable platform for optimizing scarce health and care resources.

The case is based on the AptaVivar blog series “Cursus Systems Engineering voor Patiënten”, in which a patient designs “MijnGLI”: a personal lifestyle and health-support architecture integrating data from wearables, glucose monitoring, hospital and general-practice portals, a personal knowledge base, AI agents and care-network coordination. The case is interpreted through the 30 life-cycle processes of ISO/IEC/IEEE 15288 and the INCOSE Systems Engineering Handbook. This mapping shows that the lead user does not merely “use technology”, but performs recognizable SE work: mission analysis, stakeholder-needs definition, requirements definition, architecture definition, design, implementation, integration, verification, validation, operation, maintenance, risk management, configuration management, information management and quality assurance.

The paper contributes three insights. First, lead users in healthcare can act as early system architects. By building working arrangements around real health missions, they reveal missing interfaces, usability barriers, data gaps, unsafe assumptions and supplier lock-ins that are often invisible in top-down innovation programs. Second, the most important design object is not an individual app or device, but the interstitial space between components: the data flows, consent arrangements, semantic mappings, feedback loops and human decision points that make coordinated care possible. Third, many structured N=1 experiments can become a collective learning infrastructure. When lead-user architectures, requirements, workarounds, risks and outcomes are captured consistently, they can inform reference architectures, procurement criteria, interoperability agreements and platform governance.

The article positions this approach as an application of SE in a novel context with direct relevance to adoption and scale-up challenges in healthcare. It proposes a “Lead User Health Architecture Lab” as a practical mechanism to connect citizens, care providers, suppliers, researchers and regulators. Such a lab would maintain reusable user journeys, data-source maturity models, privacy and safety patterns, AI-validation practices, and small-scale evaluation protocols. The expected outcome is not another isolated dashboard, but a pathway toward an open, user-directed, interoperable care platform that supports prevention, lifestyle change, professional coordination and better allocation of human and technological resources. In a sector where capacity is scarce and complexity is abundant, the lead user may be the modest but decisive starting point for platform emergence.