Core concepts
The building blocks of EnaBed: buildings, floors, units, rooms, beds, and occupancy status.
Last updated on
Core concepts
EnaBed models every physical care location as a hierarchy and every sleeping surface as a bed with a live occupancy status.
Facility hierarchy
Building
└── Floor
└── Unit (ward / department zone)
└── Room
└── Bed| Level | Example | Purpose |
|---|---|---|
| Building | North Tower | Site or campus block |
| Floor | Level 3 | Vertical slice within a building |
| Unit | ICU, Ward 4B | Clinical or operational zone |
| Room | Room 312 | Enclosed care space |
| Bed | Bed A | Assignable sleeping/treatment surface |
Each level supports ordering, search, CSV export, and role-scoped permissions.
Bed occupancy status
Every bed carries a status that bed managers update from the admin panel:
- Available — ready for admission
- Occupied — patient assigned
- Reserved — held for incoming transfer
- Cleaning — turnover in progress
- Maintenance — out of service
- Blocked — administratively unavailable
Status changes propagate via live updates when the plan includes that feature.
Bed search
Bed search lets authorized users filter beds across the hierarchy by status, department, isolation requirements, equipment tags, and free-text query — without walking the wards.
Departments and quotas
Organizations define departments for reporting and access control. Subscription plan limits cap buildings, units, rooms, beds, and team members; the admin panel surfaces quota usage inline.
Audit and security
Every create, update, delete, and reorder operation is recorded in an append-only HMAC-SHA256 audit chain. PostgreSQL row-level security isolates tenant data at the database layer.