NEXUSNOVA|v1.0|ONLINE
IST--:--
45m → 5m · +12% occupancy
turnover +22% · ALOS -0.8d · central board ward/ICU
Bed allocation by phone/WhatsApp caps occupancy. HospitalOS syncs ADT via HL7/FHIR, drives a real-time ward/ICU board, and writes back to your HIS — no replacement, parallel run.
> _cost: 20–30 beds idle/day at 150 beds · transfers 38m · occupancy blind
> _hospital_invariants
FHIR/HL7 layer on your HIS — zero downtime. Every ADT event is a FHIR resource, not a spreadsheet row.
01 · HL7 ADT ingest (A01/A03/A08)
HIS adapter listens to ADT feed and mirrors to FHIR Encounter + Location. No HIS replacement.
> HL7v2 ADT → FHIR Encounter
02 · Real-time bed board (ward/ICU)
Digital board by ward, floor, ICU. Occupancy, cleans, and ALOS live — chain view if multi-site.
> FHIR Location / Schedule
03 · AI bed allocator
Rules + AI suggest ward/ICU by acuity, isolation, and TAT. Nurse approves in 1 tap — phone queue gone.
> FHIR Task
04 · HIS write-back + dashboards
Allocation writes back to HIS ADT. Occupancy, turnover, and ALOS dashboards auto-update.
> FHIR Encounter write-back
ADT is the trigger. Lab & pharmacy are the downstream handshakes — embedded, not standalone.
Admission → LIS order FHIR Task. Abnormal recall 46%→91% via FHIR-driven alerts.
Bed ready ↔ pharmacy handshake blocks discharge until meds cleared — visible on board.
Discharge → bed status 'cleaning' → ready. Turnover +22% from measured gaps.
> ABDM M1-M3 aware · HL7v2 + FHIR R4 · on-prem/VPC adapter
Tech: FHIR Encounter, Location, Schedule, Task · HL7v2 ADT · FHIR R4 · ABDM M1-M3 · HIS write-back API · 99.9% SLA · India residency · RBAC + audit trails · NABH/NABL mapped in discovery
Hospital — 150 beds
Multi-specialty hospital with 6-8h discharge TAT and bed allocation by phone. Needed ADT automation + HIS sync.
Discharge 6.2h→2.1h, bed turnover +22%, occupancy +11%.
Hospital Chain — 3 sites
Super-specialty chain losing referrals between sites and lacking central occupancy view.
Referral leakage -35%, central occupancy visible, ALOS -0.8 days.
Yes — ICU / HDU / isolation rules are configured during discovery (1–2w). The allocator respects acuity + isolation constraints and writes the final assignment to HIS via FHIR.
No. It is a FHIR/HL7 layer. HIS remains source of truth; HospitalOS mirrors ADT and writes back approved allocations. Parallel run — zero admission downtime.
Yes — Chain case: centralized ADT + referral network across 3 sites gave central occupancy, ALOS -0.8d, and leakage -35%.
Parallel run with no downtime. Discovery 1–2w, phased 3–6w, SOP handover and 99.9% SLA.