The foundation’s first project
Care that follows
the patient.
In development
Hutham Healthcare is a connected healthcare platform designed to help healthcare organizations coordinate care around one continuous patient identity and a medical history that keeps its sources. This page describes the model it is being built around.
01 — The problem
Healthcare is fragmented. The patient is not.
One episode of care can pass through reception, a physician, a laboratory, a pharmacy, billing, a result that arrives days later, and follow-up somewhere else entirely.
A history rebuilt each time
Every stage asks the patient to tell their story again, and reassembles a history that already exists.
Context trapped in a visit
Information stays inside the encounter or the organization that recorded it, and where it came from becomes hard to establish.
Follow-up without an owner
A result that arrives after the consultation ends can drift away from the physician who asked for it.
Hutham is designed to make these relationships explicit: to treat care as a continuing journey with clear responsibility and context, rather than a set of screens that happen to describe the same person.
02 — One patient
One identity, held steady.
The defining object here is not the appointment, the invoice, or the clinic. It is the patient, and the record that continues with them.
Hutham gives the patient a platform-level identity designed to stay consistent over time. A Hutham patient card can help an organization recognize the correct patient at the desk without the card itself being a key that opens the medical record.
One patient identity
Designed to continue even when the visit, the physician, or the healthcare organization changes.
A patient card
Simplifies identification without carrying the record it points to.
Reissue without loss
Replacing a card does not have to break the continuity of the history behind it.
03 — The Unified Medical Record
A history that remembers where it came from.
السجل الطبي الموحد — a record built for continuity, not one that collapses every source into a single undifferentiated file.
Relevant healthcare information is brought into a coherent patient history without losing its origin. Information can carry where it was recorded, when, which healthcare encounter it belonged to, and which authorized professional was responsible for it.
That context is what keeps a record understandable years after the visit that produced it.
A unified record does not mean
“Any Hutham clinic can see all of your medical history.”
It means
A medical history designed for continuity, with information kept connected to its original source and shared only through authorized healthcare relationships.
04 — One connected journey
Six roles, one journey.
A visit is not designed as an isolated appointment. Depending on the healthcare organization, it can become a shared workflow in which each participant works with the information their role actually needs.
Reception
Identifies the patient and opens the journey with the operational information the desk needs.
Doctor
Works with relevant clinical context, documents the encounter, and keeps responsibility for what comes next.
Laboratory
Receives what is needed to perform and report the requested work, and returns results that stay attached to the journey.
Pharmacy
Receives the finalized prescription and relevant medication-safety information — not the whole clinical record.
Follow-up
Keeps a delayed result, a partial dispense, or an unresolved question connected to someone responsible for it.
Billing
Tracks payment against delivered services on its own track: a clinical journey is not rewritten because an amount is outstanding.
The goal is not to digitize each department. It is to make the handoffs between them coherent.
05 — Access and accountability
Privacy is a design decision.
Encryption is not a privacy model. Controlled disclosure is: information available according to healthcare responsibility and context.
Role-appropriate access
Being part of a healthcare organization does not automatically mean seeing everything about a patient.
Controlled sharing
Connecting information across organizations follows verification and authorized relationships, not convenience.
Accountable corrections
A correction improves the record without erasing it: the original, the change, who made it, and when it happened all remain.
Traceable origin
A result has a source. A clinical fact has a source. Nothing arrives in the record from nowhere.
Healthcare information should move when care requires it — not simply because a system is able to move it.
06 — Medication safety
Support for the decision, not the decision.
Structured medication knowledge exists here to make a relevant safety concern visible at the moment it matters.
The platform is designed around structured information about medications, active ingredients, medication families, and known patient allergies, so that relevant safety concerns can be surfaced during prescribing when the available information supports doing so.
Where a concern calls for human judgment, the workflow is built around explicit clinician awareness and confirmation.
What we do not claim
That every interaction is detected, that every prescription is safe, or that software decides whether a medication can be given.
What the platform is for
Surfacing relevant safety information during prescribing, and keeping the clinician’s awareness and confirmation part of the decision.
07 — Who it serves
One platform, three vantage points.
The same continuity looks different depending on where you stand in it.
Patients
Fewer disconnected records, a history that carries its own context, and healthcare information that is connected where care requires it rather than exposed by default.
Doctors
Relevant patient context, structured clinical history, prescription and laboratory workflows, medication-safety support, and follow-up whose ownership stays clear.
Healthcare organizations
Coordinated departments, role-appropriate access, accountable records, and financial operations that run alongside clinical work instead of through it.
08 — The long view
Healthcare should follow the patient.
Not the other way round.
Hutham Healthcare is in development. This page describes the model the platform is being built around; it is not a statement that every capability described is already running. What is operating, and from when, will be stated here and in the foundation’s financial notes.
Working in healthcare?