Hospital Coordination Layer · رافق

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

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

RAFEQ is an orchestration 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 disruptionReady for national standards (FHIR)Non-clinical by design
🔒 Live demo by private session · glimpses below · العرض الحي بحساب خاص حفاظاً على الملكية
RAFEQ operations console
RAFEQ — Operations console: every open request, its owner, countdown and escalation. Synthetic data.
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.
How escalation works · كيف يعمل التصعيد

Not a screen of alerts. A work screen that points to where requests are late.

The delay climbs one step at a time, and each department solves its own first.

STEP 1 · RECEIVE

The department accepts the request

Within a set time after it is issued.

STEP 2 · THE TEAM

Supervisor and staff deliver it

If it runs late, the team has time to fix it inside the department.

STEP 3 · THE HEAD

The department head steps in

Only when the request is still late.

STEP 4 · CASE MANAGEMENT

A case that needs intervention

Central case management sees only what the department could not solve.

Doctors, nurses and paramedics keep working as they do, with no follow-up calls. RAFEQ follows.

Key modules

Every capability a hospital needs to keep requests moving

One layer across departments — tracking, escalation, boards, and reading from the systems you already run.

◉

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.

↔

Reads from your systems

Read-only access to the systems you already run. Ready for national exchange standards (FHIR / NPHIES) as they roll out.

📈

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. Estimates, not results — assumptions available on request.

~37,000SAR estimated saving per bed, per year
~7.4MSAR per year for a 200-bed hospital
~15×Estimated return on the subscription
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.
Ready for national standards. Designed for FHIR and NPHIES, so connecting gets cheaper as the national exchange grows.
Non-clinical by design. It does not diagnose, treat or recommend care. It tracks the work around clinical decisions, so it is light to deploy.
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
🛡 الهيئة السعودية للملكية الفكرية · حق مؤلف 26-12-98061022 · علامة تجارية مقبولة ومنشورة TM-01-00-39860-26