Hoopoe is not a stack of independent modules. It is a connected system where one click at reception ripples through booking, inventory, accounting, payroll, marketing, compliance, and reporting. Understanding the ripple is the difference between using the software and using it well. This article traces seven everyday actions and shows what fires in which module, and why.

Why this matters#

If you do not see the ripple, you compensate with manual work. Reception re-enters data the system already has, the accountant rebuilds reports the system can produce, the manager second-guesses numbers because they do not trust where they came from. When you see the ripple, the cost of doing things right drops to almost zero and the cost of doing them wrong becomes visible.

Action 1: reception checks a patient in#

What clicks happen#

Reception opens the session, clicks Check-in (or the patient self-checks-in on the tablet).

What ripples#

Booking: session status flips from Confirmed to Arrived (the locked transition). Arrival timestamp recorded.
Check-in gates: four checks run server-side (unpaid balance, missing consent, wrong branch, no eligible package credit). Any failure blocks the transition and surfaces a reason.
Provider queue: the patient now appears on the provider's My Panel queue.
Package credits: if booked against a package, the credit is reserved at this moment.
NABIDH (UAE): ADT A04 (register) transmits if not yet sent and the tenant is onboarded to NABIDH. Riayati (federal) and Malaffi (Abu Dhabi) transport is on the roadmap — for those emirates, plan manual MoH portal reporting.
Reports: arrival contributes to "waiting time" KPI (time from arrival to first provider action).
Notifications: provider gets in-app + push that their next patient has arrived.

Action 2: provider submits the service report#

What clicks happen#

Provider in My Panel → Medical record → Service report → fills service items, materials used → Submit.

What ripples#

Booking: session flips Arrived → Done. Locked transition.
Medical record: per-session note locks. Future edits are addenda, not in-place.
Inventory: BOM consumption fires. Each material used decrements stock, EXACT precision on quantities.
Accounting (revenue): if pay-per-session, an invoice is queued by Celery and lands within seconds — not the same instant. If the queued task fails (rare; usually a price-list mismatch), the session is still Done but no invoice appears. Cross-check Reports → Sales against Accounting → Journal entries to spot misses. If package-credit, deferred revenue releases to recognised revenue at the per-