How family medicine physicians are reshaped as AGI capability advances.

About 55% of the work in Family Medicine Physicians 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 signals strongly indicate a true hybrid role. While tools are overwhelmingly IT/Software (26 tools in segment 43, including EMR and scheduling software) and activities like 'Documenting/Recording Information' (4.96) and 'Working with Computers' (4.55) are critical, the role mandates hands-on physical presence. This is evidenced by the top activity 'Assisting and Caring for Others' (4.99) and context attributes like 'Physical Proximity' (4.97) and 'Exposed to Disease or Infections' (4.78).
grounded in the economy graph · digital scalar 0.55 · hybrid
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Family Medicine Physicians engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Family Medicine Physicians 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.
Family Medicine Physicians 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.
Family Medicine Physicians is typically employed by 43 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+31 more via typicallyEmploys
Family Medicine Physicians is employed across 37 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+25 more via employs
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Family Medicine Physicians uses 74 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.
+62 more via usesTool
Family Medicine Physicians relies on 30 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.
+18 more via uses
The software Family Medicine Physicians 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.