| 1. Domain Scope & Core Workflows |
| Primary Use CaseTarget deployment environment and primary operators | Hospitals, clinics, and health networks OPD triage, IPD bed allocation, e-prescriptions, and lab routing | Enterprises and multi-state employers Statutory payroll runs, biometric attendance, employee tax declarations | Enterprise SaaS platform infrastructure Unified auth, schema routing, background queues, and telemetry |
| AI Assistance ModelHow generative AI models are integrated | Clinical Scribe Drafts structured SOAP notes from ambient audio; clinician review mandatory | Statutory Policy Assistant Guides payroll admins on changing state tax slab deductions | Zero Unsupervised Actions AI outputs are always drafts; permanent DB commits require user authorization |
| Operator VerificationHuman-in-the-loop validation boundary | Mandatory doctor electronic signature Prescriptions and notes locked only after licensed clinician approval | Two-party payroll verification Maker-checker approval flow before salary disbursements and bank file export | Cryptographic signature & audit log Every administrative change logged with actor ID, timestamp, and IP |
| 2. Tenancy, Data Sovereignty & Security |
| Tenant Data IsolationArchitectural database partition model | Dedicated PostgreSQL Schema Patient records isolated per hospital tenant; zero shared tables | Dedicated PostgreSQL Schema Employee compensation and bank details strictly isolated per organization | Zero cross-tenant querying Connection pooling enforces tenant ID in session context automatically |
| Encryption StandardCryptographic safeguards in transit & rest | AES-256-GCM + TLS 1.3 Per-tenant cryptographic key isolation with hardware KMS integration | AES-256-GCM + TLS 1.3 Statutory filings and salary registers encrypted at column and volume level | Enterprise Key Management Enforced TLS 1.3 ciphers with automated certificate rotation |
| Data ResidencyGeographical hosting location | Republic of India (Mumbai / Hyderabad) Protected health data never leaves Indian borders | Republic of India (Mumbai / Delhi) Indian payroll and tax records retained strictly in-country | Sovereign Cloud Deployment Optional on-premise Kubernetes or customer-owned private VPC |
| 3. Regulatory Standards & Statutory Compliance |
| Core Regulatory ReadinessStatutory frameworks supported | ABDM M1–M3 Sandbox ABHA creation, health record linking, and HIU/HIP consent manager flows | Multi-State Statutory Engine EPF, ESI, Professional Tax (all states), TDS Section 192, and Form 16 | DPDP Act 2023 Readiness Built-in consent capture, data principal access, and erasure pipelines |
| Interoperability StandardStandardized clinical & payroll schemas | HL7 FHIR R4 Profiles Encounter, Observation, Condition, and DiagnosticReport schema export | Direct Bank Clearing Formats Standardized NEFT, RTGS, and IMPS batch clearing files for Indian banks | OpenAPI 3.1 & Webhooks Idempotent RESTful endpoints with HMAC SHA-256 payload signing |
| 4. Release Stage & Deployment Status |
| Current Release StageCurrent engineering and deployment status | Staging / Pilot Cohort Active sandbox validation with healthcare design partners | Staging / Pilot Cohort Active staging testing with multi-state employer design partners | Production Runtime Core infrastructure deployed and monitored with 24/7 health probes |
| Next ActionRecommended evaluation step | Explore CybeHealth specs → | Explore CybeHRMS specs → | Review architecture layers → |