EhrOS
The clinical nervous system.
Patient records, lab and pharmacy coordination, scheduling, billing, staff management.
- Patient Records
- Scheduling
- Billing
- Clinical Workflow
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.
EhrOS
ScholoraOS
WorkflowOS
Mobile apps
Live activity
Patient 0412 registered → sent to Laboratory
Illustrative screen with sample data.
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.
Every department lives inside the same institution boundary.
One login and one permission model for every user and role.
Approvals, tasks and handoffs routed the same way everywhere.
Every action recorded, timestamped and searchable.
EhrOS, ScholoraOS and WorkflowOS share the same kernel, so records, approvals and people stay connected — on the web and in your pocket.
The clinical nervous system.
Patient records, lab and pharmacy coordination, scheduling, billing, staff management.
The academic nervous system.
Student lifecycle, academic records, fees, staff, parent communication, timetabling.
The layer underneath both.
Workflow engine, approvals, forms, documents, scheduler, search, reporting — available standalone for any department.
Your institution in your pocket.
Parents, students, teachers, clinicians and admins get alerts, fees, timetables and messaging on Android and iOS.
Patient information follows the patient from registration to the ward, so nothing gets lost between desks.
Patient 0412 · Adult OPD
Waiting for doctor
Patient 0409 · Paediatrics
Triage done
Patient 0405 · Antenatal
Lab ordered
Patient 0398 · Pharmacy
Prescription ready
Illustrative screen with sample data.
From the first enrolment to the final report card, administrators, teachers and parents work from the same facts.
Form 5 Science
Term 2 fees · 38 of 42 paid
Lower Sixth Arts
Term 2 fees · 21 of 30 paid
Form 1A
Report cards ready for review
Timetable
Term 3 draft published
Illustrative screen with sample data.
Replace approvals over chat and paper with one engine for forms, sign-offs, documents and reports, for any department.
1 · Request submitted
Department head
2 · Budget check
Finance
3 · Approval
Administrator
4 · Audit record
Timestamped automatically
Illustrative screen with sample data.
The e-conneq mobile apps bring school and hospital tools to Android and iOS. Everyone connected, everywhere.
Track your child's progress, receive alerts, pay fees
Ask about the appsParents
Today
Illustrative screen, sample data
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.
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)
Confirms who someone is and what they’re allowed to touch, at every request.
@econneq/kernel-identity, @econneq/kernel-permissions (RbacEngine)
Routes work: approvals, task assignment, escalation, department handoffs.
@econneq/platform-workflow (WorkflowEngine)
Notifies the right person through the right channel — email, SMS, push, in-app.
@econneq/platform-notifications
Stores records, documents and history with a full audit trail.
@econneq/platform-documents, @econneq/kernel-auditing
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
Each role sees the tools it needs, with permissions enforced by the kernel.
Doctors, nurses, lab and pharmacy teams, cashiers, hospital management.
Administrators, teachers, bursars and registrars running admissions, fees and results.
Anyone who approves, routes or reports: requests, forms, documents and sign-offs.
Alerts, fee payments, timetables and messages on Android and iOS, wherever they are.
Practical foundations, not promises: what the platform does differently under the hood.
Hospital and school run on the same tenant, identity and workflow core.
Roles are configured per institution and checked on every request.
Approvals, transitions and record changes are timestamped and reviewable.
Go live module by module and department by department, not all at once.
The platform speaks both languages of your institution.
Talk to the team directly, the way your staff already communicate.
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
The same five steps, whether we're equipping one department or rolling out a whole hospital or school.
Map current workflows, systems and departmental boundaries.
Design the tenant, role and workflow model for your institution.
The product (EhrOS or ScholoraOS) is configured on the shared kernel, not rebuilt from scratch.
Staff onboarded module by module, department by department.
New workflows and modules are added on the same kernel over time.
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.
Tell us how you work today and we will show you the product that fits, with a live demo.