Medical doctor
Dr. AlbaraPortfolio
Scroll to play
My internship batch used to share one paper roster. Now every booking and every duty point is in the app, and I still answer the support messages myself.
Every intern in cohort 194 has a record in the systems I built for the internship office, and the hospital administration runs the year from the same records. Doctors seconded from other universities are in there too.
It began in my first year of medical school as a way to share study files with my class. I coded the bot from scratch.
My classmates elected me in 2020 and kept re-electing me every year until we graduated.
The Internal Medicine one sends out a new schedule every week, along with a report on any gaps in cover.
Doctors at Kasr Al Ainy copy handwritten admission sheets into MRM, the records system, by hand. Scrybe, an AI app I programmed for the ward PC, does the copying and stops short of saving.
A doctor photographs the sheet with a phone, and the photo comes over to the PC by cable.
The patient's name is masked before any model sees the page. Scrybe never stores it and never sends it.
Gemini and Groq each read the handwriting separately. If their readings differ, the field is flagged and both versions are shown side by side.
The doctor goes through every field, fixes what is wrong and confirms the rest.
Scrybe types the confirmed fields into MRM. You press Save, because the app never will.
In RotaMate, my AI-supported shift app, a Duty Assistant answers interns' questions from the published guides. The booking side runs on rules I wrote, and this is how they share out the cover.
Interns pick the shifts they want. Left to first come, first served, a few keen people end up holding most of the fortnight.
Then the rules count everyone's shifts and hand cover from the busiest to the least busy, never onto the day after a night. Each intern sees every change that touches them.
The same fortnight, shared out evenly.
Internal Medicine records is the department's records app. The part I'm building now lets a doctor say the note instead of typing it.
The doctor opens the patient's page and types the name and file number by hand. The AI never hears either of them.
Then they say the rest out loud, moving between Arabic and English as they like, and Gemini turns it into the department's template.
Every field it fills stays marked. A blood pressure of 1500/90 can't be right, so it gets flagged and left empty.
The doctor checks each mark and signs. Only then is it saved, logged as AI-assisted, and the recording deleted.
Prof. Dr. Ehab El Refaee and I came up with the alumni system, and I programmed it with AI coding agents. It finds where the faculty's graduates went and what they've published.
The agents worked through a plan one task at a time, and more than 500 tests check what they wrote.
There's no AI inside the app itself. A fixed rule scores each match: half for the name, a quarter for a Kasr Al Ainy link, the rest for specialty and timing.
A strong score only marks a match. It still waits until a person says it's the same doctor.
The two readings disagree here, so the doctor checks the sheet.
Patient
Age54
WardMedicine 3
ComplaintShortness of breath for two days
Pulse96
Blood pressure135/85
PlanChest X-ray, bloods, review in the morning
You press Save.
Ward note
Sample patient, made up.
Patient
File no.
Typed by hand. The AI never hears it.
Listening
عنده ألم في الصدر من الصبح
pulse 96, BP 1500 over 90, plan ECG and troponin
Recording deleted
ComplaintChest pain since the morning
Pulse96
Blood pressure150/901500/90 can't be right. Left for the doctor.
PlanECG and troponin
Build plan
Worked through by AI coding agents, one task at a time.
Possible match
Sample. The doctor is made up.
Name0.46 / 0.5
Kasr Al Ainy link0.25 / 0.25
Specialty and timing0.15 / 0.25
0.86, strong
Same doctorNot themUnsure
A person decided
Prof. Dr. Ehab El Refaee runs a neuroendoscopy fellowship, and this plans it. The first cycle starts in January 2027. Organizers see who teaches each session and where there's still a gap, and faculty pick their own sessions and dates.
Some are tools I made for myself, some are client work, and a few are still being planned.
See all 19 projectsThis is what I'm working on now. None of it is done yet, so you won't find any results here until there are some worth showing.
On the side I'm building payment checks for Smart Vision. A student sends a screenshot of the transfer, and the system reads it and checks that the reference hasn't been used before. Anything doubtful goes to a person.
I only take on work that interests me or lets me build something new, and I research it properly first.
