NPHIES Integration
The complete NPHIES platform. Financial and clinical, one vendor.
Haseelo is the only platform that covers both NPHIES programs in a single integration — Taameen for revenue cycle and Sehey for clinical data exchange. No middleware. No separate vendors. One connection to the national health infrastructure.
CCHI — Financial
Taameen
Insurance claims, eligibility verification, prior authorization, and payment reconciliation.
Live today
MoH — Clinical
Sehey
Encounters, clinical documents, medications, labs, radiology, immunizations, and the national patient record.
Ready now
Financial integration
Taameen — revenue cycle through NPHIES
Native NPHIES gateway with AI-powered claim scrubbing. Go live in days, not months.
Native NPHIES gateway
Direct mTLS connection with certificate lifecycle management. Eligibility, prior authorization, claim submission, and status polling through one platform. No middleware layer between you and CCHI.
Certificate management
Upload, rotate, and monitor your NPHIES mTLS certificates. Expiration alerts before they become outages. Sandbox testing with one-click environment switching.
Real-time eligibility
Verify patient eligibility and coverage details through NPHIES before the encounter. Batch verification for scheduled patients. Results cached and searchable.
Claim lifecycle
Draft, scrub, submit, and track claims through NPHIES. Three-stage AI scrubbing catches errors before CCHI sees them. Human-readable claim numbers your staff can quote on the phone.
Clinical integration
Sehey — clinical data exchange for NPHIES
20+ clinical interfaces across three protocol families. Encounters, documents, medications, labs, radiology, and immunizations — all flowing to the national patient record through one hub.
Encounter management
15 ADT event types over HL7v2 — admit, transfer, discharge, pre-admit, and updates. Real-time vital signs via ORU. Every encounter flows to the national longitudinal record automatically.
Clinical documents
Publish and retrieve discharge summaries, operative notes, consultation notes, progress notes, and referral letters. IHE XDS.b document registry with query and subscription notifications.
Medications and Raqeeb
Standard prescriptions and dispensing plus full Raqeeb compliance for controlled substances — mandatory height/weight, reason codes, SecureCode verification, and zero-refill enforcement. The national controlled substance registry, handled.
Laboratory integration
Lab orders and results in both CDA and FHIR formats. LOINC-coded observations, SNOMED findings, specimen tracking. Publish via XDS.b or submit as FHIR document bundles.
Radiology integration
Radiology orders, structured reports, and embedded-PDF reports. DICOM KOS metadata registration with WADO URLs. Your PACS keeps the images — we register the metadata.
Immunization and iEHR
Query and retrieve immunization summaries, immunization cards, and iEHR patient summaries. On-demand document generation with persisted versioning. The complete patient view, on request.
Architecture
One hub, three protocols
Your EMR sends simple REST/JSON to Haseelo. We handle the protocol complexity — transforming to the right format for each NPHIES interface. No rip-and-replace, no protocol expertise needed.
Encounters and vital signs
15 ADT event types, ORU observations. Standard pipe-delimited messages over HTTPS — not MLLP sockets.
Clinical documents
ITI-41 publish, ITI-18 query, ITI-43 retrieve, ITI-53 notifications. CDA R2 documents with MTOM/XOP binary attachments.
Medications, labs, radiology
Standard and Raqeeb prescriptions, dispensing, lab orders/results, radiology orders/reports. Profile-validated FHIR bundles.
Canonical FHIR pivot. Every inbound message is normalized to canonical FHIR R4, validated against NPHIES-CS profiles, then encoded for the target protocol. N sources + M interfaces = N+M mappings, not N×M. When NPHIES updates a spec, we update one adapter — your API stays the same.
Platform
Built into the integration core
Services that every clinical integration needs — shared across financial and clinical channels. Not bolt-ons. Not separate products.
Master Patient Index
Cross-system patient matching with Arabic name support. AnyAscii transliteration, phonetic matching, and fuzzy scoring resolve patients across systems — even when names are transliterated differently.
Clinical consent guard
PDPL-compliant consent enforcement. Every clinical exchange checks patient consent status before data leaves your facility. Granular or catch-all consent types with full audit trail.
Terminology service
LOINC, UCUM, RxNorm, ICD-10-AM, SNOMED CT (free in KSA), SCHI/SBS procedure codes, and SFDA drug codes. Lookup, expand, and translate — all in one service.
Message lineage
Every message tracked from ingress to delivery with per-hop content versioning. Operator replay, deduplication, and PHI-aware retention policies. When NPHIES rejects a message, you see exactly why.
Why not middleware?
Most NPHIES integrations bolt a middleware layer between your EMR and the national platform. That layer becomes the single point of failure and the hardest thing to maintain.
Middleware approach
- Separate vendor for financial, another for clinical
- 12–18 months to integrate NPHIES-CS
- Breaks with every NPHIES spec update
- Manual HL7v2/XDS.b/FHIR protocol handling
- No visibility into message success or failure
- Separate consent and audit systems
With Haseelo
- One platform for Taameen and Sehey
- 6–8 weeks to go live on clinical exchange
- Platform absorbs spec changes — your API stays stable
- Send REST/JSON, we handle protocol translation
- Real-time dashboards with per-message lineage
- Consent and audit built into the integration core
PDPL compliant
In-Kingdom data processing and storage
NPHIES certified
Vendor onboarding and certification
Row-level isolation
No other tenant can see your data
Full audit trails
Every clinical exchange logged immutably