We Engineer the Nervous Systems of Institutions
e-conneq OS is the shared platform kernel — tenancy, identity, workflow, and permissions — running underneath EhrOS for hospitals and ScholoraOS for schools. One kernel. Every department wired in.
Platform Kernel·Multi-Tenant Architecture·Role-Based Access Control·Workflow Orchestration·Real-Time Audit Trail
Institutions don’t fail because they lack software. They fail because their departments can’t talk to each other.
Most hospitals and schools run five to twenty disconnected tools — one for records, one for billing, one for messaging, one for scheduling — each with its own login, its own data, its own blind spots. e-conneq OS replaces that fragmentation with a single kernel that every department, and every product built on it, shares: one tenant model, one identity system, one workflow engine, one audit trail.
The kernel, in six layers
Every product built on e-conneq OS shares the same six layers. Nothing below is illustrative — each layer names a real package in the platform.
Sensory
Every action a person takes — a patient arriving, a fee paid, a form submitted — enters the system as a structured event.
@econneq/kernel-events (EventBus)
Identity & Access
Confirms who someone is and what they’re allowed to touch, at every request.
@econneq/kernel-identity, @econneq/kernel-permissions (RbacEngine)
Processing
Routes work: approvals, task assignment, escalation, department handoffs.
@econneq/platform-workflow (WorkflowEngine)
Communication
Notifies the right person through the right channel — email, SMS, push, in-app.
@econneq/platform-notifications
Memory
Stores records, documents and history with a full audit trail.
@econneq/platform-documents, @econneq/kernel-auditing
Intelligence
Turns operational data into dashboards, reports and forecasts.
@econneq/platform-reporting, @econneq/platform-search
- Sensory: Every action a person takes — a patient arriving, a fee paid, a form submitted — enters the system as a structured event. (@econneq/kernel-events (EventBus))
- Identity & Access: Confirms who someone is and what they’re allowed to touch, at every request. (@econneq/kernel-identity, @econneq/kernel-permissions (RbacEngine))
- Processing: Routes work: approvals, task assignment, escalation, department handoffs. (@econneq/platform-workflow (WorkflowEngine))
- Communication: Notifies the right person through the right channel — email, SMS, push, in-app. (@econneq/platform-notifications)
- Memory: Stores records, documents and history with a full audit trail. (@econneq/platform-documents, @econneq/kernel-auditing)
- Intelligence: Turns operational data into dashboards, reports and forecasts. (@econneq/platform-reporting, @econneq/platform-search)
Two live products. One platform underneath.
EhrOS
The clinical nervous system.
Patient records, lab and pharmacy coordination, scheduling, billing, staff management.
ScholoraOS
The academic nervous system.
Student lifecycle, academic records, fees, staff, parent communication, timetabling.
WorkflowOS
The layer underneath both.
Workflow engine, approvals, forms, documents, scheduler, search, reporting — available standalone for any department.
What changes when you run on the kernel
Every department keeps its own spreadsheets and logins
One tenant, one identity, one permission model across departments
Approvals happen over WhatsApp and paper trails
Every approval routes through the workflow engine with a timestamped audit trail
Leadership finds out about a bottleneck a week late
Reporting and search surface it in real time
Adding a new process means another vendor contract
New workflows are configured on the existing kernel
How e-conneq works with your institution
Assessment
Map current workflows, systems and departmental boundaries.
Architecture
Design the tenant, role and workflow model for your institution.
Configuration
The product (EhrOS or ScholoraOS) is configured on the shared kernel, not rebuilt from scratch.
Rollout & Training
Staff onboarded module by module, department by department.
Operate & Extend
New workflows and modules are added on the same kernel over time.