Account and workspace setup

The product separates organization and client scope. Protected procedures resolve the caller's security context before domain actions are executed.

Production hospital onboarding

Production hospital workspaces are not created through the normal development bootstrap path. The repository contains a governed hospital-access-request flow:

request
  → review
  → approve
  → provision Internal Pilot
  → invite first admin

Provisioning does not automatically authorize EHR, payer, patient communication, payment, telephony, coding, or managed-service activity.

Roles and permissions

Authorization is enforced through organization access checks, scoped client context, and action-level permission gates. High-impact actions may require additional human approval or an approved-action request.

First workflow

The documented product path is:

1. create or receive an approved workspace;
1. establish user access;
1. configure the relevant integrations or intake channels;
1. create/import a denial case;
1. review extracted facts and evidence;
1. prepare a human-reviewed action;
1. record the outcome.