Harmony — Executive Command Center Workspace Mockup

Filter

Kesiapan data: READYfield sudah ada, tinggal agregasi DERIVEdata ada, perlu logic perhitungan baru BUILDperlu model/field baru

Holding Overview

Tampilan utama owner. Menjawab: unit mana sehat, mana bermasalah, apakah target bulan ini masih mungkin tercapai.

RevenueDERIVE

Rp 48,2 M

▲ +6,1% vs bln lalu

Σ hmy.billing.document.total_amount

EBITDA marginBUILD

18,4%

▼ −1,3 pp vs target

revenue − cost · butuh costing.episode

Patient volumeREADY

31.480

▲ +4,0%

count hmy.encounter

BORDERIVE

71%

target 75%

admission ÷ facility.bed.count

AR daysDERIVE

▲ +7 hari

billing.amount_due + posted_at

Klaim pendingREADY

Rp 9,7 M

412 klaim

hmy.bpjs.claim state≠reconciled

Status Unit

BUILD scoring

RS Harmony Pusat

RS · Jakarta · 320 bed

›

RS Harmony Bekasi

RS · margin turun, BOR 54%

›

RS Harmony Bandung

klaim + AR memburuk

›

Klinik Harmony Depok

Klinik · Depok

›

Klik unit → drill-down ke command center anak perusahaan.

org: res.company + hmy.service.unit · warna = rule engine (baru)

Tren Revenue & Margin Holding

DERIVE

Revenue (Rp)EBITDA margin %

Revenue naik, margin melandai → tekanan biaya di 2 unit.

read_group billing per company per bulan

⚠ Alert Center

BUILD engine

Margin RS Bandung −5 pp

PIC: Dir. RS Bandung · sejak 3 hr

Klaim pending > limit (Rp 3,1 M)

PIC: Casemix · 28 klaim > 14 hr

AR aging > 90 hr naik 18%

PIC: Finance holding

BOR Bekasi turun ke 54%

PIC: Dir. RS Bekasi

KPI mutu merah 2 bln berturut

PIC: Komite Mutu

rule: threshold + trend + PIC mapping (baru)

Performance Command

Kontrol operasional: kunjungan, utilisasi, BOR/ALOS/TOI/BTO, antrean & waiting time.

Pertanyaan yang dijawab: Apakah kapasitas (poli, dokter, bed) terpakai optimal? Di mana antrean menumpuk? "Masalahnya operasional atau volume?"

Mix Kunjungan

READY

● RJ 58%

● RI 27%

● IGD 15%

hmy.encounter.encounter_type

BOR Holding

DERIVE

Σ admission days ÷ (bed × hari)

ALOS · TOI · BTO

DERIVE

3,8

ALOS (hr)

1,6

TOI (hr)

5,2

BTO (×)

admission_date / discharge_date + bed_count

Waiting Time & Antrean

DERIVE

24'

avg tunggu

386

antre aktif

4,1%

cancel

queue.ticket + call.log timestamp

Utilisasi Dokter & Poli (Top 5)

DERIVE

Poli Penyakit Dalam

92%

Poli Jantung

84%

Poli Bedah

71%

Poli Anak

58%

Poli Mata

41%

encounter group by practitioner_id / service_unit_id

Tren Volume per Unit (6 bln)

READY

PusatBekasiBandung ↓

read_group encounter per company per bulan

Revenue Command

Kontrol pendapatan: revenue per unit & service line, payer mix, klaim, target vs realisasi.

Pertanyaan yang dijawab: Dari mana revenue datang dan ke mana bocornya? "Apakah target bulan ini masih mungkin tercapai?"

Revenue per Unit

DERIVE

RS Pusat

19 M

RS Bekasi

13 M

RS Bandung

10 M

Klinik Depok

6 M

billing group by company_id

Revenue per Service Line

DERIVE

Rawat Inap

21 M

Bedah

11 M

Rawat Jalan

9 M

Penunjang

7 M

charge.event ↔ medical_service.service_domain

Payer Mix

READY

● BPJS 55%

● Asuransi 28%

● Umum 17%

billing.payer_id → hmy.payer.payer_type

Funnel Klaim BPJS

READY

Diajukan

1.240

Submitted

1.020

Reconciled

828

Rejected

112

hmy.bpjs.claim.state · eklaim_status

Target vs Realisasi

BUILD target

Revenue92% · Rp 48,2/52,5 M

Margin78%

Cash collection64%

Garis hitam = target. Perlu model target/budget holding (belum ada).

butuh model hmy.kpi.target / account.budget

Cost Command

Kontrol biaya: struktur biaya, rasio payroll/dokter/BMHP, cost per visit, margin per service line.

