Bikin SIMRS yang Tahan Banting: Laravel Queue, Retry, dan Status Pending

🔀 Read in English 🇬🇧

Selamat Datang di Hajriah Fajar: Hidup Sehat & Cerdas di Era Digital

Bikin SIMRS yang Tahan Banting: Laravel Queue, Retry, dan Status Pending

Kadang sistem SIMRS tuh kayak manusia kelelahan: pas disuruh banyak hal sekaligus, dia malah nge-freeze. Dokter udah klik, resepnnya harus masuk, SEP harus dikirim, antrian harus dibuat. Tapi sistem kita bilang: “Saya lelah, Bang.”

Nah, ini dia kenapa kita butuh sistem yang gak manja. Kita butuh SIMRS yang bisa napas pelan, mikir satu-satu, dan punya tenaga buat nyoba lagi kalau gagal. Di sinilah Laravel Queue dan Redis masuk.

Apa Itu Queue? Bayangin Warteg

Pernah ke warteg rame-rame? Kamu bisa bilang ke penjaganya: “Bang, pesen nasi rendang, telur dadar, sambal ijo, es teh.” Tapi kan gak semua langsung dikerjain bareng. Ada antrian. Nah, queue di Laravel tuh semacam “pesanan” yang ditaruh dalam urutan, dikerjakan satu per satu, tanpa bikin kamu nunggu di depan warteg (eh… sistem).

Kenapa Laravel Queue + Redis?

• Laravel Queue: Mesin antriannya. Bisa antri banyak job, kasih retry, kasih status.
• Redis: Tempat naro antriannya. Ringan, cepat, gak ribet.

Bayangkan Laravel Queue kayak kasir modern. Redis itu kayak tray makanan. Laravel naruh pesanan ke Redis, Redis kasih satu-satu ke dapur (worker).

Kalau Gagal Gimana?

Tenang. Laravel bisa bilang ke worker: “Kalau gagal, coba lagi ya... maksimal 5 kali.” Dan bisa disetel supaya nyoba tiap 10 detik, tiap menit, atau besok pagi sekalian. Yang penting user gak kena error di layar.

Status: Pending, Gagal, Sukses

Setiap job di queue dikasih status. Biar admin bisa lihat:

Job	Status	Keterangan
Input SEP	pending	Belum diproses, BPJS lambat
Input Resep	sukses	Farmasi udah terima
Permintaan Radiologi	gagal	PACS server mati

Status ini bisa ditaruh di tabel tersendiri atau di kolom status dalam tabel utama.

Laravel Horizon (Opsional Tapi Mantap)

Kalau kamu pengen dashboard real-time buat lihat antrian queue, Laravel Horizon bisa bantu. Dia kasih visual: berapa job pending, berapa retry, berapa gagal. Cocok buat tim IT rumah sakit yang pengen “megang kendali”.

📊 Studi Pendukung

Menurut IEEE Xplore, penggunaan job queue di aplikasi klinis meningkatkan respons time dan fault tolerance hingga 60%. Bayangkan, pasien lebih aman, dokter lebih nyaman.

Alur Simpan Modern SIMRS (Simplified)

1. Dokter klik SIMPAN → hanya data SOAP yang langsung masuk DB
2. Resep, SEP, permintaan penunjang masuk ke Redis Queue
3. Worker ambil satu-satu, kirim ke sistem masing-masing
4. Status job dicatat → sukses/gagal/pending
5. Admin bisa cek dan retry kalau perlu

Penutup: Biar Sistem Gak Baperan

SIMRS bukan cuma soal bikin aplikasi. Tapi soal bikin sistem yang ngerti kalau hidup itu gak selalu lancar. Kadang BPJS lemot. Kadang jaringan putus. Kadang lab down. Kalau semuanya dibebankan ke satu klik “simpan”... ya jelas patah. Tapi dengan Laravel Queue, Redis, dan sedikit kasih sayang dari admin IT, sistem kita bisa lebih tahan banting, dan gak gampang nangis di tengah shift dokter.

---

Welcome to Hajriah Fajar: Living Smart & Healthy in the Digital Age

Making SIMRS Resilient: Laravel Queue, Retry, and Pending Status

Sometimes SIMRS feels like an overworked intern — you ask too much, and it just freezes. Doctors click save. The system is supposed to handle prescriptions, SEP requests, queues, labs. But it says: “Nope, I’m done.”

Queue = Like a Canteen

Ever ordered 5 dishes at once at a street food stall? They won’t serve them all at once. They line up your order. That’s what a queue system does. It handles jobs one by one, without keeping you waiting.

Laravel Queue + Redis = Power Duo

• Laravel Queue: The ordering system, handles retries and status.
• Redis: The queue tray. Fast, lightweight, reliable.

What if a Job Fails?

Laravel can retry. 5 times. 10 times. Every 10 seconds or next morning. No ugly error for the doctor. Just retry in the background.

Track Everything: Pending, Failed, Success

Each job comes with a status log, so admins can see what’s working and what’s not.

Job	Status	Info
SEP submission	pending	Waiting for BPJS
Prescription	success	Sent to pharmacy
Radiology order	failed	PACS offline

Laravel Horizon: For Real-Time Control

Want a visual dashboard for queue jobs? Use Laravel Horizon. See pending, failed, successful jobs — in real time. It’s like a cockpit for your hospital IT team.

📊 Study Says...

A IEEE paper reported queue-backed systems in clinical settings saw a 60% boost in fault tolerance and speed.

Modern SIMRS Save Flow (Simplified)

1. SOAP → saved immediately to DB
2. Others → sent to Redis Queue
3. Workers pick & execute
4. Status updated
5. Admins monitor and retry

Closing: Build a SIMRS That Doesn't Panic

A good system isn't the one that never fails. It’s the one that knows how to recover, retry, and move on — just like a good nurse in a hectic shift. With Laravel Queue, Redis, and smart status logs, your SIMRS doesn’t just survive — it grows stronger.