An old idea from enterprise integration deserves more attention in the AI conversation: separate how a ‘system is built’ from ‘how it runs’. Design time is where teams assemble connectors, workflows, interfaces and business rules. Runtime is where those pieces execute, with defined permissions and controls. MCP can play a role in both. The model […]
An old idea from enterprise integration deserves more attention in the AI conversation: separate how a ‘system is built’ from ‘how it runs’. Design time is where teams assemble connectors, workflows, interfaces and business rules. Runtime is where those pieces execute, with defined permissions and controls. MCP can play a role in both. The model […]
A vendor says “sovereign AI,” a buyer nods, and both may leave with different ideas about what was promised. Where the data is stored. Where are your databases, documents and backups? Who can access them, and who manages the encryption keys? Local hosting can address storage requirements. You also need to understand how access is […]
Integration used to be largely proprietary. Twenty years ago, connecting two enterprise systems often meant buying a middleware stack and staying bought. Connectors were vendor-specific, and teams repeated much of the integration work for each project. Then the interfaces opened up. SOAP and WSDL, backed by incumbents such as IBM and Microsoft. REST, emerging from […]
My notes and reflections from Canada’s largest digital health gathering. This week, I spent three days at e-Health26, Canada’s largest digital health gathering, hosted by Digital Health Canada, CIHI, and Canada Health Infoway, in Halifax. I returned home with one strong belief: the future of Canadian healthcare won’t be decided by who launches the most […]
