Tenelix
Patient management

One patient record. Across every visit, every site.

Demographics, history, vitals, prescriptions, lab results, files — every artifact for a patient lives on one record. Custom fields per specialty, contacts and relationships modeled as first-class objects, and a binder export that travels with them.

PAT-2026-0014 · Kemi Adesanya
KA
Kemi Adesanya
27y · Female · O+ · Allergy: penicillin
ActiveInsurance: NHIS
Visits
14
Active Rx
2
Open invoices
1
Timeline
  • Visit · GP consultation
    Apr 18, 2026
  • Lab order · CBC, LFT
    Apr 18, 2026
  • Rx · Amoxicillin 500mg
    Mar 02, 2026
Capabilities

What you actually get.

Custom fields per specialty

JSON-driven forms let you add cardiology, OB/GYN, or paediatric fields without forking the schema.

Medical history timeline

Visits, prescriptions, lab orders, vitals, attachments — chronological, filterable, queryable.

Contacts & relationships

Emergency contacts, parent/guardian, caregivers — modeled, not stuffed into a notes field.

File attachments & photos

Patient photo, scanned ID, imaging — stored in S3 (cloud) or MinIO (self-hosted).

Search with prefixes

name:, file:, phone:, email:, gender:, blood: — power users find anyone in seconds.

Patient binder (.tpb.zip)

Cross-tenant export and import — patients moving between practices keep their full record.

Custom fields without forking

A paediatric clinic and an oncology practice need very different patient data. Tenelix uses a JSON-driven form layer so each tenant — even each clinic within a group — can define its own fields, validations, and required sections without database migrations.

  • Field types: text, number, date, select, multi-select, signature, file, signature pad
  • Auto-versioning: edits to a published form preserve historical submissions
  • Visibility toggles per role and per patient state

PHI access logging is on by default

Every read of a patient record emits a structured PHI event — who accessed what, when, from where, in which tenant. The events flow into a dedicated phi log channel and are queryable in your audit dashboard.

  • Tenant-aware: events are scoped and attributable
  • Queryable: filter by patient_id, user_id, time, action
  • Compliance-ready: HIPAA / GDPR / NDPA-2023 patterns supported

Ready when you are

Bring this module live in your clinic.

Join early access and see it in your context — configured with your services and your data.