Physician Assistants

The work of Physician Assistants engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.

+29 more via engagesIn

Physician Assistants involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.

+29 more via involvesActivity

Physician Assistants performs 28 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.

+16 more via performs

Physician Assistants is typically employed by 60 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.

+48 more via typicallyEmploys

Physician Assistants is employed across 38 settings — the places where this role's work is done, and where digital employees first sit beside the humans.

+26 more via employs

Physician Assistants uses 132 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.

+120 more via usesTool

Physician Assistants relies on 48 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.

+36 more via uses

The software Physician Assistants 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.