Trust & Security · Architecture Specification
A precise explanation of Operative Signal's zero-cloud-ingestion architecture, cryptographic boundaries, authorization models, and hospital compliance safeguards.
Visual Topology
NAS · PACS · Workstations · Towers
High-resolution recordings, patient records, and local file paths remain on your existing storage drives.
Software running on your server
Indexes procedure type, duration, optics vendor, and local rights. Assigns a pseudonymous OS Video ID.
Governed Network Coordination
Evaluates cohort availability in the aggregate. No external party can browse or access your files without approval.
Connect folders once. OS Node keeps catalog records synchronized automatically.
Works seamlessly with your current NAS, PACS, local drives, and endoscopy recording towers.
Your hospital decides who may query, analyze, or validate models against your data.
The cloud control plane stores user accounts, organization memberships, permissions, project metadata, pseudonymous OS Video IDs, and append-only audit events. Original raw surgical video files remain physically on hospital NAS, PACS, or server storage and are never uploaded to Operative Signal managed cloud buckets.
OS Node operates as an on-premises daemon establishing outbound mutual TLS connections to the control plane. No inbound firewall ports are opened, and no external entities can initiate unsolicited connections into the hospital intranet.
Assets are indexed using SHA-256 content-addressed fingerprints and pseudonymous OS Video IDs. Internal institutional directory paths, patient identifiers, and server IP addresses are stripped locally and never transmitted across the wire.
All access tokens, permission grants, and Project Space memberships are validated by server-side authorization routines. Client-provided identifiers are never trusted autonomously.
Every policy modification, access authorization, and validation evaluation is recorded in an immutable ledger, providing health system compliance officers with full historical provenance.
Arbitrary third-party executable containers and patient-derived cloud uploads remain disabled in production by default. Governance checklists do not override institutional ethical review requirements.
Our engineering team provides comprehensive architectural packets, threat models, and pilot deployment guides for hospital security officers.