Pertanyaan yang dijawab: Di mana biaya naik abnormal dan menggerus margin? Sebagian besar butuh dibangun — integrasi payroll & costing episode belum lengkap.

Struktur Biaya Holding

BUILD

Payroll 41%Dokter 23%BMHP 19%Overhead 17%

butuh HR payroll + costing.rate.cost_pool

Cost Ratio (vs ambang)

BUILD

Payroll ratio41%

Doctor fee ratio23%

BMHP/obat19% ▲

cost ÷ revenue per pool (baru)

Cost per Visit / Admission

BUILD

Rp 312rb

per visit (RJ)

Rp 4,8 jt

per admission

costing.episode allocation (belum lengkap)

Margin per Service Line

BUILD

Service line	Revenue	Cost (est)	Margin	%
Rawat Inap	Rp 21,0 M	Rp 16,8 M	Rp 4,2 M	20%
Bedah	Rp 11,0 M	Rp 7,7 M	Rp 3,3 M	30%
Rawat Jalan	Rp 9,0 M	Rp 7,6 M	Rp 1,4 M	16%
Penunjang	Rp 7,0 M	Rp 6,8 M	Rp 0,2 M	3%

butuh costing.episode.margin per medical_service (baru)

KPI Command

Target holding: KPI owner, direktur RS, finance, operasional, mutu klinis — achievement & trend.

Revenue achievement

Margin achievement

Cash collection

Mutu & service

KPI Strategis Holding

BUILD model KPI

KPI	Owner	Target	Realisasi	Trend
Revenue growth YoY	Owner	+10%	+6,1%	↗
EBITDA margin	Finance	20%	18,4%	↘
BOR	Dir. RS	75%	71%	→
AR days	Finance	≤45	58	↗
Claim acceptance rate	Casemix	≥95%	91%	↘
Waiting time IGD	Dir. RS	≤15'	24'	↗
Patient satisfaction	Komite Mutu	≥90%	88%	→

butuh model hmy.kpi.definition + hmy.kpi.target + scheduled snapshot

Drill-down per Unit

Heatmap status semua unit lintas dimensi. Klik sel merah → halaman command center anak perusahaan.

Unit	Revenue	Margin	BOR	AR	Klaim	Waiting	Mutu	Status
RS Harmony Pusat	●	●	●	●	●	●	●	Sehat
RS Harmony Bekasi	●	●	●	●	●	●	●	Perhatian
RS Harmony Bandung	●	●	●	●	●	●	●	Kritis
Klinik Harmony Depok	●	●	–	●	●	●	●	Sehat

Hijau / sehatKuning / perhatianMerah / kritisN/A (klinik tanpa rawat inap)

matrix unit × KPI · skor warna = rule engine (baru)

Ringkasan Kesiapan Data — apa yang siap vs perlu dibangun

Berdasarkan inventaris model existing di codebase Harmony18 (addons_fin, addons_flow, addons_core).

Komponen	Status	Sumber data existing	Yang perlu dibangun
Patient volume, mix RJ/RI/IGD	READY	hmy.encounter (encounter_type, state, started_at, company)	—
Klaim BPJS & funnel	READY	hmy.bpjs.claim (state, eklaim_status, total_claim_amount)	—
Payer mix	READY	hmy.billing.document.payer_id → hmy.payer.payer_type	—
Cash collection	READY	hmy.cashier.payment (amount, state, payment_date)	—
Revenue per unit / service line	DERIVE	hmy.billing.document.total_amount, hmy.charge.event	read_group per company / medical_service.service_domain
BOR / ALOS / TOI / BTO	DERIVE	hmy.admission (dates) + hmy.facility.bed.bed_count	fungsi okupansi bed-day per periode
AR days & aging	DERIVE	billing.amount_due + posted_at	bucket aging + DSO calc
Waiting time & cancellation	DERIVE	hmy.queue.ticket + hmy.queue.call.log	delta call_log timestamp → avg wait
EBITDA / margin / cost ratio	BUILD	hmy.costing.rate (parsial)	integrasi HR payroll + costing.episode allocation
Target vs realisasi / KPI	BUILD	hmy.dashboard.widget (struktur saja)	model hmy.kpi.definition + hmy.kpi.target + snapshot
Status warna unit & Alert Center	BUILD	—	rule/threshold engine + PIC mapping + notifikasi

READY = bisa langsung agregasi · DERIVE = data ada, perlu method perhitungan · BUILD = perlu model/field baru. Fondasi hmy_dashboard_core (board + widget + metric_key) sudah ada dan bisa diperluas untuk menampung command center ini sebagai modul hmy_dashboard_executive.