Identify potential referrals
How identify potential referrals are reshaped as AGI capability advances.
The bottom line
Roughly 75% of the work in Identify potential referrals is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: With no child occupations seeded, I evaluated the APQC process name 'Identify potential referrals' within the healthcare provider framework lens. Identifying referrals is fundamentally an information-processing and clinical-documentation task—evaluating patient data against care criteria and initiating orders in an EHR system—placing it in the digital band.
grounded in the economy graph · digital scalar 0.75 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Identify potential referrals sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Identify potential referrals inherits.
Where Identify potential referrals sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A patient assessment reveals a medical condition or social need requiring specialized care or services outside the current provider's scope.
- Evaluate patient symptoms, diagnosis, and treatment plan
- Identify gaps in current care capabilities
- Match clinical needs to required specialty or service types
- Verify initial patient preferences and insurance constraints
- Document the referral necessity in the electronic health record
Outcome: A required referral is documented in the patient's medical record and staged for provider matching and authorization.