Waseel Connect is a Saudi NPHIES integration bundle that automates claim generation and claims management for clinics and hospitals; the vendor states that its services are trusted by Saudi healthcare providers and institutions and describes Waseel Connect as the leading software chosen by KSA healthcare professionals and clinics (waseel.com/connect, verified 2026-11-06). Pricing is on request.
Many providers run Waseel as a claims layer next to a separate HIS or EMR, which means two systems, two data models and reconciliation work between them. This page compares that model, as described on Waseel's site, with SBS HIS and RCM from SBS Group, where NPHIES eligibility, pre-authorization, claims and payment reconciliation run inside the same clinical and billing system, with ZATCA-compliant invoicing and an Odoo ERP back-office.
| Criteria | SBS (Odoo / SBS HIS) | Waseel |
|---|---|---|
| Arabic & RTL | Arabic/English clinical and administrative screens with RTL layouts and Arabic patient documents; bilingual trainers. | Saudi company (وصيل); website in Arabic and English. |
| E-invoicing compliance (ZATCA) | Patient and insurer invoices issued ZATCA Phase 2 compliant through the integrated Odoo finance layer; SBS handles onboarding on the Fatoora platform. | Not part of the Waseel Connect bundle as described on its page; invoicing stays in the provider's billing system. |
| NPHIES / insurance integration | Eligibility checks, pre-authorization, claim submission and payment reconciliation built into SBS HIS/RCM (NPHIES page: sbs-me.com/ar/healthcare/nphies/). | Core product: Waseel Connect — NPHIES integration with automated claim generation, eligibility and claims management (waseel.com/connect). |
| Local implementation team | Implementation and support teams in Saudi Arabia and Egypt; on-site go-live support; 24/7 dedicated support (per sbs-me.com). | Saudi-based; 'trusted by Saudi healthcare providers and institutions' (vendor statement). |
| Customization / interoperability | Modular platform (HIS, clinic, dental, LIS, RIS, emergency, physiotherapy, RCM) with configurable forms and workflows and HL7/FHIR interfaces; Odoo ERP back-office (finance, HR, supply chain). | Connectivity and claims layer that sits beside the provider's existing HIS/EMR; clinical documentation remains in the other system. |
| Hosting options | SBS-managed cloud or on-premise inside the facility. | Cloud service. |
| Pricing model | Modular licence sized to the facility + implementation quote; transparent module list, no hidden per-module surprises after signature. | Bundle pricing on request; not public. |
| Support SLA | SLA contract with response/resolution targets, named account manager, 24/7 dedicated support (per sbs-me.com). | Not published. |
| Integrations | PACS/RIS with AI imaging, LIS and analyzers, pharmacy, NPHIES, Odoo ERP, patient portal and identity management. | NPHIES and payers; integration with the provider's existing systems. |
| Scalability | Single clinic to polyclinic to multi-hospital group on one platform. | Clinics to hospitals, scaled by claims volume. |
Who should switch
- Providers whose HIS and claims platform disagree on services, prices or patient data and who spend staff time reconciling the two.
- Hospitals and polyclinics replacing a legacy HIS that want NPHIES, billing and clinical documentation in one vendor's system.
- Groups that want revenue-cycle KPIs (denials, days in A/R, first-pass rate) from the same database as the clinical record.
- Facilities that need ZATCA-compliant patient invoicing and insurer invoicing from the same billing engine.
- Organizations that want finance, HR and procurement on Odoo ERP integrated with the HIS.
Migration and onboarding with SBS
SBS maps your payer contracts, price lists, service codes and open claims, replays recent eligibility and pre-authorization cases in the NPHIES test environment, and runs claims in parallel for one cycle before cut-over so no submission window is missed. Discovery and claims-gap analysis are free; migration is quoted as a fixed package.
Frequently asked questions
Can SBS replace only the claims layer and keep our HIS?
SBS RCM can run alongside an existing HIS through HL7/FHIR interfaces, but the full benefit — one data model for documentation, billing and claims — comes with SBS HIS. SBS scopes both options in the discovery session.
Does SBS handle NPHIES pre-authorization and communication requests?
Yes. Eligibility, pre-authorization, claim submission, claim communication and payment reconciliation are supported inside SBS HIS/RCM, with onboarding and test cases managed by SBS.
How does SBS reduce claim rejections?
Validation rules run at order and discharge time (coverage, codes, attachments), so errors are caught before submission; denial reasons are tracked for root-cause fixes.
What is the cost model?
A modular licence by facility size plus implementation; SBS shares the module list and a three-year total cost before signature, with no per-claim transaction fees in the SBS licence.
Request a free claims-gap analysis or message SBS on WhatsApp (+20 105 023 2113).