One governed path to every AI model

Why health-system AI governance has to be enforced on the request, and what that looks like in practice

Get the paper

What the paper covers

Health systems now run AI from many vendors and many internal teams, and each use case arrives as its own privacy review, security review, BAA negotiation, and integration. Governance committees and policy documents describe what should happen; they have no way to see or stop the requests that actually leave for a model provider. This paper lays out a model in which every AI request from an internal team or a vendor passes through one governed path deployed in the health system's own cloud account, where the institution's decisions about caller, purpose, data class, model, agreement, and identifiers are checked on each request and written to one record.

  1. 1. The problem as it exists in the hospital
  2. 2. Why policy and committees fail without enforcement at the request
  3. 3. The model: one path, two registries, and routes
  4. 4. The boundary
  5. 5. Vendors
  6. 6. Deployment and rollout
  7. 7. What to do this quarter