industries · healthcare
healthcare software
patients actually open.
we design and ship healthcare products in mena. patient portals, telehealth, clinic operations, lab integrations. ux-first since 2015, with the privacy plumbing your compliance team will sign off on.
three things this industry actually needs from a software partner. nobody else says them out loud.
01
a portal nobody opens is a feature nobody used.
most patient portals are built like internal admin tools and shipped to consumers. the result is a 4 percent monthly active rate. the products that win design for the panicked parent at 2am, not the it team in the procurement meeting.
02
privacy is a workflow, not a checkbox.
data minimization, role-based access, append-only audit logs, consent capture at the right moment. these are design decisions made screen by screen, not a security policy you bolt on after the fact.
03
arabic is a clinical accuracy problem.
patient names, drug names, lab results, dosages. rtl-aware typography and number formatting are not aesthetics; they are the difference between a correctly-read prescription and a malpractice claim.
what we ship for healthcare teams, ranked by what most engagements actually need.
4× usage
the moment a patient stops trusting the app is the moment a phone call replaces it.
patient portal monthly active rates lift this much when ux is designed for the urgent moment, not the admin moment.
emr / his integrations
fhir, hl7v2, custom rest. local hospital information system bridges where standards do not exist.
consent + audit trails
append-only event logs, role-based redaction, hipaa-equivalent audit exports.
telehealth video + chat
lab + imaging integration
arabic + rtl from day one
patient names, drug names, lab results in english and arabic side-by-side. clinical accuracy is the brief.
four stages. fixed deliverables at each. no scope-creep invoices.
week 1 — discover
discover
we map clinical workflows, privacy perimeter, and stakeholder priorities before any design.
week 2 — design
design
patient-first design with provider efficiency as a constraint, arabic-rtl native throughout.
week 3 — build
build
production-grade engineering with audit trails, role-based access, and emr integrations from day one.
week 4 — operate
operate
launch, monitor, iterate with the clinical team in the loop.
every agency lists what they do. here is what we explicitly won't do for healthcare teams.
we will not design a "patient portal" that is really an admin form
admin tools have one user type and a salaried audience. patient products fight for attention with messages and food delivery. they need different design.
we will not skip ux research with real patients
you cannot design healthcare products from inside a hospital meeting room. five interviews with real patients in your target group changes the product more than five months of internal review.
we will not own clinical liability
we are a software partner. clinical decisions, patient consent, and liability sign-off belong with credentialed providers. we collaborate; we do not pretend to substitute.
pick the path that matches where you are.
how a healthcare build at maxiphy actually runs.