Skip to Content
العربيةBook a demo
Solutions
Platform
Integrations
Security & Delivery
Resources
Company
Book a demo

NPHIES integration for Saudi hospitals, clinics and laboratories

NPHIES is the national platform that providers and insurers use to exchange eligibility, prior authorisation, claims and payment messages. This is what it asks of a hospital system, and how Ventrecs scopes the connection.

What NPHIES is

NPHIES is the national platform for health and insurance exchange in Saudi Arabia. Healthcare providers and insurers exchange their insurance transactions through it, instead of through a separate connection to each insurer.

For a hospital or clinic, connecting means that eligibility checks, prior authorisation requests and claims leave the HIS as FHIR messages, and that every response, including one that arrives later, is applied to the right patient and charge.

At a glance
Where
Saudi Arabia
Launched by
The Council of Health Insurance
Carries
Eligibility, prior authorisation, claims, payment, communication
Standard
HL7 FHIR R4.0.1, in a published implementation guide
Transport
Mutually authenticated HTTPS, with polling for deferred responses
Published
Implementation guide, academy course and a sandbox reached through onboarding
NPHIES

Who needs to connect

Hospitals, clinics and other healthcare providers in Saudi Arabia that submit insurance transactions.
Technology vendors that build the connection for providers. The operator decides whether the provider, the vendor or both onboard, so ask early.
Groups with several facilities, where one internal claim model should feed every connection.
NPHIES

What data is exchanged

EligibilityWhether the patient's coverage applies, and the answer stored against the coverage.
Prior authorisationRequests and approvals, with validity and any amount limit.
ClaimsSingle and batch claims built from the charges the patient was billed.
Payment and communicationPayment notices, requests for more information and error notices.
NPHIES

What the exchange involves

Six transaction groups

The implementation guide organises the exchange into six groups. Each matches a step the hospital already performs.

  • Eligibility at the front desk
  • Authorisations from the clinical and insurance desk
  • Claims, payment notices and communication in finance and billing

Technical rules

The published guide sets rules that a hospital system has to meet.

  • FHIR R4.0.1 messages that carry a MessageHeader
  • Mutually authenticated HTTPS with an X.509 certificate issued by NPHIES
  • Polling for deferred responses, with up to 100 messages per poll

Onboarding

The operator defines the path, not the software vendor.

  • Mandatory training and registration on the NPHIES portal
  • Sandbox testing with synthetic data and conformance checks
  • Production once the integration requirements are complete
NPHIES

How Ventrecs handles it

Coverage and eligibilityPayers, plans, patient coverages with a priority, and eligibility checks that store their answer. Eligibility can use a generic REST connector or a FHIR R4 eligibility request connector.
Pre-authorisationRequests held with an approval number, validity and amount, linked to the service they cover.
ClaimsOne claim per encounter and coverage, a defined lifecycle, the payer response applied to each line, and an export as a FHIR R4 Claim.
Durable outboxMessages leave through an outbox with retry, a transaction log and a reconciliation queue, so a deferred, rejected or missing response is a visible state with an owner.
How the connection is delivered

Each connection is delivered as a project: scoped with your facility and NPHIES, built as an interface adapter on the Ventrecs integration layer, tested in the operator's environment and signed off before go-live. Where the operator requires approval or certification, it is part of the project plan.

Messages are carried by Ventrecs Connect. See how an integration is delivered, from scoping to monitoring. Ventrecs Connect · The integration lifecycle

NPHIES

Typical rollout steps

The same eight stages as every Ventrecs deployment, applied to this connection. How we deliver

  1. 1
    DiscoverConfirm with the NPHIES onboarding team which of your facility types must connect, and which messages or transactions apply.
  2. 2
    DesignAgree the message set, identifiers and code mappings, and name an owner for each interface.
  3. 3
    ConfigureSet up facilities, users, catalogues and the integration layer, with credentials held outside the clinical records.
  4. 4
    MigrateLoad the master data the exchange needs, such as facilities, clinicians and patient identifiers, and reconcile it.
  5. 5
    TestTest in the environment the NPHIES onboarding team provides, with synthetic data, including rejected and duplicate messages.
  6. 6
    TrainTrain the teams who watch the interface and fix the rejections.
  7. 7
    Go-liveCut over in phases with on-site support, and with sign-off from the NPHIES onboarding team where the operator requires it.
  8. 8
    HypercareClose monitoring in the first weeks, then hand-over to the agreed support process.
NPHIES

Sources

Operator and standards documents these statements rest on. Standards change, so work from the current version.

NPHIES

Questions we are asked

Do we connect directly to each insurer?

No. Providers and insurers exchange messages through NPHIES, which validates and routes them.

Which FHIR version does NPHIES use?

The published implementation guide for healthcare financial services is based on FHIR R4.0.1.

Is a response always immediate?

No. Some are deferred, so the provider system polls NPHIES, and a poll returns a maximum of 100 messages.

Can Ventrecs connect us to NPHIES?

Yes. We deliver the connection as a project: Ventrecs Connect carries the messages through an integration layer with retry, a transaction log and a reconciliation queue. We scope it with your facility, build and test it in the NPHIES sandbox, and agree the go-live plan with you.

Talk to us about your setup

Tell us about your facility and current systems. We will reply within one working day.