UI Overview
The clinician view shows patient status, recovery metrics, alerts, and expandable trend panels.
Dashboard
The list groups patient status, post-op day, step recovery, sleep recovery, and heart rate in one row.
Expanded Patient
Expanded rows show longer recovery curves for steps, sleep, and heart rate against the patient baseline.
The Problem
Sleep and ambulatory recovery change before and after surgery, but those trajectories are often reviewed only during scheduled clinical contact. MedWatch tracks step recovery, sleep recovery, and heart rate so the care team can follow recovery trends between visits.
MedWatch uses the patient's smartphone as a recovery data channel, giving clinicians structured pre- and post-operative recovery data without EHR integration. In many healthcare settings, the complexity of EHR access, governance requirements, and institutional barriers make direct system integration impractical. MedWatch is designed to operate independently of the EHR as a remote monitoring layer.
Monitoring Gap
Limited between-visit visibility
Clinicians may not have a simple view of sleep and ambulatory recovery between appointments.
Baseline matters
Pre-operative sleep, heart rate, and activity provide context for interpreting post-operative recovery.
Trend review
Structured recovery curves make it easier to see whether ambulation and sleep are returning toward baseline.
Methodology
MedWatch was built around the deployment realities clinical teams face. EHR integration is hard, expensive, and often blocked by institutional governance. The system runs as a standalone web app on a local server, with patients logging data from their phone and clinicians reviewing the dashboard from inside the institution's network.
Patients log recovery data from a browser on their phone. The server aggregates it into per-patient recovery scores. Thresholds flag patients who need clinical attention. The clinical team sees a single triage view sorted by acuity, with the ability to drill into any patient's full recovery trajectory.
Front-end skills
Responsive web UI, native chart rendering, theme system, dashboard composition.
Clinical skills
Post-operative recovery trajectory, acuity scoring, threshold calibration.
Product skills
Triage dashboard design, alert prioritisation, expand/collapse interaction.
Deployment skills
Local-server packaging, institutional governance fit, no-EHR architecture.
At a glance
The system runs as a web app on the institution's own infrastructure and does not require direct EHR integration.
Web
App
Local
Server
3
Metrics
01 Capture
Patients access MedWatch via their smartphone browser and log daily step count, sleep duration, and heart rate, three key physiological indicators of recovery trajectory.
02 Sync
Data is submitted through the web interface and stored on a local server, keeping patient data within the institution's own infrastructure.
Acuity
03 Score
Wearable trends are aggregated into per-patient recovery scores and statuses. Threshold rules flag patients whose recovery trajectory warrants clinical attention.
Alert
04 Review
The dashboard surfaces alerts and recovery summaries acuity-sorted. The team triages remotely — calling the patient, adjusting medications, or scheduling an urgent visit without waiting for the next appointment.
The System
01 · Triage Dashboard
Clinicians manage an entire panel of recovering patients from a single prioritised view, acuity-sorted so the patients who most need attention appear immediately.
Patient rows are expandable inline — open one to see the full step, sleep, and HR recovery curves without leaving the triage view.
02 · Recovery Trends
Each patient's step, sleep, and heart rate trends are visualised alongside their pre-op baseline, so trajectory changes are visible during review.
The pre-op baseline anchors the visualisation. A heart rate of 98 bpm is meaningless without the patient's normal range; against a 72 bpm baseline it's a 36% elevation worth a phone call.
03 · Local Deployment
MedWatch runs on a local server inside the institution's network. There's no EHR integration to negotiate, no external API to validate, and no PHI leaving the institutional perimeter.
The app can be run as a standalone monitoring layer while EHR integration, governance, and procurement questions are handled separately.
Why It Matters
Sleep and ambulation are important signals during pre- and post-operative recovery. Structured remote monitoring gives the clinical team a clearer view of those trends between visits.
Post-Op
Home recovery focus
Web App
Local server
3 Metrics
Steps · Sleep · HR
Live
Local deployment
