PSG Portal

Patient Safety Grid · Device 1 Pilot

Draft v3
Sep 2026

Discovery 25 Aug - 30 Sep 2026 · PS1 starts 15 Oct

DISCOVERY

PRE-PILOT

BANDING

GATE

25 Aug - 30 Sep PS1-PS5 · 15 Oct - 23 Dec ~15 Dec - 11 Jan ~20 Jan

Where are we?

Discovery phase — A2Z completing hardware research and component selection. Pilot design doc, engagement tracker, and timeline delivered as drafts. Awaiting feedback and date confirmation before PS1 sprint begins 15 Oct.

8 milestones 62 deliverables 7 sprints ~20 Jan gate

What's next?

HW platform locked

A2Z · PS1 · 28 Oct

Pilot design signed off

A2Z + AyurVAID · PS1 · 28 Oct

Round 1 built and tested

A2Z · PS3 · 25 Nov

What we need from AyurVAID

Review and sign off pilot design doc

A2Z + AyurVAID · By 28 Oct (M2)

Confirm pilot dates — banding start (~15 Dec), go/no-go (~20 Jan)

AyurVAID · Before PS1 starts (15 Oct)

Ward access for assessment — floor plans, beacon placement survey

AyurVAID ops · Two weeks before pilot start

Designate 3-5 nurses for usability validation session

AyurVAID · PS2-PS3 (Nov)

Patient consent protocol — admission workflow, consent forms, family app opt-in

AyurVAID legal/clinical · Before banding (~15 Dec)

MOU sign-off — commercial terms for pilot

AyurVAID + A2Z · PS4 (9 Dec)

Staff for training — 1-hour training sessions for ward nurses

AyurVAID nursing lead · PS5 (late Dec)

Explore

Pilot Overview

What, why, capabilities

Execution

Sprints, milestones, deliverables

Updates

Status, risks, decisions

Commercials

MOU, production

Pilot Design

Scope, architecture, success criteria, and deployment approach for the AyurVAID pilot.

Pilot Objectives

OBJ-1

Demonstrate the functional requirements

Validate the 8 demonstrated capabilities + heart rate in real ward conditions.

OBJ-2

Fall detection ≥98%

False negatives treated as critical.

OBJ-3

Establish false alarm baseline

Set a real-world false alarm threshold from pilot data.

OBJ-4

Verify hardware reliability

Battery life, uptime, failure rate under continuous ward use.

OBJ-5

Validate sense-reach-care workflow

End-to-end workflow with nursing staff.

OBJ-6

Patient comfort and wear compliance

Confirm comfort over the full pilot duration.

OBJ-7

Support and maintenance operations

Test device lifecycle, spares, escalation.

OBJ-8

Go/no-go dataset

Gather a clear dataset for the AyurVAID executive sponsor.

System Components

Wearable bandCustom ESP32-S3 · IMU/accelerometer · Wi-Fi + BLE · no display

Nurse consoleReal-time dashboard · patient status · alerts · zone map

Family appPatient status for families · opt-in via consent

Zone listenersBLE receivers in rooms, bathrooms, corridors, exits

ServerVirtual private server · zone engine · alert routing · all data on-premise

Functional Requirements — Detail

FR-1

Fitment Detection Setup

Confirms band is on patient's wrist within 15 seconds of being fastened. IMU/accelerometer detects skin contact and orientation.

Success: device pairs and reports within 15 seconds of fitment.

FR-2

Hard Fall Detection Critical

IMU detects impact signature and orientation change consistent with a fall. Triggers immediate alert to nurse console with patient identity and zone.

Success: ≥98% detection rate; zero false negatives treated as critical.

FR-3

Slow Fall Detection Critical

Slower, softer descent detected by IMU. Alerts nurse console for welfare check.

Success: included in ≥98% detection rate.

FR-4

Consecutive Falls Critical

Multiple falls in quick succession with no acknowledgement detected and alerted.

Success: each fall in sequence generates a separate alert.

FR-5

Geo-fencing High

Patient crosses ward-exit zone — wandering / flight-risk scenario detected via Wi-Fi/BLE beacons.

Success: alert fires when patient exits geofenced zone.

FR-6

Band Removal Detection High

Detects band removed from wrist within 15 seconds. Alerts nurse console for unscheduled removals. Scheduled removal during Ayurvedic therapies follows agreed protocol.

Success: alert fires within 15 seconds of band removal.

FR-7

SOS Button Critical

Recessed physical button on band. Patient presses for help; haptic confirmation on band, immediate alert on nurse console.

