!Hospital onboarding

Hospital onboarding

The current onboarding architecture is deliberately gated.

Contract
  ↓
Organization
  ↓
Users / roles
  ↓
Integration request
  ↓
Sandbox
  ↓
Validation
  ↓
Customer UAT
  ↓
Production authorization
  ↓
Production activation
  ↓
Monitoring

Hospital access request

The repository contains a platform-admin review flow:

SUBMITTED → IN_REVIEW → APPROVED/REJECTED → PROVISIONED

Provisioning creates an INTERNAL_PILOT organization and an initial Organization Admin invitation.

Customer actions

The hospital/customer must provide business and technical authorization required for its chosen integrations and UAT.

Vendor actions

The EHR/payer vendor may need to register DenialOS, approve scopes, provision a tenant/client, and enable sandbox or production access.

DenialOS actions

DenialOS configures the connection contract, validates the runtime, performs source/canonical reconciliation tests, and records activation evidence.

No customer is marked production-active merely because a workspace exists.