🛡 محمي لدى الهيئة السعودية للملكية الفكرية · حق مؤلف 26-12-98061022 · علامة تجارية TM-01-00-39860-26
Hospital Coordination Layer · رافق

Every request gets an owner,
a clock, and a way up

لكل طلبٍ بين الأقسام مالكٌ ووقتٌ مستهدف وتصعيدٌ تلقائي

RAFEQ is an operational coordination layer for hospitals. Requests between departments never get lost, and delays surface — and escalate — before they ever reach the patient.

Get in touch
Read-only, zero disruptionBuilt on the national FHIR standardOutside SaMD — deploys fast
🔒 Live interactive demo is by private session — glimpses below · العرض الحي بحساب خاص حفاظاً على الملكية
RAFEQ Executive Overview
RAFEQ — Executive overview: on-time completion, cost of delay, and beds freed, in one view.
The film · الفيلم

The medical decision takes minutes. The coordination takes hours.

Thirty seconds on the problem RAFEQ was built for.
القرار الطبي يُتخذ في دقائق، أما التنسيق فيأخذ ساعات.

RAFEQ — an orchestration layer for hospital operations.
Key modules

Every capability a hospital needs to keep requests moving

One operational layer across departments — tracking, escalation, boards, and standards-aligned integration.

◉

Request tracking

Every inter-department request carries a named owner, an automatic target time, and a clear status — nothing falls through.

▲

Escalation ladder

Automatic, time-driven escalation (L1→L4). Thresholds are a share of each request's own target — a 30-minute request and a 48-hour one, alike.

▦

Bed & discharge boards

Case console, discharge board, and bed board in one place — a live view of flow across the whole floor.

↔

Read-only FHIR integration

Speaks the language of NPHIES. Build once, connect to all — no rebuilding an integration at every site.

📈

Operational analytics

Request turnaround, length-of-stay impact, and bed turnover — the numbers leadership acts on.

🛡

Compliance view

A standards-aligned, auditable record designed to complement national systems, not compete with them.

See it in action

A live view of flow across the whole floor

Real screens from RAFEQ — discharge, orders, and escalation, department by department.

Discharge board
Discharge board — every pending step across pharmacy, transport, and affairs, before the bed clears.
Order list
Order list — every request with elapsed time against its own target, and its escalation level.
The value

Capacity added — without building a single new bed

By shortening length of stay and raising bed turnover, RAFEQ returns the hospital many times its cost. Figures are conservative and assumption-based.

~33,600SAR saved per bed, per year
~3.4MSAR per year for a 100-bed hospital
13×Return — RAFEQ pays for itself many times over
Why RAFEQ is different

Four answers to the four questions every hospital asks

Measures the request, not the patient. It tracks the workflow itself — seeing the bottleneck where it happens, without feeling like surveillance of staff.
Read-only, zero disruption. It runs on top of your systems without touching them — no risk to data or workflow.
Built on the national standard (FHIR). It speaks the language of NPHIES. Build once, connect to all.
Operational, outside SaMD. It does not diagnose or treat, so it avoids heavy regulatory approval and deploys quickly.
Built from the inside

Founded by someone who lived the problem from the inside — for 24 years

RAFEQ was built by Bandar Alasmari — 24 years inside Saudi hospitals in inter-department operations: bed management, case management, and transplant coordination. He cut average length of stay from 11 to 7 days through structured coordination, watched it collapse when it depended on people, and built RAFEQ so it would last in structure.

Working product · Copyright registered with SAIP