<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Access control on phiz</title><link>https://phiz.ca/tags/access-control/</link><description>Recent content in Access control on phiz</description><generator>Hugo</generator><language>en</language><copyright>Powered by [Wellington-Dufferin-Guelph Public Health](https://wdgpublichealth.ca/)</copyright><lastBuildDate>Fri, 20 Feb 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://phiz.ca/tags/access-control/index.xml" rel="self" type="application/rss+xml"/><item><title>MLOps in Public Health: Workspaces, Pipelines, and Governance</title><link>https://phiz.ca/posts/2026-02-kubeflow/</link><pubDate>Fri, 20 Feb 2026 00:00:00 -0500</pubDate><guid>https://phiz.ca/posts/2026-02-kubeflow/</guid><description>&lt;p>Modern data science and ML work depends on consistent environments, controlled access patterns, and reproducible workflows. In public health, these needs underpin governance as much as they support productivity.&lt;/p>
&lt;p>At Wellington-Dufferin-Guelph Public Health (WDGPH), we have found that the simplest way to address both delivery and risk is to standardize how tools are delivered into managed, isolated environments, and to route repeatable work through governed pipelines. This post focuses on those two foundations, developer environments and pipelines, within a larger MLOps program.&lt;/p></description></item></channel></rss>