The daily problems

Where the work usually goes wrong.

01

Back office and clinical systems do not talk

Finance and HR run on their own tools, so management sees clinic activity only in monthly reports.

02

Rosters and expiry dates are manual

Shifts, overtime, staff documents and licence expiry dates are maintained by hand, and one missed date stops a person working.

03

Supplies are ordered without a trail

Medical and office supplies are requested by message and approved verbally, so spend per department is unclear.

04

Patients ask the same questions

Opening hours, preparation instructions, locations and documents needed are answered again and again by phone.

05

Sensitive data needs deliberate handling

Health information is among the most sensitive personal data, and where it is hosted and who can reach it needs to be decided, not defaulted.

Saudi requirements

What the software handles for you.

These are the Saudi regimes that touch this sector, and what the software does about each. Your proposal confirms which apply to your company. This is not legal advice; confirm obligations with your adviser.

RequirementWhat the software handles
Personal data (PDPL)Health information is treated as sensitive personal data. Access by role, an audit trail and the hosting location are agreed per project.
VAT at 15%Calculated per invoice line, with the treatment you set for your services, and posted to VAT accounts.
ZATCA e-invoicingInvoicing is built to work with ZATCA e-invoicing requirements. The scope for your company is confirmed in your proposal.
GOSI, WPS, Saudization, IqamaPayroll, contributions, salary files, headcount tracking and Iqama expiry dates in the HR module.

Saudi compliance

How a project starts

From first call to a working system.

The order differs a little by sector. The principle does not: a written scope comes first, and you test with your own data before anything goes live.

  1. Draw the boundary

    We agree which systems stay as they are, which data may be shared with the new ones, and what must never leave the clinical system.

  2. Decide hosting and access first

    Hosting location and who can see what are settled before any screen is designed.

  3. Start with the back office

    Finance, purchasing and rosters go first, because they carry the least sensitive data.

  4. Add patient-facing answers last

    An assistant or portal is added once the content it may answer from is approved by your staff.

Questions

What buyers in this sector ask.

Can you store patient records?

We do not offer a clinical records product. Where a custom build must hold patient information, hosting, access and audit trail are decided first and written into the proposal.

Where can health data be hosted?

Hosting in Saudi Arabia or on your own servers are both options. Which one your licence or regulator requires is for you to confirm; we build to your decision.

Can a chatbot give medical advice?

No. A patient-facing assistant answers from the documents you supply, such as services, hours and preparation instructions, and hands over to staff for anything clinical.

Can it hold licence expiry dates for staff?

Iqama expiry tracking is part of the HR module. Other dates, such as professional licences, are set up as tracked fields for your deployment and confirmed in the proposal.