Jordan is a regional medical tourism destination, which means hospitals here handle a patient mix and an administrative load that most systems of their size never face. Scheduling, records and billing have to work across languages, insurers and countries.
We build clinical and operational systems for that reality: patient flow platforms that coordinate appointments across departments without double-booking, records systems that keep bilingual clinical notes searchable, and insurance claim workflows that handle both local funds and international providers.
Patient data governance drives the architecture. Access is role-scoped and logged, data stays where regulation requires, and every integration is designed on the assumption that it will be audited.
We are careful about where AI belongs in a clinical setting. Decision support that surfaces relevant history to a clinician is valuable. A model that makes a diagnosis unsupervised is not something we will build. The distinction matters, and we hold to it.
Typical outcomes: four hours of daily manual coordination removed, patient wait times down by roughly a third, and claim rejection rates cut through validation at the point of entry rather than after submission.
