Clinical and practice systems
Multi-site practice management and the internal tools clinics run on — written up in the UK Medical Practice Systems case study.
Healthcare & clinical software
Healthcare software development,engineered for people who cannot afford downtime.
I design and build software for clinicians, healthcare providers and medical educators — clinic and practice systems, web platforms, mobile apps and the systems behind them — and I stay accountable for it after launch.
- Clinicians & providers
- Web and mobile
- Accountable after launch
What I build
Software for healthcare, built with healthcare in mind.
Healthcare software carries sensitive data and busy users. I plan for both from the first conversation.
Medical education
Exam preparation, question banks and AI oral-viva practice for postgraduate candidates.
Mobile apps for clinicians
iOS and Android apps that work on the move and keep working when the connection drops.
Published work
Products that are live and in use.
Every link goes to the real product or its store listing.
for algarra7 Ltd
Smart FRCS AI
An AI examiner for the FRCS oral viva — spoken, examiner-led and scored on the real band scale
for algarra7 Ltd
SmartFRCS
FRCS exam preparation on the web, Android and iOS — and it keeps working offline
Healthcare
UK Medical Practice Systems
Multi-site clinic management platforms for UK medical practices. Patient portals and appointment systems.
What's included
What I plan for in healthcare projects.
Every project is scoped individually; these considerations are part of every healthcare scope:
- Data handlingWhat is stored, where, for how long and who can see it — decided up front, not retrofitted.
- Roles and permissionsAccess that matches how the organisation actually works.
- Audit trailsA record of who changed what, where the work requires it.
- Your compliance requirementsTell me the regulations and policies that apply at the start, so they are part of the plan.
- ReliabilityBackups, monitoring and release practices that keep the system running.
How it works
A clear process, with you at every step.
No fixed promises before the facts are known. Timelines and cost come from the agreed scope, and you see progress at every milestone.
Discovery call
We talk through the idea, the users and the constraints. You get an honest view of whether — and how — to build it.
Scope & estimate
A written scope with milestones and an estimate based on it, so you know exactly what is being built.
Design
Flows and screens you can click through and approve before any development starts.
Build in milestones
Development in agreed stages, with working builds you can review as the work progresses.
Release
Final testing, deployment and — for apps — store listings and submission.
Support & growth
Updates, fixes and the next version, under the support arrangement we agreed.
Founder-led
You won't be passed to an account manager. You talk to the engineer who designs your product and answers for it.
Khalid AboubakrFounder & principal engineer
- I lead the architecture, the technical decisions and the quality of what ships.
- When a project needs more hands, I bring in senior specialists I trust — and I stay accountable for the result.
- Healthcare and medical education are my flagship work; government, education and commercial products sit alongside them.
Questions
Before you get in touch.
Do you hold healthcare certifications?
I don't claim certifications I don't hold. Tell me the regulatory and data requirements your project has at the start, and they become part of the scope and the architecture.
Have you worked with UK healthcare and medical education?
Yes — practice-management systems for UK clinics, and medical education products for two UK-registered institutions.
How do you protect patient data?
Security is treated as an engineering requirement of each project, decided in the design rather than after launch. The controls are chosen for the data the system holds and its risk — for example how data is encrypted, who can access what, which actions are logged, where it is hosted and what third-party services, including AI providers, may receive. Your regulatory requirements are part of that specification.
Can the new software work with the clinical systems we already use?
Often, but it depends on what those systems expose: an API, a standard such as FHIR, or only exports. I check that early, because an integration the existing vendor does not support changes the plan and the estimate.
Who owns the code and the accounts?
Ownership of the code, the store listings and the hosting accounts is agreed in writing before work starts.
How much will it cost?
It depends on what the product has to do: features, user types, integrations and the systems behind it. After a discovery call you get a written scope and an estimate based on it — not a number guessed in advance.
How long will it take?
That also comes from the scope. Once we agree on it, you get a milestone plan with the order in which features will be delivered.
Who will I actually be working with?
With me, directly. I lead the project from the first call; when specialists are needed, I bring them in and stay responsible for their work.
Start your project
Tell me about the product you want to build.
Your message comes straight to me. I'll reply personally with questions that sharpen the plan, an honest read on scope, or a clear no if I'm not the right fit.
Khalid AboubakrFounder & principal engineer