# Administrator Role, Setting & Situation Recipes

These recipes choose views and questions; they do not confer authority or activate a power.

## Health system or enterprise administration

Select enterprise operating level; verify board/executive delegation, legal entities and central-versus-local decision rights. Start with Powers 1–4, 9, 16–18 and 22. Use portfolio, source, risk and human decision queues. Keep entity partitions separate; a system-wide title does not erase local governance.

## Hospital, facility or service-line administration

Verify facility, service, medical-staff/clinical, nursing, operations, finance and quality owners. Start with Powers 5–9, 12, 16, 19–21. Use approved aggregate data only. No bed, discharge, staffing, clinical or emergency command occurs through STEWARD.

## Clinic, ambulatory, practice or multi-site administration

Verify ownership model, sites, payer/contract routes, clinical leadership, scheduling and revenue-cycle owners. Start with Powers 5–8, 10–14, 16–18 and 20. Patient scheduling, referrals, claims, coverage and contracting stay in official human workflows.

## Independent or small-practice administrator

Use Minimum Mode: one North Star, one access/flow question, one resource scenario, one compliance-source queue and one protected-life commitment. Never treat limited staffing as permission to merge personal, clinical, payroll, claim, bank, credential or contract data into the private OS.

## Academic, public, nonprofit or community setting

Record the exact governance, public-record, grant, civil-rights, research, teaching, labor and community-engagement owners. Use Power 18 early. Do not infer that one ownership or tax status changes applicable requirements.

## Critical access, rural and limited-redundancy setting

Record the exact provider/facility type, transfer and transport dependencies, after-hours coverage, utility/telecom constraints, supply lead times and mutual-aid owners. Verify current federal, state and local sources for the exact organization. Use Powers 5–8, 11–12 and 19–21. A rural label never proves a reimbursement, licensing or regulatory category.

## FQHC, Health Center Program, Rural Health Clinic or safety-net setting

Keep each designation separate. Verify scope of project, governing-board responsibilities, service area/population, sliding-fee or assistance requirements, contracts, reporting and current HRSA/CMS sources with authorized humans. Do not infer that FQHC, look-alike, RHC, free clinic or other safety-net status are equivalent.

## Tribal, IHS or sovereign setting

Begin with sovereignty, tribal governance, compact/contract, data governance and authorized community leadership. Determine applicable tribal, federal and state sources only through qualified humans. Never treat community engagement, data use or external partnership as authorized because another health system uses it.

## Ownership and capital-structure gate

Public/government, nonprofit/tax-exempt, for-profit/private, publicly traded, joint-venture and management-agreement settings carry different governance, records, procurement, disclosure, conflict and community obligations. Record the exact entity and owner. AI never determines public-record exemptions, tax compliance, fiduciary duties, securities disclosure, antitrust, corporate-practice rules or reserved powers.

## Dual clinical and administrative hats

Choose one active hat for each workflow and show it at the top of every artifact. A clinical credential does not grant budget, employment or contracting authority; an administrative title does not grant clinical authority. If a workflow crosses hats, split it into separately owned artifacts and connect them only through a named human handoff.

## Transition, turnaround, merger, closure or crisis planning

Begin with CHART and official governance; use synthetic/private planning or a separately authorized partition. Surface rights, continuity, community, workforce, quality, finance and exit impacts. AI never announces, executes or commits the change.

## Agent sequence recipe

Register one AI use case with Power 22; compare a non-AI alternative; charter one agent with Power 23; test in a synthetic sandbox; have an independent human review; permit at most one bounded run; return to Disabled; inspect receipt; then retain, revise, kill or retire with Power 24. Never activate a multi-agent chain as the first run.
