Consent is the default, not a setting
Health records are not shared until someone decides to share them. Access is granted per document, per clinician, and can be withdrawn without asking anyone’s permission.
About
Health information should follow the patient
Care gets fragmented in the gaps — between a prescription and whether it was taken, between a record existing and the right clinician being able to see it. So7tek exists to close those gaps without taking control away from the person the record belongs to.
The name
So7tek means “your health”
صحتك is what you say in Arabic when you wish someone well. The 7 stands in for the letter ح — the substitution people already make when writing Arabic on a keyboard.
It is a small thing, but it says the important part out loud: the health in question is yours, and so is the decision about who gets to see it.
Scope
What So7tek is — and what it isn’t
It is
- A platform for coordinating care between patients and clinicians
- A record of prescriptions, doses, consultations and documents
- A channel for live vital signs and secure messaging
- A consent system that patients control directly
It isn’t
- A medical provider — it gives no medical advice, diagnosis or treatment
- A diagnostic tool; the assistant answers from your data, it doesn’t conclude
- A video-calling product — virtual visits carry a link to your own video app
- A payment processor; fees and payments are recorded, not collected
In an emergency, contact your local emergency services. Do not use So7tek to seek urgent help.
How we build
Three commitments
Say what the software actually does
We would rather describe three capabilities accurately than imply ten. Where something is a record rather than an action — a payment entry, say — we call it that.
Care is a team activity
Patients, clinicians and the people around them all hold part of the picture. The platform’s job is to keep those parts consistent with each other.
Under the hood
Independent services, one coherent record
So7tek runs as separate services rather than a single application, so monitoring, messaging and AI can scale — and fail — without taking care delivery down with them.
- Core API
- Consultations, records, prescriptions, permissions
- Monitoring
- Live vitals ingestion and streaming
- Assistant
- Retrieval-grounded Q&A over a patient’s own data
- Messaging
- Real-time chat between patients and clinicians
- Notifications
- Push, email and in-app delivery
- Scheduling
- Appointment and medication reminders
Identity is handled by Keycloak (OIDC), data lives in PostgreSQL with per-domain schemas, and every service reports metrics, logs and uptime to a shared observability stack.
Want to see it properly?
We will walk you through the platform against your own workflow.