Success: alert fires within 5 seconds of button press.

FR-8

Dwell Time / Location Medium

Patient stays in a zone (e.g. bathroom) longer than expected. Room-level positioning via BLE listeners.

Success: configurable threshold; alert fires when exceeded.

FR-9

Heart Rate Monitoring High V2

Optical PPG sensor on board. Hardware present in pilot devices; software and clinical validation deferred to V2.

Success: heart rate logged continuously; anomaly alerts configurable.

Pilot Scope

In Scope (V1)

FR-1 through FR-8 — all IMU and zone-tracking capabilities

5 wards at AyurVAID · 40 beds · ~20 patients banded (~50% occupancy)

Nurse console for real-time monitoring and alerts

Family app with consent-based opt-in

Zone listeners in rooms, bathrooms, corridors, exits

Band removal protocol for Ayurvedic therapies

Out of Scope (V2)

FR-9 heart rate / SpO₂ clinical readings

Multi-hospital deployment

Success Criteria Go / No-Go

Measured during banding period (~15 Dec to ~11 Jan). Reviewed at go/no-go gate ~20 Jan 2027.

FR demonstrationAll 9 FRs (FR-1 to FR-9) validated with real patients

Fall detection rate≥98% of real falls detected; false negatives = critical

Alert latency≤5 seconds from event to alert on console

Device uptime≥95% uptime per device across pilot duration

Battery lifeTarget set after Round 1 internal testing

Patient safetyZero adverse events attributable to the device

Banding window~4 weeks banding, go/no-go by ~20 Jan 2027

Deployment Approach

Round 15 devices · bench testing and sensor validation

Round 210-15 units + 30 Wi-Fi/BLE beacons · ward deployment

Band swapTwo bands per bed · charged spare in dock · swap at shift change

Training1-hour sessions per ward · led by Madhav

SupportOn-site rotation during banding · <6 hour response

DataAll data on virtual private server · nothing leaves hospital network

Ward Infrastructure

Zone listenersOne per room · one per bathroom · pairs at exits · corridor coverage

Listener powerMains + UPS per node

NetworkHospital Wi-Fi for band connectivity · Ethernet backhaul for listeners

ServerVirtual private server · zone engine · alert routing

Alert pathDual: Wi-Fi direct to server + BLE via listeners

Key Risks

Hardware revision needed — spin-1 board may need rework

Mitigated: module prototypes validate sensors and firmware before board arrives

Battery life on hospital Wi-Fi — network settings affect power draw

Mitigated: 32 kHz crystal for light-sleep · no band scanning · request DTIM ≥3 from hospital IT

Bathroom zone boundary — signal through tiled walls varies

Mitigated: dedicated listener inside each bathroom · walk tests before banding

Nurse adoption — new workflow for ward staff

Mitigated: 1-hour training · band-on/off under 15 seconds · simple console

Execution Plan

7 pilot sprints (PS1-PS7), 8 milestones, 62 deliverables. Two-week sprint cycles from 15 Oct 2026 to 20 Jan 2027.

8 Leadership Milestones

	Milestone	Owner	Sprint	Date
M1	HW platform locked	Ranga	PS1	28 Oct
M2	Pilot design signed off	Madhav	PS1	28 Oct
M3	Round 1 built and tested	Ranga	PS3	25 Nov
M4	Nurse console accepted	Srivathsa	PS3	25 Nov
M5	MOU signed	Ramana	PS4	9 Dec
M6	Deployment ready	Madhav	PS5	~12 Dec
M7	Pilot live — patients banded	Madhav	PS5	~15 Dec
M8	Go / No-Go decision	Madhav	PS7	~20 Jan

Sprint Breakdown

PS1

15 - 28 Oct

Lock HW platform, sign off pilot design doc, begin firmware development, nurse console wireframes

PS2

29 Oct - 11 Nov

PCB fabrication, firmware for FR-1/FR-2/FR-6/FR-7, console MVP development, ward assessment

PS3

12 - 25 Nov

5 units assembled and bench tested, console acceptance review, FR-3/FR-4 firmware, beacon procurement

PS4

26 Nov - 9 Dec

MOU signed, Round 2 production (10-15 units), Wi-Fi/BLE beacon setup, FR-5/FR-8 integration, family app

PS5

10 - 23 Dec

Virtual private server setup, training sessions (1-hr), end-to-end dry run, deployment ready (~12 Dec), first patients banded (~15 Dec)

PS6

24 Dec - 6 Jan

Pilot live — banding ongoing, real-time monitoring, support rotation, data collection

