Frequently asked questions about Nabd
Straight answers about what Nabd does today, what is integration-ready, what is still planned, and how a hospital moves to it.
Product and modules
What does Nabd cover?
Patient registration and the medical record, appointments and clinic queues, emergency, inpatient wards and nursing, operating theatres, laboratory, radiology, blood bank, pharmacy and stores, billing, insurance and claims, accounting, HR, quality, medical equipment, reports and a patient app. See all features.
Does Nabd work in Arabic and English?
Yes. The interface is right-to-left Arabic by default and every user can switch to English. Patient names are recorded in both languages, and invoices print in both.
What is the difference between Nabd HIS and Nabd on Odoo?
Nabd HIS is a standalone system that covers every hospital department. Nabd on Odoo 19 adds the medical layer (patient file, clinics, medical billing and pharmacy) on top of Odoo apps and suits medical centres and organisations that already run Odoo.
Is there a patient app?
Yes, one app for iPhone and Android plus a web portal, for booking, results, prescriptions and bills. It is ready but not yet published in the app stores.
Does Nabd use artificial intelligence?
Only if the hospital turns it on. The optional assistant drafts discharge summaries, suggests ICD-10 codes and writes Arabic patient instructions; it is off by default, receives de-identified data and every use is recorded. Clinicians review every draft.
Deployment, hosting and data protection
Where does Nabd run?
On the hospital's own server inside the hospital, or on a dedicated server chosen with you. Nabd is installed for each hospital as a ready program (Docker images); it is not a shared online service.
Can we sign up and subscribe online?
No. There is no online sign-up or self-service subscription. Every hospital starts with a demo, then a discovery session, a written proposal and an implementation by the Flexcode Systems team.
Does any patient data leave the hospital?
No. The licence check sends five technical values (licence id, installation id, a non-reversible fingerprint, the version and the number of active users) and never patient or personal data. Optional AI features that call foreign services are off by default.
What happens if the internet or our licence lapses?
The hospital keeps working. An internet outage never restricts anything, and even in the most restricted licence state every record stays visible, printable and exportable, and the emergency department, medication administration and critical results keep working.
Who owns the data, and can we export it?
The hospital owns its data. A full export of every table and stored file is available to administrators in every licence state, and each patient’s own data can be exported for access and portability requests.
Integrations and compliance
Does Nabd support Egyptian e-invoicing?
Yes. Nabd produces ETA e-invoice and e-receipt documents and a submission queue. The live connection is configured with each hospital's own ETA credentials: registration, point-of-sale devices and the electronic signature. More in e-invoicing for Egyptian hospitals.
Does Nabd connect to insurers and TPAs?
Nabd is integration-ready; live connectors are connected per payer after an agreement. Today approvals and claims run through the payer’s usual channels with every exchange recorded, a FHIR R4 connector is built and tested against a test payer, Shafafiya and eClaimLink files are exported as XML, and MedNet, GlobeMed and NEXtCARE connectors wait for a signed agreement and specification.
What about NPHIES, ZATCA, Malaffi or NABIDH?
They are planned country packs, not available today. The FHIR R4 payer connector is shaped like NPHIES messaging but is not certified against NPHIES. Details per country: Saudi Arabia, United Arab Emirates.
Does it integrate with lab analysers and radiology systems?
Nabd offers a read-only FHIR R4 API, a results API for analyser middleware and a link to the PACS image viewer. An HL7 v2 interface engine, the on-site analyser agent and the DICOM Modality Worklist are on the development roadmap.
Is Nabd certified by GAHAR or under the data-protection law?
No. Nabd is built to support GAHAR accreditation workflows and the Personal Data Protection Law (PDPL 151/2020): incident reporting, critical results, the audit trail, consents, data-subject requests and a breach register. Accreditation is granted to the healthcare facility, not to software.
Implementation, migration and the demo
Can we move our data from the current system?
Yes: patients with their old file number, items, insurance payers, opening stock and opening balances, from Excel or CSV files, checked in full before anything is imported. Insurance cards, allergies and open invoices are planned for the next stage. See keeping patient history safe when changing systems.
How long does an implementation take?
It depends on the departments, the data and the training needed. We agree the scope and a written plan after the discovery session rather than promising a date before we know your hospital.
Who trains our staff?
The Flexcode Systems team, in separate sessions per role (reception, doctors, nurses, cashiers, lab, pharmacy, accounts) on the screens each role uses, followed by go-live support.
What does the demo show, and on which data?
A live session focused on the departments you choose, on fictional demo data. No real patient data is used. Request a demo.
See Nabd on sample data
A live demo focused on the departments that matter to your hospital.