Healthcare software built for regulated environments.
For clinics, hospital groups, digital health start-ups and insurers. Patient portals, booking, telehealth, HL7/FHIR integrations and claims flows — with access control and audit trails designed in from the first schema.
We build patient portals, clinic booking, telehealth and integrations for providers and health start-ups in Saudi Arabia, the UAE, Qatar and Oman, then Europe and Pakistan — built to NPHIES, PDPL and DHA rules. We have not shipped a clinical system; access control and audit trails transfer from our 1Link portal.
Updated November 2026
A practice, not a sales territory.
Healthcare doesn't forgive architecture shortcuts. A leak of patient data is a regulator's investigation and a collapse of patient trust, not a PR problem. In the Gulf that means Saudi PDPL, UAE health data law and Qatar PDPPL; in Europe, GDPR's rules for health data; in the US, HIPAA. We design access control, audit logging and encryption in from the first schema, not as a retrofit.
We have not shipped a clinical platform, and we say so. What transfers: role-based access, reporting and audit trails from the card-management portal we built for 1Link, deployed on its own infrastructure; payments and invoicing from Pay2m; and registration flows from the sites we build in Doha. HL7 and FHIR integration is standards work, and we scope it with your clinical team before we write code.
The gap most teams miss isn't the video call — it's what happens when the connection drops mid-consultation, when an insurer rejects a claim, or when a record has to reach a national health exchange. We plan for those cases first.
Sub-verticals.
Common engagements.
Patient data architecture
Data flows, role-based access, audit logging and encryption at rest designed from the ground up, so a privacy review against PDPL, GDPR or HIPAA is straightforward rather than a retrofit.
EHR & FHIR integrations
HL7 v2 and FHIR R4 integrations with hospital systems and national exchanges such as Dubai's NABIDH and Abu Dhabi's Malaffi. We build the middleware and document every data flow; access to each system is arranged with its owner.
Insurance claims & eligibility
Eligibility checks, pre-authorisation and claims submission through Saudi Arabia's NPHIES, with rejection reasons shown to the billing team instead of buried in a log.
Telehealth & virtual care platforms
Video, async messaging, scheduling and prescription workflows — built for clinical reliability, not just connectivity. Tested for real-world network degradation.
AI for clinical use cases
Clinical documentation, decision support, triage assistants and pre-authorisation summaries. Built with explainability, audit trails and clinician override controls.
Patient portal & booking
Appointment booking, reminders on WhatsApp and SMS, lab results, care plans and payments, in Arabic and English. Designed for the patients who are least digitally fluent — your most vulnerable users.
Healthcare, market by market.
Gulf — Saudi Arabia, UAE, Qatar, Oman
Saudi Arabia routes insurance claims through NPHIES and treats health data as sensitive under PDPL. Dubai and Abu Dhabi connect providers to NABIDH and Malaffi, and UAE law expects health data to stay in the country. Patients expect Arabic and English, and WhatsApp for reminders.
Spain, Italy, France
Health data is a special category under GDPR, and France requires certified hosting (HDS) for it. Software that diagnoses or guides treatment falls under the EU Medical Device Regulation.
Pakistan
Clinics and hospital groups run on a mix of local hospital systems and paper. Patient apps, booking and pharmacy ordering are where software helps first, and Urdu and English both matter.
Work that transfers to healthcare.
When you need a certified clinical system.
If you need a full hospital information system or an EHR, buy an established product — clinical systems take years to build and certify, and are not a custom job. If you need a vendor that holds HIPAA, ISO 27001 or HDS certification itself, that is not us. Hire us for what sits around the core: portals, booking, integrations, claims and internal tools.
Where to start.
Built for regulated work.
Tools we reach for first.
Frequently asked.
8 questions answered. Still have one? Reach out.
No — we hold no certification of our own and we are not a covered entity. We build to the rules that apply to you: Saudi PDPL, UAE health data law, GDPR or the HIPAA Security Rule — access control, audit logging, encryption at rest and in transit, minimum necessary access. Where a data-processing agreement or BAA is needed, it is agreed in the contract. Formal certification and audit work is done by a specialist consultant, not by us.
Other sectors.
Tell us where it hurts.
We will say honestly whether we have shipped in your sector, what transfers from the ones we have, and where the expensive mistakes usually are.