{"resourceId":"utah-medical-board-ai-pilot-consultation-2026","versions":[{"version":"external-7d164862411ee663d8ba1aeb48feec09c9e096dca0c4c1c174b588df05e25bc3","resource":{"id":"utah-medical-board-ai-pilot-consultation-2026","title":"Utah Medical Board objection exposes disagreement over pre-launch consultation","organization":"Utah Medical Licensing Board","sector":"State professional licensing oversight","geography":"Utah, United States","publishedAt":"April 20, 2026","publicationDate":"2026-04-20","eventDate":"2026-04-20","sourceName":"Utah Medical Licensing Board letter to Commerce and OAIP","sourceLabel":"Primary oversight correspondence","sourceUrl":"https://commerce.utah.gov/wp-content/uploads/2026/04/doctronic-letter-from-medical-board.pdf","evidenceClass":"standards-guidance","outcomeClass":"cautionary","topics":["governance-procurement","operating-model"],"finding":"The Board said it learned of the pilot after implementation and requested suspension pending discussion.","sledRelevance":"A state-agency consultation and decision-rights case, not proof of clinical harm.","evidence":"The April 20 letter is an oversight objection, not an outcomes study. Commerce's inspected April 21 response says medical experts reviewed the pilot and declines suspension, citing Phase 1 human review.","architectureImplications":"Interpretation: translate domain review requirements into explicit action and escalation gates; the letter specifies no hosting design.","governanceImplications":"Interpretation: establish which advisory and authorizing bodies review a pilot before launch and record unresolved disagreement.","securityPrivacyImplications":"Interpretation: include privacy and security specialists in pre-launch review; the letter supplies no technical assessment.","caveats":"A requested suspension is not an enacted suspension. The response is at https://commerce.utah.gov/wp-content/uploads/2026/04/Medical-Board-Doctronic-Response.pdf. Competing official positions are preserved; no adjudication of legal authority or current clinical safety is made.","streamIds":["state-government"],"roles":{"sales":"Interpretation: Explore governance coordination with the regulatory program owner, licensing board, agency counsel and domain specialists. Ask who must be consulted before launch and how dissent changes the decision. A bounded readiness review could map decision rights and produce a documented consultation record. The value hypothesis is fewer unresolved responsibilities at deployment, not a guarantee against harm or controversy. Do not infer that the pilot lacked all clinical review: the agency response disputes that implication. Keep advisory objections separate from binding action and avoid treating this dispute as an opportunity to endorse or displace a supplier.","engineering":"Interpretation: Use the dispute to test whether approval evidence is connected to deployable permissions. Model the workflow and identify where an authorized pause, scope change or review requirement must take effect. Prerequisites include agreed decision owners, a versioned approval record and access to configuration evidence. Proposed validation should trace a hypothetical change from domain review through authorization, deployment and rollback, then confirm that downstream action stops when required. Protect case data during review. This correspondence supports governance design questions; it provides no model benchmark, integration specification, hosting recommendation or technical proof that safeguards succeed.","delivery":"Interpretation: Convene program and oversight owners to document consultation timing, escalation routes and release checkpoints. The authorizing agency owns the decision; advisory specialists own their recorded assessment; delivery staff implement approved boundaries. Dependencies include available expertise, timely access to evidence and agreement on handling dissent. Proposed acceptance criteria: all designated reviewers are consulted before launch, unresolved objections have written disposition, and a pause exercise reaches the operational owner within the locally agreed response target. Train staff on these responsibilities. Risks include nominal consultation, conflicting public statements and treating an approval record as proof of effectiveness."},"retrievedAt":"2026-09-09T03:01:41Z","enrichedAt":"2026-09-09T03:01:41Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: include frontline and affected-user perspectives alongside formal advisory bodies.","procurementImplications":"Interpretation: approval procedures should identify required consultation before contract or pilot commitments.","operatingModelImplications":"Interpretation: define who may advise, authorize, pause, investigate and communicate decisions.","updateExplanation":"No Doctronic or matching letter record in the full archive. Historical letter newly added alongside the agency response to preserve substantive contradictory oversight evidence.","sourceVerification":{"openedUrl":"https://commerce.utah.gov/wp-content/uploads/2026/04/doctronic-letter-from-medical-board.pdf","referenceExcerpt":"immediately suspended pending further discussion.","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}