Compliance, stated plainly
What each regulation requires, what our system or site provides for it, and what we do not claim yet.
Regulation is why many clinics buy software: insurance claims that must go through a national platform, invoices that must carry certain fields, patient data that must stay in the country and be used only with consent, a licence that waits for an integration. Each page below covers one regulation in three parts: the requirement, what the Alnitak clinic system or booking site provides for it today, and what is planned but not done. Nothing here says certified unless a certificate exists.
NPHIES: claims through the national platform
Mandatory for every facility that bills insurance. Here is what it asks of your software, and what ours does and does not do yet.
ComplianceZATCA e-invoicing: the invoice a clinic must issue
Phase 2 reached clinics by revenue wave. Here is what the invoice must contain and what our invoicing module produces.
CompliancePDPL: patient data, consent and where it lives
Health data is sensitive data under the law. Here is what that means for a booking site, a WhatsApp assistant and a clinic system.
ComplianceNABIDH: the unified record a licence waits for
A DHA-licensed clinic must connect to NABIDH. Here is what the connection expects from your records, and what we do and do not do yet.
ComplianceE-receipt and universal health insurance: what changes for a clinic
Two roll-outs reach private clinics in Egypt: the Tax Authority's e-receipt and the universal health insurance system. Here is what each asks of your software.
Compliance
These pages are engineering notes, not legal advice. Confirm your obligations with the regulator or a licensed adviser before you rely on them.
Send how your clinic books today. We diagnose before we quote.
A written map of where bookings and records are lost, what a WhatsApp assistant can take over, and a fixed price for the first step, within two working days.
Prefer to talk? Message us on WhatsApp