From the State Government edition of October 5, 2026
Utah extends its AI sandbox into clinical care with three 12-month pilots and master agreements with two health systems, but officials say they haven't decided which decisions AI should never make
Utah Department of Commerce, Office of Artificial Intelligence Policy (reported by FOX 13 Salt Lake City) · State AI regulatory sandbox / health care licensing · Utah statewide
- Publisher
- FOX 13 Salt Lake City
- Original publication
- 2026-10-05
- Source retrieved
- 2026-10-06
- Event date
- 2026-10-05
What happened
On Oct 5 Utah unveiled a health care pillar in its Pro-Human AI Initiative: master agreement frameworks with Intermountain Health and University of Utah Health covering data privacy and AI governance (individual departments may propose pilots the state must still approve), three new 12-month sandbox pilots (Nolla Health acne telehealth with dermatologist oversight; Expect Fitness AI-assisted pelvic-health physical therapy; August AI renewals of existing non-controlled prescriptions from a roughly 148-drug formulary, with no new prescriptions, dose changes or substitutions), and clinical advisory and third-party evaluation networks. Companies must submit plans for patient safety, consumer benefit and data reporting and notify the state before operating. The Medical Licensing Board, which objected to the earlier Doctronic renewal pilot, now has a working group supporting the office's review; a board member says this is not blanket approval. Commissioner Busse says officials don't yet know which clinical decisions AI should never make.
Why it matters
State agencies are using sandbox authority to grant temporary rule relief for AI, with licensing boards brought into the review. It is directly relevant to state regulators and to legislators who will use the results to set liability and transparency rules. Announced Oct 5.
Evidence and measured results
Opened the FOX 13 article (curl, UA SLED-research-bot/1.0, BeautifulSoup extraction); parsely-pub-date 2026-10-05. Confirmed the three pilots, 12-month terms, about 148 medications, master agreements, medical board working group, and the Busse quote. Cross-checked with Deseret News (Oct 5) and the Office of AI Policy evaluator page.
Limitations and uncertainty
News report of an announcement; no pilot results. Company statements (formulary size) are unverified. Health care is outside core state-government operations; relevance here is the state regulatory model. The earlier Doctronic pilot and medical board letter are already archived.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-05; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- State regulators want to test AI in licensed services without either blanket bans or unchecked deployment.
- Stakeholders
- State AI policy office
- Licensing boards
- State health agency
- Health system partners
- Legislators drafting liability rules
- Discovery questions
- How would you pilot AI in a licensed profession under current rules?
- Which decisions should AI never make alone, and who decides?
- What evidence would justify renewing a pilot?
- How would licensing boards join the review?
- Value hypothesis
- A pilot framework with defined reporting and evaluator roles can let a state learn from limited AI use before legislating.
- Potential engagement
- Design of an intake, review and evidence plan for one regulated AI pilot, including renewal criteria.
- Unsupported claims
- That Utah's pilots improve access or reduce costs
- That AI prescription renewals are safe
- That medical board support means approval of AI
- That this model fits every state's regulatory authority
Pre-sales engineering
Role takeaway
- Fit
- Data-sharing and reporting design for regulated pilots, not clinical AI development.
- Architecture and integration
- Use the master agreement as the data-governance base, define reporting feeds to the regulator, and log AI actions for evaluator sampling.
- Prerequisites
- Sandbox or regulatory-relief authority
- Master data and governance agreements
- Pre-launch safety and benefit plan
- Evaluator assignment
- Constraints
- Health privacy law
- No public data-flow detail
- Undefined AI-only decision boundary
- Health-sector specific
- Security
- Minimize patient data shared with vendors and evaluators, log access, and require escalation to licensed clinicians for out-of-scope cases.
- Proof of value
- Regulator can produce a pilot status report from submitted data
- Evaluator completes a sample review
- Escalation paths tested before launch
Delivery
Role takeaway
- Work
- Run pilot intake, board review, evaluator assignment, monitoring and 12-month renewal decisions.
- Dependencies
- Licensing board working group
- Health-system master agreements
- Evaluator network
- Ownership
- Utah Office of AI Policy with the relevant licensing board.
- Skills and adoption
- Regulators and board members need enough AI literacy to judge evidence; vendors need to report in a common format.
- Governance checkpoints
- Pre-launch plan approval
- Notification before operations
- Mid-term evaluator review
- Renewal decision at 12 months
- Acceptance criteria
- Proposed: every pilot has an evaluator and reporting plan before launch
- Proposed: renewal decisions cite evaluator findings
- Proposed: safety concerns reported within an agreed window
- Risks
- Review capacity falls behind the pipeline
- AI-only decision limits stay undefined
- Self-reported outcomes dominate
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Master agreements that let health-system departments propose pilots imply repeated data-sharing and EHR integration under one framework; August AI's design cites improved EHR integration. Specifics are not public in this article.
Governance
Who approves, reviews and stays accountable for outcomes?
Combines temporary regulatory relief with licensing-board review, pre-launch plans, 12-month terms and independent evaluation, while leaving the boundary of AI-only decisions undefined.
Security and privacy
What data, permissions and controls need testing?
Master agreements address data privacy and AI governance; the article provides no detail on data flows or patient consent.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Pitched as stretching a scarce clinical workforce (for example, a limited number of physical therapists serving more patients remotely); effects on clinicians are untested.
Procurement
What should contracts, pricing and exit terms secure?
Not a procurement, but the master-agreement approach is a reusable way for a state to pre-negotiate privacy and governance terms with large partners before individual projects.
Operating model
Which teams own the service once it runs?
A small policy office coordinates commerce, health, licensing boards and health systems; capacity to review a growing pipeline of pilots is an open question.
Publication history
- 2026-10-05State Government · Issue 305 resources
Stable resource ID: utah-health-ai-sandbox-pilots-fox13-20261005