⚡ e-conneq OS · Platform Kernel

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.

  • 🏥 Hospitals
  • 🎓 Schools
  • iOS & Android
  • English · Français
e-conneq OS · Command centre
Clinical

EhrOS

Academic

ScholoraOS

Approvals

WorkflowOS

Alerts

Mobile apps

Live activity

Patient 0412 registered → sent to Laboratory

Illustrative screen with sample data.

🧩 The problem

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

Every department lives inside the same institution boundary.

One identity system

One login and one permission model for every user and role.

One workflow engine

Approvals, tasks and handoffs routed the same way everywhere.

One audit trail

Every action recorded, timestamped and searchable.

🧱 Built on one kernel

One platform. A product for every department.

EhrOS, ScholoraOS and WorkflowOS share the same kernel, so records, approvals and people stay connected — on the web and in your pocket.

Live

EhrOS

The clinical nervous system.

Patient records, lab and pharmacy coordination, scheduling, billing, staff management.

  • Patient Records
  • Scheduling
  • Billing
  • Clinical Workflow
Live

ScholoraOS

The academic nervous system.

Student lifecycle, academic records, fees, staff, parent communication, timetabling.

  • Student Records
  • Fees
  • Timetabling
  • Communication
Standalone

WorkflowOS

The layer underneath both.

Workflow engine, approvals, forms, documents, scheduler, search, reporting — available standalone for any department.

  • Workflow Engine
  • Approvals
  • Forms
  • Reporting
iOS & Android

Mobile apps

Your institution in your pocket.

Parents, students, teachers, clinicians and admins get alerts, fees, timetables and messaging on Android and iOS.

  • Real-time alerts
  • Fees
  • Timetables
  • Messaging
🏥 EhrOS · Clinical

Every department of the hospital, on one record

Patient information follows the patient from registration to the ward, so nothing gets lost between desks.

  • Patient records and scheduling
  • Laboratory and pharmacy coordination
  • Billing and staff management
  • Clinical workflows with a full audit trail
EhrOS · Outpatient queue

Patient 0412 · Adult OPD

Waiting for doctor

Queue

Patient 0409 · Paediatrics

Triage done

In consult

Patient 0405 · Antenatal

Lab ordered

Laboratory

Patient 0398 · Pharmacy

Prescription ready

Dispensing

Illustrative screen with sample data.

🎓 ScholoraOS · Academic

Admissions, fees and results in one school system

From the first enrolment to the final report card, administrators, teachers and parents work from the same facts.

  • Student lifecycle and academic records
  • Fee billing, payments and balances
  • Timetabling and staff records
  • Parent communication built in
ScholoraOS · Fees overview

Form 5 Science

Term 2 fees · 38 of 42 paid

90%

Lower Sixth Arts

Term 2 fees · 21 of 30 paid

70%

Form 1A

Report cards ready for review

Results

Timetable

Term 3 draft published

New

Illustrative screen with sample data.

⚙️ WorkflowOS · Workflows

Approvals that route themselves

Replace approvals over chat and paper with one engine for forms, sign-offs, documents and reports, for any department.

  • Workflow engine and approvals
  • Forms, documents and scheduler
  • Search and reporting
  • Available standalone, or underneath EhrOS and ScholoraOS
WorkflowOS · Purchase request

1 · Request submitted

Department head

Done

2 · Budget check

Finance

Done

3 · Approval

Administrator

Pending

4 · Audit record

Timestamped automatically

Auto

Illustrative screen with sample data.

📱 Mobile apps

Your institution in your pocket

The e-conneq mobile apps bring school and hospital tools to Android and iOS. Everyone connected, everywhere.

  • Real-time attendance & grade alerts
  • Assignments and timetables
  • Pay fees and view payment history
  • Message teachers and school admin

Track your child's progress, receive alerts, pay fees

Ask about the apps

Parents

Today

  • Attendance recorded ✅
  • Term 2 fees: balance due
  • New message from teacher

Illustrative screen, sample data

🧠 The kernel

The kernel, in six layers

Every product built on e-conneq OS shares the same six layers. Nothing here is illustrative — each layer names a real package in the platform.

01

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)

02

Identity & Access

Confirms who someone is and what they’re allowed to touch, at every request.

@econneq/kernel-identity, @econneq/kernel-permissions (RbacEngine)

03

Processing

Routes work: approvals, task assignment, escalation, department handoffs.

@econneq/platform-workflow (WorkflowEngine)

04

Communication

Notifies the right person through the right channel — email, SMS, push, in-app.

@econneq/platform-notifications

05

Memory

Stores records, documents and history with a full audit trail.

@econneq/platform-documents, @econneq/kernel-auditing

06

Intelligence

Turns operational data into dashboards, reports and forecasts.

@econneq/platform-reporting, @econneq/platform-search

  1. 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))
  2. Identity & Access: Confirms who someone is and what they’re allowed to touch, at every request. (@econneq/kernel-identity, @econneq/kernel-permissions (RbacEngine))
  3. Processing: Routes work: approvals, task assignment, escalation, department handoffs. (@econneq/platform-workflow (WorkflowEngine))
  4. Communication: Notifies the right person through the right channel — email, SMS, push, in-app. (@econneq/platform-notifications)
  5. Memory: Stores records, documents and history with a full audit trail. (@econneq/platform-documents, @econneq/kernel-auditing)
  6. Intelligence: Turns operational data into dashboards, reports and forecasts. (@econneq/platform-reporting, @econneq/platform-search)

0

Products on one kernel

EhrOS · ScholoraOS · WorkflowOS

0

Kernel layers

Events to intelligence

0

Languages

English and Français

0

Shared audit trail

Across every department

👥 Who it's for

Built for the people who run your institution

Each role sees the tools it needs, with permissions enforced by the kernel.

Hospitals & clinics

Doctors, nurses, lab and pharmacy teams, cashiers, hospital management.

Schools & colleges

Administrators, teachers, bursars and registrars running admissions, fees and results.

Operations & finance teams

Anyone who approves, routes or reports: requests, forms, documents and sign-offs.

Parents, students & staff

Alerts, fee payments, timetables and messages on Android and iOS, wherever they are.

⭐ Why e-conneq

Why institutions choose e-conneq

Practical foundations, not promises: what the platform does differently under the hood.

One kernel, many products

Hospital and school run on the same tenant, identity and workflow core.

Access you can trust

Roles are configured per institution and checked on every request.

Reviewable audit trail

Approvals, transitions and record changes are timestamped and reviewable.

Phased rollout

Go live module by module and department by department, not all at once.

English and Français

The platform speaks both languages of your institution.

Reach us on WhatsApp

Talk to the team directly, the way your staff already communicate.

🔄 Before / After

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

🛠️ Delivery

How e-conneq works with your institution

The same five steps, whether we're equipping one department or rolling out a whole hospital or school.

STEP 01

Assessment

Map current workflows, systems and departmental boundaries.

STEP 02

Architecture

Design the tenant, role and workflow model for your institution.

STEP 03

Configuration

The product (EhrOS or ScholoraOS) is configured on the shared kernel, not rebuilt from scratch.

STEP 04

Rollout & Training

Staff onboarded module by module, department by department.

STEP 05

Operate & Extend

New workflows and modules are added on the same kernel over time.

❓ FAQ

Common questions

Every institution is a tenant in @econneq/kernel-tenancy. Tenancy is enforced at the data-access layer, not just in the UI, so one tenant’s records are never queryable from another tenant’s context.

💬 Let’s talk

See your institution as one system.

Tell us how you work today and we will show you the product that fits, with a live demo.