Define service requirements
How define service requirements are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Define service requirements 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: Because no child occupations are seeded in the grounding block, this scalar is derived from the process name ('Define service requirements') and its healthcare industry lens. Defining and planning service requirements is inherently an analytical, information-gathering, and documentation task. As pure knowledge work rather than physical execution, it maps squarely to the digital band, landing at a band-center value of 0.85.
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Define service requirements 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 Define service requirements inherits.
Where Define service requirements 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 strategic planning cycle or community health needs assessment identifies a gap in existing clinical services.
- Analyze community health data and patient demographics
- Assess current clinical capabilities and facility capacity
- Identify regulatory and accreditation standards
- Draft clinical and operational service requirements
- Review requirements with medical and administrative leadership
- Finalize and approve the service requirements portfolio
Outcome: A comprehensive set of clinical, operational, and regulatory requirements for a new or updated healthcare service is documented and approved.