# INFRASI HealthOps Platform — Comprehensive LLM Specification (llms-full.txt)
> Machine-Readable Architectural Guide, Data Dictionaries, API Contracts, and Remediation Workflows for LLMs & AI Autonomous Agents.

## 1. Executive Overview
INFRASI HealthOps is an enterprise multi-tenant hospital operations system designed for clinical engineering, facility operations, and healthcare IT. It coordinates clinical IoT device telemetry, emergency electrical power management, high-availability cellular connectivity, and automated CMMS work order workflows under strict domain-restricted identity enforcement.

## 2. Platform Architecture
```
+-----------------------------------------------------------------------------------+
|                           INFRASI HealthOps Architecture                         |
+-----------------------------------------------------------------------------------+
|  Identity Gateway        : Domain-restricted Google SSO (@infrasi.com)           |
|  Presentation Layer      : React 18 + Vite + Tailwind CSS + Lucide Icons         |
|  Server Application      : Node.js Express API + Gemini AI Diagnostic Engine     |
|  Clinical IoT Ingestion  : SNMPv3, MQTT over TLS 1.3, CoAP Telemetry             |
|  Facilities Subsystem    : Switched PDU / Smart UPS monitoring & cycling          |
|  WAN / Connectivity      : Dual-SIM 5G Cellular Failover (NetCloud OS)           |
|  Work Order Engine       : Maintastic CMMS automated ticket dispatch             |
|  AI Diagnostic Layer     : Google Gemini API (gemini-2.5-flash / server-side)    |
+-----------------------------------------------------------------------------------+
```

## 3. Hospital Tenant Environments
INFRASI HealthOps operates in strict multi-tenant isolation. All assets, telemetry, power circuits, and work orders are scoped to a specific `tenantId`:
1. `st_jude`: St. Jude ChildrenResearch Hospital (Memphis, TN) — 1,248 clinical devices, 4 campuses, pediatric oncology focus.
2. `mayo_clinic`: Mayo Clinic Rochester (Rochester, MN) — 3,420 clinical devices, 8 campuses, high-density surgical suites.
3. `johns_hopkins`: Johns Hopkins Hospital (Baltimore, MD) — 2,890 clinical devices, 6 campuses, critical care trauma units.

## 4. Role-Based Access Control (RBAC)
Every authenticated identity must belong to `@infrasi.com`. Access is segmented into 5 defined operational tiers:
- **`super_admin` (Enterprise Super Admin)**: Unrestricted access across all tenants, PDU switched outlet controls, network cellular failover triggers, AI diagnostics, and work order approval.
- **`biomed_lead` (Lead Biomedical Technician)**: Clinical IoT fleet lifecycle, calibration overrides, maintenance dispatch, and CMMS work order resolution.
- **`power_specialist` (Critical Facilities & Power Specialist)**: Smart UPS battery monitoring, runtime estimations, and remote switched PDU power-cycling.
- **`netops_admin` (Network & 5G Cellular Admin)**: Cradlepoint router telemetry, dual-SIM failover testing, speed tests, and WAN latency auditing.
- **`clinical_auditor` (Clinical Compliance & Audit Officer)**: Read-only access to HIPAA audit trails, FDA 21 CFR Part 11 records, and incident timeline history.

## 5. Machine-Readable API Reference
All endpoints return JSON (`Content-Type: application/json`).

### Session & Identity
- `GET /api/auth/session`: Returns `{ authenticated: boolean, user: InfrasiUser | null, requiredDomain: "infrasi.com" }`
- `POST /api/auth/switch-role`: `{ role: "super_admin" | "biomed_lead" | "power_specialist" | "netops_admin" | "clinical_auditor" }`
- `POST /api/auth/logout`: Clears session cookie and returns `{ success: true }`

### Telemetry & Devices
- `GET /api/devices`: Returns array of `IoTDevice` objects.
- `GET /api/tenants`: Returns list of hospitals and campus details.

### Operational Controls
- `POST /api/actions/pdu-outlet`:
  - Request: `{ upsId: string, outletId: string, action: "cycle" | "on" | "off" }`
  - Guard: Requires `canControlPDU` permission.
  - Response: `{ success: true, message: string, outlet: OutletState }`
- `POST /api/actions/router-command`:
  - Request: `{ routerId: string, command: "ping" | "speedtest" | "failover_test" }`
  - Guard: `failover_test` requires `canTriggerNetworkFailover` permission.
  - Response: `{ success: true, output: string, operator: string }`

### AI Copilot & Diagnostics
- `POST /api/ai/diagnose`:
  - Request: `{ incident: IncidentPayload, tenant: TenantPayload, devices: IoTDevice[], upsList: CyberPowerUPS[], routers: CradlepointRouter[] }`
  - Model: Server-side Gemini 2.5 Flash via `@google/genai`
  - Response: `{ success: true, analysis: { rootCause: string, severity: string, immediateActions: string[], preventiveRecommendations: string[], confidenceScore: number } }`

## 6. Standard Operating Procedures (SOP) for AI Operators
When an autonomous agent identifies an active incident:
1. **Correlate Signals**: Compare clinical device power telemetry against PDU outlet status and Cradlepoint WAN packet loss.
2. **Determine Criticality**: If telemetry affects life-support devices (e.g., ventilators, infusion pumps), prioritize PDU circuit health and hospital backup generator synchronization.
3. **Generate Work Order**: Dispatch via Maintastic CMMS with SLA deadline set to under 60 minutes for high-priority clinical assets.
4. **Log Immutable Audit Record**: Record operator email (`*@infrasi.com`), timestamp (UTC), and action hash in compliance with FDA 21 CFR Part 11.