How psychiatric aides are reshaped as AGI capability advances.

About 45% of the work in Psychiatric Aides is information-shaped and increasingly AI-deliverable, with the rest a hybrid of judgment and hands-on work. The automation frontier runs straight through the middle of this role.
Why: Tools are almost evenly split between IT/software like patient management systems (segment 43, 12 tools) and physical medical equipment like restraints and suctioning kits (segment 42, 11 tools). Work activities similarly blend 'Documenting/Recording Information' (4.41) with hands-on 'Assisting and Caring for Others' (4.65). The work context enforces a physical requirement through 'Physical Proximity' (4.55) and 'Exposed to Disease or Infections' (4.17), placing this role squarely in the hybrid band of physical patient care and digital charting.
grounded in the economy graph · digital scalar 0.45 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Psychiatric Aides engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Psychiatric Aides involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Psychiatric Aides performs 17 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+5 more via performs
Psychiatric Aides is typically employed by 70 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+58 more via typicallyEmploys
Psychiatric Aides is employed across 27 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+15 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Psychiatric Aides uses 18 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
+6 more via usesTool
Psychiatric Aides relies on 15 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+3 more via uses
The software Psychiatric Aides reaches for already exposes 12 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
+9 more problems on the graph
No articles yet for this entity.
No capability events for this entity yet.