Requirements
Before setting up Ward, ensure your facility meets these requirements.
Network Requirements
- Internet connectivity - Ward requires an active internet connection for all features
- Firewall access - Outbound HTTPS (port 443) to Ward's cloud services
- WebSocket support - Required for real-time dashboard updates
Device Requirements
Mobile Devices (iOS/Android)
- iOS: iPhone or iPad running iOS 15.0 or later
- Android: Device running Android 10 (API level 29) or later
- Camera: Required for QR code scanning during EOC rounds
- Location services: Optional, used for manual proximity override logging
Web Access
- Browsers: Chrome, Safari, Firefox, or Edge (latest 2 versions)
- Screen resolution: Minimum 1024x768, recommended 1280x800 or higher
Staff Requirements
- Each staff member needs:
- A unique email address for their account
- Assignment to at least one unit
- A role designation (Staff, Charge Nurse, Unit Manager, etc.)
Optional: Sensor Hardware
For automated proximity verification, fall detection, and elopement prevention:
- Sensor Hub: Raspberry Pi 4, one per unit — processes wristband data and communicates with Ward
- Patient Wristbands: BLE wristbands (Minew B7) assigned to patients for proximity, fall detection, and elopement
- Fixed BLE Receivers (exits): Minew MG4 BLE gateways at unit exits and facility boundaries for elopement detection
- Fixed BLE Receivers (room doorways): Optional — Minew MG4 gateways at room doorways to enable room-level geofencing and presence confirmation
Without sensors, staff can use manual proximity override with reason documentation.
Optional: EMR Integration
For EMR connectivity:
- FHIR R4 or STU3 endpoint for observation/vitals sync
- HL7 v2.4/2.5 capability for ADT messages (patient census)
- OAuth2 client credentials for API authentication
- Network access from Ward to your EMR system
Contact your EMR vendor or IT team to obtain:
- FHIR base URL and auth URL
- Client ID and client secret
- Required scopes for read/write access