How emergency medical technicians are reshaped as AGI capability advances.

About 60% of the work in Emergency Medical Technicians 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: The grounding hints indicate a hybrid profile driven by a mix of physical and software tools. Of the 30 tools listed, 21 fall into segment 43 (IT/software, digital prior 0.85), including applications like PEPID EMS and Medical Wizards ER Suite. The remaining 9 tools belong to segments 42 and 24 (medical and material handling equipment, digital prior 0.00), anchoring the physical aspect of the work and resulting in a mid-range hybrid scalar.
grounded in the economy graph · digital scalar 0.60 · hybrid
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Emergency Medical Technicians performs 12 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
Emergency Medical Technicians is typically employed by 28 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+16 more via typicallyEmploys
Emergency Medical Technicians is employed across 72 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+60 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Emergency Medical Technicians uses 98 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.
+86 more via usesTool
Emergency Medical Technicians relies on 25 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.
+13 more via uses
The software Emergency Medical Technicians reaches for already exposes 8 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.
No articles yet for this entity.
No capability events for this entity yet.