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

Wasfaty integration for pharmacies and hospitals in Saudi Arabia

Wasfaty is the Ministry of Health e-prescription service that links hospitals and primary care with community pharmacies. This is what the public sources say, what we could not find, and how Ventrecs prepares a hospital or pharmacy system.

What Wasfaty is

Wasfaty is an electronic prescription service in Saudi Arabia. The Ministry of Health introduced it in 2019 so that a patient prescribed medicines at a hospital or primary healthcare centre can collect them from a community pharmacy near home. It is managed by the National Unified Procurement Company, NUPCO.

In outline, a prescriber records the prescription electronically, the patient receives a code, and a registered pharmacy uses it to retrieve the prescription and dispense.

At a glance
Where
Saudi Arabia
Run by
NUPCO, under the supervision of the Ministry of Health
Introduced
2019
Connects
Hospitals and primary healthcare centres with community pharmacies
Public vendor documentation
None found: no public API, sandbox or integration guide
Wasfaty

Who takes part

Hospitals and primary healthcare centres that prescribe, as described by public sources.
Community pharmacies registered on the NUPCO platform with a valid pharmaceutical facility licence and a licensed pharmacist.
Software vendors only where the operator offers a system-to-system option, which we could not confirm publicly.
Wasfaty

What data is exchanged

PrescriptionsA prescription recorded electronically by the prescriber, with the medicine, route, dose and frequency held as structured data in Ventrecs.
DispensingWhat a registered pharmacy dispensed, with batch and expiry.
What is not publicNo public API, message specification or medicine catalogue was found. Ask NUPCO and the Ministry of Health which apply.
Wasfaty

What we could and could not verify

What is public

Public descriptions cover the purpose, the operator and the requirements for a pharmacy to join.

  • A Ministry of Health service managed by NUPCO
  • Pharmacy registration, licences, accredited suppliers and basic equipment
  • A code given to the patient and presented at the pharmacy

What we did not find

We looked for technical documentation of the kind a vendor needs.

  • No public API specification
  • No public sandbox or integration guide
  • No public statement of the medicine catalogue and codes used

Questions for the operator

Ask NUPCO and the Ministry of Health in writing.

  • Is there a system-to-system option for hospital and pharmacy software, and under which agreement?
  • Which catalogue and codes are used, and who maintains them?
  • Is there a test environment, and who grants access?
Wasfaty

How Ventrecs prepares for e-prescribing

Structured prescriptionsPrescriptions are written with ingredient and generic search, routes, dose and frequency as structured data, against a controlled formulary.
Verification and dispensingA pharmacist verifies before dispensing. Dispensing records batch and expiry and blocks recalled or quarantined stock at the moment of use.
Controlled medicinesA witness who is not the person dispensing, and an audit trail of who prescribed, changed and dispensed.
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 Wasfaty, 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

Wasfaty

Typical rollout steps

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

  1. 1
    DiscoverConfirm with NUPCO and the Ministry of Health 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 NUPCO and the Ministry of Health 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 NUPCO and the Ministry of Health where the operator requires it.
  8. 8
    HypercareClose monitoring in the first weeks, then hand-over to the agreed support process.
Wasfaty

Sources

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

Wasfaty

Questions we are asked

What is Wasfaty?

An electronic prescription service of the Saudi Ministry of Health, introduced in 2019 and managed by NUPCO. It links hospitals and primary healthcare centres with community pharmacies.

Is there a public API for Wasfaty?

We found no public API, sandbox or integration guide. Access for software vendors, if offered, is arranged with the operator.

What does a pharmacy need to join?

Registration on the NUPCO platform, a valid pharmaceutical facility licence, a licensed pharmacist classified by the Saudi Commission for Health Specialties, and basic equipment including a barcode reader and a printer.

Can Ventrecs connect us to Wasfaty?

Yes, as a project. Ventrecs Connect carries the messages through an integration layer with retry, a transaction log and a reconciliation queue. Once NUPCO and the Ministry of Health provide the specification and access, we scope, build and test the connection with you.

Talk to us about your setup

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