Industries
Software that moves the patient record without losing it.
Clinics, hospitals and insurers in the Kingdom run on a mix of EMRs, claims platforms and paper. We connect those systems, build the patient-facing layer on top, and treat health data as the most sensitive thing we will ever touch.
What this removes.
Claims rejected for avoidable data errors
Today
Billing staff re-key diagnosis and service codes into insurer portals, and small mismatches send claims back for weeks.
With the system
Claims built from the clinical record, validated before submission, with rejection reasons routed back to the right desk.
An EMR that does not share
Today
Lab, radiology and pharmacy each keep their own system, and a doctor sees half the picture unless someone phones across.
With the system
A connector layer that brings those records into one timeline, using the standards your EMR already supports.
Patients who book by phone and miss by habit
Today
Reception spends the day answering calls, and no-shows leave empty slots nobody can refill in time. Doctors lose clinic hours to gaps they were never told about.
With the system
Self-service booking, reminders and rescheduling in Arabic and English, with the schedule updating in real time.
Health data held more loosely than anyone admits
Today
Reports travel by email and shared drives, and nobody can say who opened what.
With the system
Role-based access, audit trails and encryption designed into the system rather than bolted on.
What actually applies.
NPHIES
NPHIES is the national platform for health insurance exchange operated under the Council of Health Insurance, covering eligibility, pre-authorisation and claims between providers and payers. We build integrations that follow its published message formats and onboarding steps. Your facility's registration with the platform stays with you.
Ministry of Health and CHI rules
Providers answer to Ministry of Health licensing requirements and to Council of Health Insurance rules on how insured services are billed and documented. We confirm the rules that apply to your facility type at scoping and build the workflow around them. Where a rule is unclear, we ask your compliance lead rather than guess.
Health data under PDPL
Health records fall under the sensitive category in the Personal Data Protection Law, which raises the bar on consent, purpose limits and cross-border transfer. We design consent capture, retention and in-Kingdom storage into the platform from the first diagram.
Delivered through these services.
Asked before signing.
Can you integrate with our existing EMR instead of replacing it?
Yes, and that is the usual route. We connect through the interfaces your EMR vendor exposes, such as HL7 or FHIR where supported, and build around it so clinicians keep the screens they already know.
Is the platform approved by the Ministry of Health or CHI?
Software is not approved by those bodies in the way a facility is licensed. We build to the requirements that apply and help you prepare onboarding material, while facility licences and platform registrations remain yours.
Where is patient data stored?
Inside the Kingdom. We design for in-Kingdom hosting from the start, keep identifiers separated from clinical content where possible, and agree the hosting location with you before any data is migrated.
How long does a patient app take?
A focused first release with booking, records and notifications usually takes 12 to 18 weeks. Telehealth, payments and insurer integration extend that, and we agree the order of release at scoping. Clinicians join the first design sessions, because a tool that adds clicks to a consultation will be abandoned.
Show us the workflow that costs you the most time.
Tell us where staff re-type, chase or wait. We will map it against NPHIES and your EMR and tell you what is worth connecting first.