Why it exists
A clinician who sees twenty patients a day writes twenty notes, and the writing takes the hours that should have gone to the patients — or to going home.
Most of a note has already been said in the room: the complaint, the history, the answers to the questions asked, the plan the clinician gives out loud. Sard listens to that conversation and drafts the note from it, so the clinician’s time goes to checking the note rather than typing it.
What it is not
Sard does not diagnose, and it does not decide. It does not add a treatment, a test or a follow-up the clinician did not say, however standard it would be, and it does not complete a dose. These are rules in the code that drafts the note, not lines in a policy.
What it is built on
-
Nothing unsaid is asserted
If it was not said, the note does not say it — not as a negative, not as a normal finding, not as a plan.
-
Every line can be checked
Every line carries a mark that says where it came from, and opens the words it came from.
-
The clinician can always correct it
No part of the draft is final, hidden or locked away from you before you sign it.
-
A consultation is never lost
A visit cannot be recorded twice: the patient has gone home. So Sard is built so that a failure after the recording — in the transcript or the draft — leaves the recording itself untouched.
-
Arabic is not a translation
Sard is built Arabic-first, for consultations that change language mid-sentence, and its interface reads right to left as a layout, not as a setting.
Where it is now
Sard is in a pilot with a small number of clinics in Jordan. Every pilot visit is one the patient has agreed to record, asked in the room, for that visit.
It is not yet cleared for routine patient data. We would rather say so here than have you find out in a clinic.
Write to us
Questions, a pilot for your clinic, or something we got wrong: [email protected]