Healthcare delegation
Delegation for the highest-stakes government decisions, the kind that can't be undone once acted on, borrowed from healthcare proxies and advance directives. Services making irreversible decisions get a delegation model medicine has already tested at those stakes.
The impact of agents
As users delegate to agents for consequential government decisions, an agency must let a user grant high-stakes, irreversible authority while keeping hard limits on what the delegate can do and a fallback when it should not act.
The difficulty is enforcing those limits and fallbacks reliably at the most extreme end of the delegation risk spectrum. Healthcare proxies and advance directives, built for exactly that end, are the closest precedent.
What must be verified
When a delegate can take irreversible, high-stakes actions, an agency needs confidence that the delegate cannot exceed the explicit limits the user set, including actions placed wholly out of reach. The clinical or institutional system reading the delegation credential must enforce those excluded actions at the point of action.
Protecting access
People who are ill, aging, or cognitively impaired are the most likely to need a delegate for high-stakes decisions. They are also the least able to complete a complex setup. A person who gives up mid-flow is left with no protection at all.
Keeping the path open
- Use simplified language throughout, and offer video recording as an alternative to written text.
- Let a trusted person assist in setting both the delegation and its excluded actions, and record the assist itself so help doesn't shade into substitution.
- Let a user set limits on a good day that hold on a bad one, since capacity fluctuates.
Response surface
Decisions the user placed off-limits are enforced wherever the delegation is read, so the delegate cannot take them at any point.
What must your agent never do?
These actions are blocked. No agent, main or backup, can take them.
Enforcement sits in the credential rather than in the agent’s restraint, so an agent that is compromised or simply wrong hits the same wall. Weakening an exclusion later takes a step-up identity check.
Maturity
- Emerging
For capping a delegate with explicit excluded actions and fallbacks, as electronic advance directives do.
- Frontier Headline
As applied to an agent authorized to take high-stakes, irreversible actions.
Precedents
Electronic advance directives and healthcare proxies (US). Several US states recognize electronic advance directives, and a healthcare proxy names a specific individual as agent with authority to make healthcare decisions; video directives supplement or replace paper documents in some jurisdictions. The instrument names a human delegate for a class of decisions, in advance of the moment the authority is used.
CRISP Health advance care plans (Maryland). The state Health Information Exchange has built infrastructure to consume advance care plan documents and display them inside existing electronic health record systems. A standing delegation is retrievable at the point of the decision, in the clinician's own workflow, rather than held as a document the patient must produce.
What carries over to agent use
Healthcare delegation patterns are relevant to agent delegation for high-stakes government decisions (benefits applications affecting housing, income, medical treatment access). Transferable elements: hierarchical delegation with fallbacks (primary agent, secondary agent, with explicit instructions for when delegation should be activated and when overridden); scope limitations (even within the delegation, certain decisions may be excluded, as in "the agent may not consent to..."); and integration with existing institutional workflows (the delegation credential must be consumable by the systems that need to act on it, not held only by the delegate).
Gap: healthcare proxies are activated by incapacity, a trigger condition. Agent delegation in government services is activated by choice ("I want my agent to handle this"), not by inability. The trigger model is different, but the safeguard model (scope limitations, excluded actions, override mechanisms) transfers directly.
Where things go wrong
The failure to prevent is an automated agent overstepping into irreversible decisions the user never authorized. Explicit excluded-action lists and hierarchical fallbacks cap what any delegate can do at exactly those points. A related failure sits with the trusted person who helps set the delegation up: assistance can shade into the helper choosing the excluded actions for the person, so the resulting delegation reads as freely given when it was substituted.
Sources
2 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.