Loading TeleClinicOs...
Why hardware
The wedge is simple: the capture system should be present before the visit, obvious during consent, local during processing, and connected after clinician review.
Always present, always on, visibly ready before the visit.
Setup happens visit-by-visit on a phone, laptop, or browser tab.
32-mic far-field array engineered for clinical room acoustics.
Capture quality depends on a consumer device sitting somewhere on a desk.
Reviewed notes carry follow-ups, scheduling, messaging, and billing forward in one system.
Output stops at a draft note; staff stitch the rest together by hand.
Consent state and review status are visible hardware affordances, not buried in a UI.
Consent and audit live in whatever tool happened to record the visit.
On-device privacy
Inference runs on the device's 96 TOPS NPU. Audio is processed locally and discarded. Only the clinician-approved note crosses the network, and only when they release it.
Proof and trust
How we're approaching trust, before pilot results are public.
From design partner interview
Documentation time we're targeting per provider day, based on design partner workflows.
Provider review before finalization. Drafts are designed for approval, not silent automation.
Designed around consent visibility, role-based review, audit trail, and customer BAA requirements.