Healthcare
NabdA Connected Patient Access Platform
A concept platform that streamlines the patient journey from booking to the clinic door across multiple branches, integrated through HL7 FHIR.
01
The challenge
In multi-branch clinic groups the phone remains the main booking channel, and physicians’ schedules are spread across different systems and sites. Patients struggle to find the earliest available slot; management struggles to see real capacity.
The effects compound: no-shows who never cancel, wasting slots other patients needed; crowded waiting rooms; and insurance eligibility checked at the front desk rather than before the visit, so patients discover surprises too late.
All of this runs on some of the most sensitive data there is. Any solution must integrate with the existing hospital information system rather than replace it, respect the PDPL and the requirements of NPHIES, the national health insurance exchange, and keep a complete trail of every access to a patient record.
02
Proposed solution
Nabd centers on a scheduling engine that manages resources, not just physicians: doctor, room and equipment together, with flexible slot templates by specialty and visit type. It surfaces the earliest slot across all branches and runs a smart waitlist that automatically offers canceled slots to the next patients in line.
Integration runs through an HL7 FHIR R4 layer exposing Patient, Practitioner, Schedule, Slot and Appointment resources in a standard shape, with an interface engine translating HL7 v2 messages for legacy systems. The platform stays a patient-access layer on top of the existing HIS, not a replacement for it.
The journey also covers pre-visit insurance eligibility checks through flows designed to align with NPHIES, self check-in from a phone or a lobby kiosk, a virtual queue that tells patients when their turn is near, and telehealth visits for follow-ups.
03
Design rationale
Patients of every age use the platform, so it is designed to be understood at a glance: large touch targets, plain language instead of clinical jargon where possible, and full support for text scaling and screen readers to WCAG 2.2 AA. A head of household can book for dependents from a single account.
Privacy is visible in the design: lock-screen notifications never reveal the specialty or reason for a visit, consent screens use clear language rather than legal fog, and patients can see who has accessed their data.
Front-desk staff, by contrast, get a high-density console suited to experienced users: a day view across all doctors and rooms, keyboard shortcuts for rapid booking, and arrival states that pair color with text. Both surfaces share one design system in dark and light themes.
04
Example architecture
An illustrative layering of the system, from the screens people use down to the infrastructure. A starting point we would validate during discovery, not a final design.
Layer 01
Experience
- Flutter patient app with family profiles
- Next.js web booking
- Reception & scheduling console
- Lobby check-in kiosk
Layer 02
Integration
- HL7 FHIR R4 facade (HAPI FHIR)
- HL7 v2 interface engine for legacy HIS
- Insurance eligibility adapter
- SMS, WhatsApp & push notifications
Layer 03
Domain services
- Resource-based scheduling engine
- Smart waitlist & slot backfill
- Virtual queue & check-in
- Telehealth sessions over WebRTC
Layer 04
Security & privacy
- Consent management
- Field-level encryption for health data
- Access audit with break-glass procedure
- Keycloak SSO & MFA for staff
Layer 05
Data & infrastructure
- PostgreSQL
- Redis slot locking
- Kubernetes in an in-Kingdom region
- OpenTelemetry observability
05
Relevant technologies
Tools we would consider for this concept. They indicate engineering ecosystems, not partnerships or certifications.
- Flutter
- Next.js
- TypeScript
- Kotlin
- Spring Boot
- HL7 FHIR R4
- HAPI FHIR
- Mirth Connect
- PostgreSQL
- Redis
- WebRTC
- Keycloak
- Kubernetes
06
Key features
Earliest slot across every branch
Unified search across doctors and branches that surfaces the earliest suitable slot by specialty and location.
Smart waitlist
Canceled slots automatically offered to waiting patients, with quick confirmation.
Pre-visit eligibility checks
Coverage and eligibility known before the visit, not at the front desk.
Check-in and virtual queue
Self check-in by phone or kiosk, with a heads-up as your turn approaches to ease waiting-room crowding.
FHIR-based integration
Standards-based data exchange with the existing HIS, without replacing it.
Telehealth visits
Secure video follow-ups within the same journey.
07
Potential benefits
These are design goals the solution is built toward, not measured results.
Designed to reduce wasted slots through reminders and backfilling
Less crowded waiting rooms
Fewer insurance surprises thanks to pre-visit checks
A clearer view of capacity across branches
Stronger protection of health data with a complete audit trail
Related services & industry
Industry
Patient-centered digital health platforms, from booking and telehealth to interoperable clinical data.
Services involved
Native and cross-platform iOS and Android apps with polished Arabic UX, steady performance and a clear path to launch.
Bilingual corporate sites, online stores and web platforms engineered for speed, security and scale.
REST and GraphQL APIs, payments, webhooks, and event-driven integrations that make separate systems work as one.
Security built into architecture, code, and delivery pipelines from day one, not bolted on after launch.
Research-led product design, from user journeys to production-ready design systems for complex enterprise interfaces.
This is a concept project created by AMA GROUP to demonstrate our approach. It is not a client engagement: the interface uses sample data, and no client, logo or result is implied.
Have a similar challenge?
Share the problem you are facing. We will come back with a clear approach, scope and next steps.