Skip to main content

Requirements

Before setting up Ward, ensure your facility meets these requirements.

Device Requirements​

Ward requires an active internet connection. Observations and vitals can be documented offline and sync when connectivity returns.

Mobile Devices (iOS/Android)​

  • iOS: iPhone or iPad running iOS 16.0 or later
  • Android: Device running Android 12 (API level 31) or later
  • Camera: Required for QR code scanning during EOC rounds
  • Biometrics: Face ID, Touch ID, or device passcode for session lock (recommended)
  • Location services: Optional, used for manual proximity override logging
Device Security

Ward performs security checks on launch. Rooted (Android) or jailbroken (iOS) devices will display a security warning banner. The app remains functional, but users should be aware of increased risk on compromised devices.

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.)
    • An authenticator app (Google Authenticator, Microsoft Authenticator, etc.) for MFA if assigned to Charge Nurse or higher role

Optional: Sensor Hardware​

For automated proximity verification and elopement detection:

  • Sensor Hub: One per unit — processes wristband data and communicates with Ward
  • Patient Wristbands: BLE wristbands assigned to patients for proximity verification and elopement detection
  • Fixed BLE Receivers (exits): Gateways at unit exits and facility boundaries for elopement detection
  • Fixed BLE Receivers (room doorways): Optional — 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