The Magenta Canon accountability gateway applies to healthcare and clinical decision support systems by enforcing authority binding for clinical AI recommendations, patient safety gates for high-risk decisions, disclosure requirements for AI-assisted care, irreversible medical action definitions, and incident breach reporting timelines. It does not govern clinical diagnosis, treatment selection, or medical judgment.
- Patient safety gates: high-risk clinical AI actions blocked pending human approval
- Disclosure requirements: AI classification enforcement for patient care contexts
- Incident reporting: gateway evidence trail for safety and compliance review
JURISDICTION
Healthcare & Medical
The accountability gateway applied to clinical decision support. Patient safety gates, disclosure requirements, and incident reporting.
How to Read This Proof Room
Four states, kept apart.
- Runnable / proven control pattern — executes today against the gate: delegated actions are allowed, withheld actions are blocked before downstream, both are recorded, and the evidence verifies independently.
- Reference / mock integration — the downstream tool in these examples is an audited mock, not a live provider. It proves the control pattern and the downstream absence of a blocked call, and nothing about a real provider's behavior.
- Future provider integration — connecting a real provider is design-partner work that has not been built. No live provider connection exists, and none is implied by a workflow appearing on this page.
- Not claimed — no compliance certification, no professional advice, no real-world side effects, and no assertion that a customer's own policies are correct.
Enforcement is scoped to the MCP tools/call method class; other MCP methods pass through the gateway ungated. The refund ceiling is the one numeric threshold the gate enforces today — other boundaries are expressed as tool-scoped allowlists under default-deny.
What Magenta Governs
Against audited mock tools, the gate enforces delegated versus withheld authority for clinical AI workflows: scribe, prior authorization, and order or prescription boundaries. Read and draft actions can proceed; patient-impacting actions stay withheld.
- Authority binding — a clinical AI action executes only under an explicit operator-delegated grant (runnable)
- Withheld patient-impacting actions — order, prescription, and similar steps are refused before downstream (runnable, against mock tools)
- Downstream absence — the mock tool's own log shows the blocked call never arrived (runnable)
- Evidence — signed, hash-chained receipts for allow and block alike, independently verifiable (runnable)
- Live EHR or clinical-system integration — future design-partner work, not built
- No HIPAA, HITRUST, or other certification is claimed, and no incident or breach reporting obligation is discharged by this system
What Magenta Does Not Govern
Magenta Canon is an accountability gateway for AI-agent tool calls, not a medical services provider. The following fall outside the scope of the gateway.
- Clinical diagnosis
- Treatment selection
- Medical judgment
- Patient outcomes
Related Governance Jurisdictions
The Magenta Canon accountability gateway also applies to law firms, financial systems, and autonomous agents — see the full jurisdictions overview.
Clarification: This refers to enforcing governance rules in healthcare contexts, not providing licensed medical advice. Domain references describe governance rule contexts, not licensed legal, financial, or medical services.