Thermal overlay
Move your pointer (or finger) along the leg. A perfusion heat-map fades in where you look — and every annotation lands in the margin, never on the body itself.
Why margins matter here: the cool zone on the lower leg reads “low perfusion — check diabetic foot”, but the label and arrow live beside the limb. The center of the body stays clean for hands, wounds and eye contact.
Contactless vitals
A camera signal — ambient light reflected by the skin — is enough to extract a pulse. No electrodes, no cuff, no touch. The waveform below is simulated from that principle.
How it will work: the glasses' RGB camera tracks micro-changes in skin color caused by blood flow (photoplethysmography), computes heart rate and oxygen saturation on-device, and flashes the number at the edge of the lens — a glance, not a screen between you and the patient.
Margin HUD
The attention budget: the center of vision belongs to the patient. Everything the agent wants to say lives in the periphery — and only one object may ask for attention at a time. Click any margin chip (or press the button) to hand it the budget.
The rule the page itself practices: marks live in margins. A HUD that paints numbers over a face is a HUD that gets taken off. One object at a time; the rest wait their turn, dimmed.
What the glasses do
Four capabilities, one frame — each demonstrated above.
Thermal overlay
- Live perfusion heat-map over skin, revealed by gaze/pointer, not plastered on
- Cool zones flagged in margin notes — diabetic foot, circulation, inflammation
Contactless vitals
- Camera-based PPG: HR, SpO₂, respiration — no electrodes, no touch
- Numbers at the lens edge; alerts escalate to the margin, never the center
Shared marks
- Anchors pinned to body-space, not screen-space — stable as the patient moves
- Multi-viewport sync: what the doctor marks, the nurse sees, same second
- Signable receipts — who marked what, when, on whose record
Margin HUD
- Attention budget: center belongs to the patient, always
- One attention request at a time; everything else queues dimmed in the periphery
What we can program
MARG is built on an OEM Android-based glasses platform. We own the whole software lane — this is what our code touches.
Firmware lane
- OEM Android-based SDK — full application layer, display compositor for both lenses
- Sensor drivers — thermal sensor, ToF depth, IMU fusion, mic-array beamforming
- On-device vision models — body tracking, anchor stability, PPG extraction; quantized, no cloud round-trip
- Update by signed deltas — firmware and models ship as cryptographically signed incremental updates; unsigned code never boots
Why Android-based matters
- Mature toolchain: Kotlin/C++, NDK, A/B partitions, OTA infrastructure
- Real-time display pipeline we can throttle — the attention budget is enforced at compositor level, not by app politeness
- Existing OEM hardware lanes mean we program, not fabricate — faster to clinical validation
The pair: glasses + tablet
One exam, two screens, two depths. The glasses capture and point; the tablet deepens and shares. Neither replaces the other — they are the pair.
Glance on the lens
- Capture & anchor — cameras and sensors read perfusion, vitals and body position while the doctor keeps hands free and eyes on the patient
- Voice inquiry — "examine the left leg", "show the last photo of this lesion" — answers arrive as quiet margin confirmations, never covering the patient
- Point — the mark, the alert, the number: one object at a time at the edge of vision
Dive on the tablet
- The full picture — complete thermal map, exam history, side-by-side comparisons — content too rich for the lens margin, shown where it belongs
- Shared with the patient — the doctor turns the screen: the patient sees their own data; trust grows in the conversation
- Extended battery & compute — heavy processing can run on the companion, keeping the glasses light enough for a full shift
Any Android device the doctor already owns
- Just an app — the MARG companion is a regular Android app: install from the store, pair with the glasses over encrypted link, done
- Works on what is already in the pocket — phone, tablet or the clinic's existing devices: the doctor buys the glasses; the second screen is the one they already have
- Offline-first sync — paired devices share the same signed marks in real time; if the link drops, each keeps working and reconciles later
Same truth on both screens
- One mark, every device — what the doctor marks by voice appears identically on the lens margin and the tablet screen, same second
- Signed both ways — voice commands and marks produce receipts: who asked, what was shown, when — on whose record
- Fits every delivery mode — hospital on-prem (clinic-owned tablets, data never leaves), hybrid, or clinic SaaS with each doctor's own device
What they must have
The non-negotiables — the frame we will accept from hardware, and the privacy bar we hold ourselves to.
Sensors
- RGB + thermal + ToF — color, heat and depth fused into one body-space anchor model
- IMU — head tracking so marks stay glued to the world, not the lens
- Mic array — beamformed voice for hands-free dictation and mark placement
Wearability
- < 80 g — a full shift must forget it's there
- All-day battery — thermal + vision workloads budgeted to last the shift, not the demo
Privacy
- On-device first — video and vitals processed on the glasses; raw frames never leave by default
- HIPAA / GDPR-grade — signed data lineage for every mark, every update, every access