Context
A provincial government needed a way to see across its healthcare system, not just within individual programs. Multiple health registries existed, but each had been built independently, with its own data model, update cadence, and owner. During a public health emergency, that fragmentation stopped being an inconvenience and became a real constraint on decision-making — leaders needed a current, trustworthy view of population health and operational capacity, and it didn't exist.
Challenge
The difficulty wasn't technical in the traditional sense — it was alignment. Clinical stakeholders were focused on patient care and data sensitivity. Government program leads had funding and policy priorities. Engineering and vendor teams had to reconcile inconsistent data structures across registries under real time pressure. No single stakeholder group had the authority or the full picture to resolve these tensions alone, and the usual timeline for this kind of integration work didn't fit the urgency of a pandemic response.
My Role
I served as Program Lead, accountable for the platform's delivery, stakeholder alignment, and governance. My job was to sit at the center of those competing priorities and turn them into a single, workable plan.
Approach
We started by structuring the ambiguity rather than jumping to a technical design: what decisions did leadership actually need to make, on what cadence, and with what confidence level in the data? That framing let us prioritize which registries to integrate first and which could wait.
From there, we designed a data architecture built around centralized and linked zones — bringing the most decision-critical data into a common, governed layer while leaving lower-priority sources loosely connected until they were needed. A metadata and governance catalog gave every stakeholder a shared reference for what each dataset meant, who owned it, and how current it was — which did more to build trust across clinical and government teams than any dashboard did.
I ran a steering cadence that kept clinical, government, and engineering leads in the same room on a regular basis, so decisions about scope, funding, and sequencing were made once, together, instead of being renegotiated by each group separately. As the initiative matured, we extended the platform to support additional provincial and national reporting requirements, which meant treating the original build as a foundation rather than a one-time project.
Outcome
The platform gave provincial leadership a working, near-real-time view of population health and operational capacity — supporting planning during active COVID-19 response and continuing to serve as reporting infrastructure afterward. Just as important, the governance model we built became the template the province used to bring additional registries and reporting requirements online without renegotiating the basic rules of engagement each time.
Large data integration programs are rarely blocked by technology. They're blocked by unresolved questions about ownership, trust, and priority — and a program lead's real job is to surface and resolve those questions before they show up as delivery risk.