Patient care navigation and health copilot AI
Alcott
Alcott is a hybrid visit companion that helps patients and families prepare for healthcare visits, record visits, generate summaries, track follow-up tasks, share with family or clinicians, and help clinics receive pre-visit briefs or completed intake forms. Its patient/family-free model, patient-facing control language, audio-deletion claim, access/download/delete rights, and family coordination features are agency-positive. The main CAIHL cautions are that the strongest evidence is official-only, patient-reported material can flow into clinic systems, AI-generated summaries and briefs need correction/contestability review, recording-consent burden is placed on users, and marketing/app shells use analytics and advertising pixels while the privacy policy says health data is not used for advertising.
Public-source research has been drafted; final human publication review and change-log detail are still required.
Summary judgment · 72% toward patient-directed
Potentially agency-expanding, mixed
Alcott is patient- and family-facing and unusually explicit about patient data control, but clinic integrations, EHR/CRM write-back, family sharing, and vendor-defined AI summaries make the agency effect deployment-dependent.
Patient agency
How this tool changes agency
The product is built around practical action support: agenda setting, visit summaries, follow-up tasks, reminders, family sharing, document sharing, calendar/task export, and clinician handoff materials.
Self-directed patient and family use appears voluntary and free. Clinic-invited prep links, SMS reminders, family/caregiver sharing, and recording workflows require hands-on review for opt-out, refusal pressure, and proxy-consent controls.
Patient-facing signals
Who does this AI serve?
Alcott serves patients and families directly, while also selling clinic subscriptions for pre-visit intelligence, intake automation, EHR/CRM integration, and workflow relief.
Can patients tell AI is involved?
Public materials describe AI-guided visit preparation, AI-generated summaries, AI insights, scribe transcription, and chat over uploaded records. Downstream use of briefs, completed forms, or EHR write-back may be less visible and needs deployment review.
Can patients meaningfully choose?
Self-directed patient and family use appears voluntary and free. Clinic-invited prep links, SMS reminders, family/caregiver sharing, and recording workflows require hands-on review for opt-out, refusal pressure, and proxy-consent controls.
Can patients correct or challenge what the AI produces?
Alcott discloses access, download, deletion, and account closure rights, and app text suggests notes can be added to sections. Public materials do not yet clearly document patient correction of AI-generated clinician briefs, completed intake forms, EHR write-back, visit summaries, or transcript errors.
Does it help patients understand or act?
The product is built around practical action support: agenda setting, visit summaries, follow-up tasks, reminders, family sharing, document sharing, calendar/task export, and clinician handoff materials.
Text findings
Who is left out or burdened?
Potentially agency-expanding, with access and proxy-consent caveats
Alcott is free for patients and families and works in a browser, which reduces cost and app-install burden. It still assumes internet access, device access, email or SMS, digital comfort, and ability to manage recording consent, family permissions, and AI-generated materials. Multilingual support is claimed, but accuracy, literacy, disability access, interpreter use, and caregiver-conflict safeguards need review.
What happens to patient data?
Comparatively detailed official policy, not independently verified
Alcott's privacy policy says it collects account information, health information, uploaded records, visit-prep chat data, scribe audio/transcripts/summaries, provider-sharing data, caregiver/patient information, and technical data. It names AWS Bedrock, AWS Transcribe Medical, self-hosted Supabase on AWS, Twilio, Stripe, Google authentication, HubSpot, Keragon, and Practice Better. The policy says audio is deleted immediately after transcription, completed patient forms are generated in real time and not stored by Alcott, health data is not sold or used for advertising, authenticated users can access/download/delete data, closed-account health content is deleted within 30 days, unauthenticated health content after 90 days, and anonymized metadata may be kept indefinitely.
Are the clinical boundaries clear?
Mostly clear in policy, still needs app and deployment review
Alcott states that it is not a medical device and does not provide medical advice, diagnosis, or treatment, and that emergencies require emergency services. The app and public pages repeat similar emergency boundaries. The clinical boundary still needs testing for high-risk symptom handling, transcript/summary errors, clinician review, and patient understanding of AI limitations.
Who defined what good looks like?
Mostly vendor-defined, early pilot claims unverified
Public pages and one-pagers report early pilot-style metrics such as intake completion, reduced clinician prep time, and fewer follow-up calls, but no independent peer-reviewed evaluation, security audit, accessibility review, patient-partnered evaluation, or validated patient-agency outcome evidence was found in this pass.
Review method
Public-source review of Alcott homepage, patient, family, clinic, how-it-works, pricing, privacy, terms, integrations, one-pager, and visit app surfaces; public HTML/app-shell inspection of visit.alcottai.com. No hands-on authenticated app walkthrough, vendor interview, patient interview, clinic deployment review, network-traffic inspection, security audit, or independent outcome evaluation.
Draft profile · Medium-low draft, official sources only