Hospital information system (HIS)

A hospital information system built around one patient record

Nabd HIS keeps every clinical fact about a patient in one place, whichever department recorded it: registration, visits, orders and results, medications, surgeries, nursing and billing. Clinicians work in Arabic or English, safety checks run inside the workflow, and every access to the record is audited.

A patient chart in Nabd with allergies, problems and insurance, and tabs for visits, orders, medications and billing
Unified patient chart
  • One record per patient

    One medical record number across all facilities, duplicate detection and audited merge.

  • Unified chart

    A tab per department: visits, orders and results, medications, surgeries and billing.

  • Safety checks in the workflow

    Allergy and drug-class, interaction, duplicate-therapy and high-alert checks when prescribing.

  • Critical results with read-back

    The ordering doctor is notified at once, with acknowledgement and escalation.

  • Standard data exchange

    A read-only FHIR R4 API with LOINC, ICD-10 and ATC codes, every read audited.

One patient, one record

Registration starts from the Egyptian national ID: birth date, sex and governorate are read from it, and the mobile number is validated. Search works on Arabic names with the usual spelling variations normalised, on the file number, the mobile number or the national ID. Possible duplicates are flagged before a new file is opened, and merging two files is a controlled, audited action. Each patient keeps one medical record number across every facility of the group.

The unified chart

Allergies, problems, alerts and insurance coverages sit on the patient banner, visible from every screen. Below it, the chart has a tab per department, so a doctor opening a file sees previous visits, orders and their results, current medications, surgeries and the billing summary without switching systems.

Orders and results that reach the right person

Lab and radiology orders, order sets and e-prescriptions are entered once and appear in the receiving department immediately. In the laboratory, orders are grouped into tubes and barcode labels print at collection; results are checked against age- and sex-specific ranges and released by a specialist. Radiology reports are written from templates, signed off and linked to the hospital’s PACS viewer. See how this works in lab orders that reach the lab instantly.

Safety checks inside the workflow

Every department on the same record

Emergency with five-level ESI triage and a live board, inpatient wards with a bed board and nursing station, operating theatres with schedules and anaesthesia records, the blood bank, pharmacy and quality all write to the same patient record. A patient moving from the emergency department to a ward to the theatre never gets a second file.

Standards and data exchange

Nabd exposes a read-only FHIR R4 API for patients, practitioners, encounters, observations (vital signs and lab results), conditions, allergies, medication requests, service requests, diagnostic reports and coverages, coded with LOINC, ICD-10 and ATC where configured. Integration keys hold only the read permission they need, can be bound to one facility, and every read is written to the audit trail.

In development, not available yet: an HL7 v2 interface engine, the on-site lab analyser agent and the DICOM Modality Worklist. Nabd links to the PACS viewer but does not store images.

Privacy by design

A consent registry, data-subject requests with due dates, a patient data export, and a breach register with the 72-hour clock are part of the administration screens. Together with the audit trail and the patient access report they are built to support the Egyptian Personal Data Protection Law (PDPL 151/2020) and GAHAR information-management standards.

Frequently asked questions

Is Nabd an EMR or a full HIS?

Both. The electronic medical record (notes, diagnoses, orders, prescriptions) is one part of Nabd HIS, which also covers emergency, wards, theatres, lab, radiology, pharmacy, billing and accounting.

Does Nabd support HL7 or FHIR?

Today Nabd offers a read-only FHIR R4 API. An HL7 v2 interface engine (admission and result messages) is on the development roadmap.

Does it connect to our PACS?

Radiology studies link to the hospital’s PACS viewer (for example Orthanc and OHIF). Nabd does not store the images; the DICOM worklist is in development.

Is Nabd GAHAR-certified?

No software is GAHAR-accredited; accreditation is granted to the facility. Nabd is built to support GAHAR workflows such as critical results, incident reporting and the audit trail.

Do clinicians have to work in English?

No. The interface is right-to-left Arabic by default and each user can switch to English. Patient names are recorded in both languages.

Walk through a patient journey in Nabd

From registration to discharge, on fictional data, with your clinical team.