Ambient scribe
Nabla
Nabla is an AI clinical assistant for ambient documentation, EHR-integrated note generation, multilingual support, and clinician workflow relief. Its public materials are comparatively strong on consent examples, no audio storage by default, no AI training on clinical notes, and configurable retention, but patient notice, refusal, transcript access, and correction rights remain deployment-specific.
Public-source research has been drafted; final human publication review and change-log detail are still required.
Summary judgment · 40% toward patient-directed
Mixed
Nabla is institution-led and clinician-mediated, but public consent language, no-audio-by-default claims, and no-training-on-clinical-notes claims make patient-facing governance more inspectable.
Patient agency
How this tool changes agency
Nabla may improve clinician attention and note completeness, but it is not a patient-controlled advocacy or navigation tool.
Consent is described, but opt-out/refusal workflow, documentation, and alternatives remain deployment-specific.
Patient-facing signals
Who does this AI serve?
Nabla is sold to clinicians and healthcare organizations for documentation and workflow support.
Can patients tell AI is involved?
Nabla publishes consent language, but actual notice depends on clinician and health-system implementation.
Can patients meaningfully choose?
Consent is described, but opt-out/refusal workflow, documentation, and alternatives remain deployment-specific.
Can patients correct or challenge what the AI produces?
Clinician review is central, but patient transcript/audio access and AI-specific correction routes are not clearly established.
Does it help patients understand or act?
Nabla may improve clinician attention and note completeness, but it is not a patient-controlled advocacy or navigation tool.
Text findings
Who is left out or burdened?
Evidence incomplete
Nabla claims broad language/specialty support and FQHC deployment, but independent evidence by language, accent, disability, specialty, interpreter use, and safety-net context remains limited.
What happens to patient data?
Stronger public governance claims, still deployment-specific
Nabla says audio is not stored by default, notes are not used for AI training, and note retention is configurable. Health-system agreements and local settings still matter.
Are the clinical boundaries clear?
Mostly clear
The product is clinician-assistive and requires clinician review. Order, coding, and workflow features raise downstream safety questions.
Who defined what good looks like?
Mostly clinician, vendor, and health-system-defined
Published evidence includes patient experience but emphasizes clinician burden, documentation time, and adoption. Patient agency measures are not yet central.
Review method
Deep public-source review of official product pages, trust/security pages, consent guidance, privacy policy, customer/public evidence, and published ambient-scribe research; no vendor interview or hands-on deployment testing.
Draft profile · Medium draft