A Hospital Information System built for Saudi operations
An integrated HIS connecting reception, clinics, laboratory, radiology, pharmacy and billing into one path — NPHIES and FHIR ready, and auditable by design.
What is a Hospital Information System, and what must it cover in Saudi Arabia?
A Hospital Information System (HIS) is the central system managing the patient journey alongside the administrative and financial operations of a healthcare facility. In the Saudi context it must cover, at minimum, the electronic medical record (EMR), appointments and reception, the laboratory system (LIS), radiology (RIS/PACS), pharmacy and inventory, and the revenue cycle with NPHIES integration for insurance eligibility, pre-authorisation and claims. Data exchange must follow HL7 FHIR, every access to patient data must be recorded in an audit trail, and hosting must respect Saudi health-data classification requirements inside the Kingdom.
One system instead of five that do not talk to each other.
What drains healthcare facilities is rarely the absence of systems — it is their fragmentation. We build an HIS layer that moves patient data between departments without re-entry or conflict.
- A unified patient record following the case from admission to discharge
- NPHIES integration for eligibility, authorisations and claims
- HL7 FHIR data exchange with external systems
- Granular permissions and an audit entry for every access
- Live operational dashboards for occupancy, appointments and revenue cycle
Modules we build or integrate with
We start with the modules that actually move operations, then expand in stages rather than a delayed all-at-once launch.
Electronic Medical Record
Structured clinical notes, prescriptions, allergies and a searchable, auditable history.
Reception & appointments
Clinic scheduling, waiting lists, reminders and no-show handling.
Laboratory (LIS)
Test orders, barcoding, result entry and critical values with immediate alerting.
Radiology (RIS)
Imaging orders, modality scheduling, reporting and PACS integration.
Pharmacy & inventory
Dispensing, reorder thresholds, batch tracking and expiry control.
Revenue cycle & billing
Pricing, discounts, insurance claims and rejection follow-up.
The integrations operations depend on
No system lives alone — these are the parties we typically connect in this kind of project.
This is not a pitch — we built it and it runs
The capabilities below are implemented in a healthcare platform we delivered and that runs in production, and are the closest to this track.
السجل الطبي والعمل السريري
طبقة سريرية كاملة تربط الزيارة بالسجل بالطلبات بالنتائج، مع ترميز معياري وتوثيق ملزم.
- ملف EMR للمريض ولوحة سريرية للممارس
- الوصفات الطبية والإجازات المرضية والطلبات الطبية والتقارير الموحّدة
- نظام مختبر: كتالوج فحوصات، ترميز LOINC، إدخال نتائج
- نظام أشعة: كتالوج، ترميز، طلبات، نتائج
- ترميز التشخيص ICD-10 وأكواد نظام متسلسلة
الامتثال وحوكمة البيانات الصحية
الطبقة التي تفصل نظاماً صحياً جاداً عن تطبيق إدارة مواعيد.
- رقم ملف طبي فريد وضوابط تكرار الهوية وتنبيه تشابه الأسماء
- موافقات المريض والموافقات الطبية الإلزامية قبل الإجراءات
- مسار تدقيق سريري آلي للوصفات والإجازات والتقارير والموافقات
- سياسة احتفاظ عشر سنوات مع تحديد آلي للسجلات المستحقة للمراجعة
- سجل حوادث سلامة المرضى مع فرز ذكي
المالية والفوترة الضريبية
دورة مالية كاملة متصلة بالتشغيل، مع فوترة إلكترونية معتمدة.
- فوترة إلكترونية ZATCA المرحلة الثانية: سجل مستندات، XML موقّع، طابور إرسال آلي
- تتبّع محاولات الإرسال وضوابط فصل بين البيئة التجريبية والحقيقية
- ضريبة القيمة المضافة: تسويات وإقرارات وملفات ضريبية للخدمات
- قواعد الإعفاء الضريبي للخدمات الصحية
- شجرة حسابات هرمية ومراكز تكلفة وقيود ومرفقات
المخزون الطبي
من الكتالوج حتى استهلاك الصنف داخل الزيارة وقيده محاسبياً.
- كتالوج أصناف واستهلاك مرتبط بالخدمة
- دورة حياة الأرقام التسلسلية
- عهدة الممارسين ووحدات الحركة
- طبقة سريرية للمخزون في الرعاية المنزلية
- قيود محاسبية مرتبطة بحركة المخزون
Questions about Hospital Information System
Direct answers to what is usually asked before adopting the solution.
How long does an HIS rollout take for a mid-sized facility?
The practical path starts with an operational core — reception, EMR and billing — in 10 to 16 weeks, then adds laboratory, radiology and pharmacy in batches. A single big-bang launch raises risk and delays return, so we do not recommend it.
Does the system integrate with NPHIES?
Yes. We build an NPHIES integration layer covering eligibility verification, pre-authorisation and claim submission, handling responses and rejections inside the system instead of a parallel manual process.
Should we replace our current system or integrate with it?
Either is possible. In many cases the most economical option is to keep the existing finance or laboratory system and integrate through FHIR or an API, building only the layers that actually cause pain. We start with an architectural assessment before any commitment.
Where is patient data hosted?
Inside Saudi Arabia, on infrastructure that respects health-data classification requirements, with encryption in transit and at rest and a full access log. External hosting is only considered with explicit authorisation and a clear compliance path.
Related solutions
Most facilities need more than one layer — these are the closest solutions to this track.
Discuss applying this to your facility.
We start with a short assessment session defining scope, integrations and launch path.