PS7

7 - 20 Jan

Banding data review, pilot report, go/no-go recommendation. Mean time to resolve: <6 hours.

View Full Execution Plan (62 deliverables)

Full Execution Plan

8 milestones, 62 deliverables. Click a milestone to expand its deliverables.

Discovery Phase 25 Aug - 30 Sep 2026

Only Ranga did active deliverable work; all others thinking and planning.

D1Reference designs ordered (ZSWatch, Open-SmartWatch, Watchy)Ranga25 Aug - 7 Sep

D2Reference design teardown and analysis completeRanga8 - 21 Sep

D3Firmware exploration and initial updates on reference HWRanga25 Aug - 30 Sep

M1 HW platform decision locked Ranga · PS1 · 28 Oct

M2 Pilot design document signed off Madhav · PS1 · 28 Oct

M3 Round 1 — 5 units built and tested internally Ranga · PS2-PS3 · 25 Nov

M4 Console accepted for pilot Srivathsa · PS1-PS3 · 25 Nov

M5 MOU signed Ramana · PS2-PS4 · 9 Dec

M6 Deployment ready — infra + training + Round 2 devices Madhav · PS3-PS5 · 23 Dec

M7 Pilot live — first patients banded Madhav · 15 Dec - 17 Jan

M8 Go / No-Go — core pilot decision PS7 · ~20 Jan

Weekly Updates

Weekly status with RAG indicators. Updated each Friday. Slots fill as sprints begin.

Communication Cadence

Internal standupsDaily (core team)

Sprint reviewEvery 2 weeks (end of sprint)

Customer syncWeekly (Madhav + Rajiv)

Advisor updateWeekly (Madhav + Niranjan)

EscalationWithin 24 hours

Status Log Upcoming

Week 1

PS1 · 15-21 Oct · Pending

Week 2

PS1 · 22-28 Oct · Pending

Week 3

PS2 · 29 Oct-4 Nov · Pending

Week 4

PS2 · 5-11 Nov · Pending

Weeks 5-20 will appear as sprints progress

Risks 7 open

Regulatory classification unclear — medical device (CDSCO) vs hospital safety tool

Impact: High · Owner: Ramana · Framing as staff-alerting safety tool; regulatory consultant to be engaged

AyurVAID IT infrastructure — may not support deployment (Wi-Fi, power, server)

Impact: Medium · Owner: Ranga · IT discovery report in PS1; site walk before infra install

Component lead times — sensors: 10-23 weeks

Impact: Medium · Owner: Ranga · Stage purchases early; second sources identified

Battery life — demo band at 1.0-1.5 hours, must improve for full-shift wear

Impact: High · Owner: Ranga · Baseline from reference design; target set after Round 1

No MOU in place — commercial terms not yet agreed

Impact: High · Owner: Ramana · MOU target: before pilot start

Beacon range / placement — may need iteration in real ward geometry

Impact: Medium · Owner: Ranga · E2E test on site before pilot start

Collaboration gap — communication cadence not established with AyurVAID

Impact: High · Owner: Madhav · Madhav as SPOC; biweekly updates to Rajiv

Assumptions 4 open

A-1

AyurVAID nominates executive sponsor, SPOC, IT contact, nursing lead

A-2

Virtual private server deployment — all data stays within the private server, zero outbound calls

A-3

5 wards, single property for core pilot

A-4

Wi-Fi/BLE beacons are battery/direct-powered — no separate power wiring needed per beacon

Decisions 4 closed

Madhav is SPOC for all AyurVAID communication · Decided Sep

Core pilot = standalone — no hospital system integration; integration = Phase 2 · Decided Sep

Training owned by Madhav (part of deployment track) · Decided Sep

~4 weeks banding accepted as minimum viable for go/no-go data · Decided Sep

PSG Portal

Pilot Overview

Execution

Updates

Commercials

Pilot Overview

What is PSG Device 1?

9 Functional Requirements

Timeline

Core Team

Pilot Design

Pilot Objectives

System Components

Functional Requirements — Detail

Pilot Scope

Success Criteria Go / No-Go

Deployment Approach

Ward Infrastructure

Key Risks

Execution Plan

8 Leadership Milestones

Sprint Breakdown

Full Execution Plan

Discovery Phase 25 Aug - 30 Sep 2026

Weekly Updates

Communication Cadence

Status Log Upcoming

Risks 7 open

Assumptions 4 open

Decisions 4 closed

Commercials

MOU Status In progress

Production Roadmap

Infrastructure

Key Dates to Confirm Assumption