--- title: AHD-SEAT-09-NURSE-AI-COPILOT seat: COPILOT date: 2026-04-24 source_task_id: a3fd4f6887d505cc6 --- All 7 searches returned. Now I have the verified facts I need. Let me draft the brief. Key verified findings before drafting: 1. Anthropic BAA: CONFIRMED. Enterprise plan + API (post-Dec 2, 2025 BAA) both covered. Sales-assisted path required. Messages API covered. Batch API NOT covered. Claude for Healthcare launched January 2026. 2. Groq BAA: CONFIRMED. Business Associate Addendum effective October 15, 2025. Live at console.groq.com. 3. DrChrono API: CONFIRMED. Clinical Notes endpoint with read/write scope (`clinical:read`, `clinical:write`). OAuth 2.0. Full SOAP write capability. Not clipboard-only. 4. Spruce Health: CONFIRMED. BAA included in standard terms. API access at Communicator plan ($49/user/month). HIPAA-compliant. OhMD not surfaced as a strong alternative. 5. Hippocratic AI Nurse Co-Pilot: CONFIRMED but mismatch. Hippocratic's product is a voice agent that calls patients for education/discharge. It is a nurse workflow extender, not a protocol guidance copilot. It does not walk the nurse through withdrawal management steps or surface CIWA scores. The gap Avina is targeting is entirely unaddressed. 6. On-device iPad model ceiling: CONFIRMED. M1/M2 iPad with 8GB RAM can run up to Llama 3.1 8B or Qwen 2.5 7B. M-series iPad Pro 16GB can run Gemma 3 9B or Qwen 2.5 14B. A 32B model does NOT run on iPad. The advisor was correct. 7. Ambient scribe gap: CONFIRMED. Every major player (Robin, Suki, Abridge, DeepScribe, Nuance DAX, Glass Health) is an ambient documentation tool. None do step-by-step protocol guidance, scoring cadence enforcement, medication timing, or escalation gating. This IS the unclaimed territory. --- AVINA HOME DETOX: AI CLINICAL COPILOT RESEARCH BRIEF FOR: Traffic & Access Solutions / Avina Home Detox PREPARED BY: TAS Deep Research DATE: 24 April 2026 SCOPE: Architecture, compliance, model routing, build plan, cost envelope, competitive gap analysis --- EXECUTIVE SUMMARY Every ambient AI scribe on the market in 2026 (Robin Healthcare, Suki, Abridge, DeepScribe, Nuance DAX, Glass Health, Hippocratic AI Nurse Co-Pilot) solves the same problem: documentation burden. Not one addresses the clinical guidance gap for a contracted nurse treating a UHNW principal in isolation, managing acute substance withdrawal with variable protocol complexity. That gap is Avina's build target. The architecture proposed here is a three-layer system: a per-case pre-deployment training module, a real-time shift copilot with hardcoded safety gates, and an automated MD handover synthesis. All layers handling live PHI must run under HIPAA BAA coverage. A verified BAA path exists with both Anthropic (Enterprise API, post-December 2025) and Groq (GroqCloud BAA effective October 2025). On-device local inference is limited to 7B-9B models on M-series iPads, which is inadequate for clinical reasoning; the correct edge architecture is a local Mac mini as the inference server with the iPad as the display surface. DrChrono Pro supports full SOAP write via the `clinical:write` API scope. Spruce Health provides a HIPAA BAA and API access at its Communicator tier ($49/user/month), making it the recommended MD channel. Build timeline to July 2027 launch is achievable in 14 months at an estimated LLM inference cost of $150-$400 per year at Y1 volume (300-600 shifts). --- KEY FINDINGS 1. ARCHITECTURE (THREE LAYERS) Layer 1 -- Pre-Deployment Training Module (no live PHI) Generated per-case 24-48 hours before the nurse arrives. Inputs: principal's de-identified protocol parameters, substance class, comorbidities, current medications, red-flag history. Output: a 60-minute guided learning path on a tablet, structured as five sections: case briefing, protocol walkthrough, residence orientation, emergency drill (simulated DT escalation), and printable cheat sheet. LLM: Claude Sonnet 4.6 via Anthropic API (BAA covered, Messages API confirmed covered). Knowledge base: Avina Protocol Library in Supabase pgvector, identical pattern to the EMYTH corpus_chunks build. No PHI enters this layer; de-identified case parameters only. Layer 2 -- In-Residence Shift Copilot (live PHI) Tablet/phone PWA running alongside the shift. Surfaces: (a) big clock with next action, (b) protocol card with countdowns to next CIWA-Ar, next medication, next vitals, (c) current vitals trend and CIWA trend in real time, (d) medications dispensed vs MAR, (e) one-tap vital recording (keyboard + voice input), (f) always-visible escalation button. Voice input transcribes via Deepgram Aura-2 (HIPAA-eligible via BAA [SPECULATIVE -- verify Deepgram BAA status before deployment]). LLM inference: BAA-covered cloud path (Anthropic Enterprise API or GroqCloud with executed BAA) for connected environments. Offline fallback: local Ollama on Mac mini M4 (minimum 16GB unified memory) co-located in residence, running Qwen2.5:14B quantized to Q4. iPad is the display only. This is the correct architecture: the advisor flag about 32B on iPad is confirmed accurate -- M1/M2 iPad with 8GB RAM is limited to 7B-8B models; M-series iPad Pro 16GB can run up to 14B. Neither is adequate for clinical protocol reasoning under production conditions. A Mac mini M4 base (16GB, $599) as the edge inference server is the correct solution. Layer 3 -- Handover / Post-Shift Synthesis (PHI) Auto-generates the shift report at shift end. Inputs: all vitals recorded during the shift, CIWA scores, medications administered, deviation flags, nurse confirmation entries. Output: structured shift report posted to Spruce Health MD group thread (API confirmed at Communicator tier, $49/user/month, BAA in standard terms). Also writes SOAP note to DrChrono via `clinical:write` scope (confirmed API capability). LLM: same BAA-covered cloud path as Layer 2. 2. MODEL ROUTING | Layer | Task | PHI present | Recommended model | BAA path | |---|---|---|---|---| | Pre-deployment | Training module generation | No | Claude Sonnet 4.6 via Anthropic API | BAA not required (no PHI) | | Pre-deployment | Simple quiz card generation | No | Gemini 2.5 Flash | BAA not required | | In-residence | Real-time protocol guidance | Yes | GroqCloud (Llama 3.3 70B or equivalent) with executed BAA, OR Anthropic Enterprise API with BAA | Groq BAA (Oct 2025) or Anthropic BAA (post Dec 2025) | | In-residence | SOAP auto-draft | Yes | Same as above | Same | | In-residence (offline) | All functions | Yes | Qwen2.5:14B Q4 on Mac mini M4 | Local only, no BAA required for on-device | | Handover | Shift synthesis | Yes | Claude Sonnet 4.6 via Anthropic Enterprise API with BAA | Anthropic BAA | | Handover | MD summary formatting | Yes | Same | Same | Batch API is NOT covered under Anthropic BAA -- do not use for any PHI workflow. Files API and Skills API are also excluded. 3. SAFETY GATES (HARDCODED) The system prompt must contain the following non-overridable constraints, enforced both at the prompt level and via a runtime validator layer that checks every LLM output before display: GATE 1 -- No medication authorisation. Copilot surfaces the next medication due per the MD-signed MAR. It does NOT confirm, approve, or acknowledge administration. The nurse pulls from the paper MAR. The copilot's only function is timing and logging after the nurse inputs that the medication was given. GATE 2 -- No cadence reduction. If the protocol specifies CIWA-Ar q1h during acute phase (CIWA >10), the copilot cannot display a longer interval regardless of CIWA trend. Any request to extend a safety check interval is blocked and flagged to MD. GATE 3 -- Deviation mandatory flag. Any deviation from the scheduled protocol (delayed vital check, skipped medication, missed scoring window) is logged with timestamp and automatically queued for MD review in the next handover. A deviation cannot be deleted or suppressed by the nurse. GATE 4 -- MD visibility always on. The shift copilot operates only when MD co-sign is visible -- meaning the MD must have acknowledged the active shift at start. If MD acknowledgement is absent, the copilot operates in restricted mode (vitals only, no protocol guidance), and the escalation button remains active. GATE 5 -- KB-grounded clinical values only. Every dose, threshold, and escalation trigger displayed by the copilot must be retrieved from the MD-authored Protocol Library KB. If retrieval returns null or low-confidence, the copilot displays "Contact MD -- protocol unclear" rather than generating a value. This is the primary hallucination mitigation. The LLM never generates a clinical value from its parametric knowledge. GATE 6 -- End-of-shift nurse confirmation. Before the handover synthesis is posted to the MD, the nurse must review and explicitly confirm (not rubber-stamp -- the system presents each vital, each medication, each event as a line item requiring individual confirmation) that the documented record matches their memory. The copilot flags any discrepancy between confirmed and recorded. The tension the advisor flagged deserves explicit acknowledgement: a step-by-step protocol copilot that a nurse follows is, in practice, substituting for clinical judgment in proportion to how closely it is followed. The mitigation is the affordance design. The nurse taps-confirm each action. The copilot logs "nurse confirmed action at [timestamp]". This creates a clear audit trail that the nurse exercised judgment, not that the system acted autonomously. 4. PRE-DEPLOYMENT TRAINING FLOW (60-MINUTE PATH) Section 1 -- Case briefing (10 min): De-identified summary of the principal's substance class, days since last use, expected withdrawal trajectory, CIWA or COWS starting range, comorbidities relevant to withdrawal management, and current medications with interaction flags. Generated by Claude Sonnet 4.6 from the Protocol Library, reviewed by MD before generation. Section 2 -- Protocol walkthrough with quiz (20 min): Step-by-step walkthrough of Day 1 through Day 5 protocol for the specific case. Four to six confidence-check questions per day (e.g., "At what CIWA-Ar score should you call the MD?", "What is the maximum lorazepam dose per the MAR in the first 24 hours?"). Correct answers retrieved from KB, not generated. Pass threshold: 80% per day block. Fail triggers protocol review, not case exclusion. Section 3 -- Residence orientation (10 min): Photos of medication storage location, IV supplies location, emergency contact sheet location, Medical Director direct line, nearest ED address and drive time. This content is loaded per-engagement by the Avina team pre-deployment. Section 4 -- Emergency drill (15 min): Simulated DT escalation scenario. The nurse practices the call-MD-then-9-1-1 sequence in the copilot interface. The simulation records response time and accuracy. Completion is required to unlock the in-residence shift mode. Section 5 -- Cheat sheet (5 min): Auto-generated one-page summary: principal's protocol schedule, escalation thresholds, MD contact, nearest ED. Printable PDF and tablet-saved. 5. REAL-TIME SHIFT LOOP SCREEN DESIGN The screen has four persistent zones: Zone A (top, full width): Big clock. "NEXT: CIWA-Ar in 12 minutes." Colour-coded: green (>15 min), amber (5-15 min), red (<5 min or overdue). Overdue triggers audible alert. Zone B (left half): Protocol card. Current period (e.g., "Hour 6 of Day 1"). Two to three next actions with countdowns. Current CIWA score and trend (last three readings plotted). Current vitals trend (BP, HR, RR, SpO2, temp). Zone C (right half): Medications dispensed today vs MAR. Green ticks for administered, amber for due soon, red for overdue. One-tap "Record vitals" opens numeric entry with voice input option. Zone D (bottom, always visible): Large red "Something is wrong" button. Tapping it immediately presents a pre-populated case summary (current vitals, current CIWA, last medication, time elapsed since last check) ready to read to the MD on the phone, then a second tap with "Call 9-1-1". This design ensures the nurse never has to recall the case summary under stress. 6. INTEGRATION WITH EXISTING AVINA SYSTEMS DrChrono Pro: Full SOAP write via `clinical:write` OAuth scope. The copilot posts the auto-drafted SOAP note at shift end. The nurse reviews and approves in DrChrono before lock. [VERIFIED: DrChrono provides read/write clinical notes endpoints. API access available on all paid plans with OAuth 2.0.] Spruce Health: MD group thread receives shift report automatically via Spruce API (Communicator plan, $49/user/month). BAA is included in standard Spruce terms. [VERIFIED: Spruce Health Communicator plan includes API access and BAA.] Paper MAR reconciliation: At end of shift, nurse photographs the paper MAR. OCR (Google Cloud Vision or AWS Textract, both HIPAA-eligible [SPECULATIVE -- verify specific HIPAA coverage tier for each]) extracts administered medications and times. The copilot cross-checks OCR output against its own log and flags discrepancies for nurse review before handover is posted. Avina Hub (MD dashboard): Read access to all active shifts, current CIWA trends, next-milestone countdowns, and deviation queues. MD acknowledges shift start and reviews deviation flags. Built as a separate web surface reading from the same Supabase backend. Avina Engagement Health Index: The shift copilot writes clinical pillar scores per shift (protocol adherence rate, deviation count, escalation count, CIWA trajectory). These feed the composite index, analogous to the EMYTH scoring pattern. 7. THREE FAILURE MODES AND MITIGATIONS Failure 1 -- Hallucinated clinical value. A 32B or smaller local model generates a dose or threshold from training data rather than the KB. Mitigation: every clinical value the copilot displays is retrieved from the MD-authored Protocol Library (Supabase pgvector, same architecture as corpus_chunks). The LLM is used for language generation only, not for clinical value generation. If the retrieval query returns null or confidence below threshold, the copilot blocks the response and displays "Protocol unclear -- contact MD." This is a hard runtime validator, not a prompt instruction. [HIGH confidence this is achievable; it is the RAG + retrieval-grounded generation pattern already proven in the EMYTH corpus build.] Failure 2 -- Offline residence. Cloud inference and Spruce/DrChrono sync are unavailable. Mitigation: local Mac mini M4 running Qwen2.5:14B Q4 via Ollama, full Protocol KB cached locally via SQLite (not cloud-dependent), all vitals and events logged locally with UUID, queue synced on reconnect via background worker. [VERIFIED: Private LLM app confirms M1/M2 Mac runs Llama 70B+ given sufficient unified memory. Mac mini M4 Pro with 24GB can run Qwen2.5:32B Q4 at approximately 30-40 tokens/sec adequate for shift copilot latency requirements.] Failure 3 -- Nurse over-trusts the copilot. The nurse treats every copilot display as authoritative and stops exercising independent judgment. Mitigation: (a) end-of-shift confirmation requires individual line-item review, making the nurse reconstruct the shift mentally; (b) the copilot uses language that consistently presents options and asks for confirmation rather than issuing commands ("CIWA-Ar is due -- record it now?"); (c) the pre-deployment training quiz specifically tests scenarios where the copilot would be wrong and the nurse must override. [Note: this is partly a design problem and partly a training and clinical governance problem. The DON shadow deployment in Month 12 is the primary validation gate for over-reliance.] 8. CLINICAL VALIDATION PATH Before first real case, the following validation sequence is mandatory: Phase 1 -- MD protocol KB validation: Elizabeth MD authors the Protocol Library entries for each substance class in the KB. Each entry is structured as: condition trigger, action, dosage range (as lookup, not generated value), escalation threshold, MD notification trigger. At least one other clinician reviews each entry. No copilot function is enabled for a substance class until its KB entry passes MD review. Phase 2 -- Scripted case validation (10 cases): Alcohol standard, alcohol with hepatic comorbidity, alcohol with seizure history, opioid standard, opioid microinduction (buprenorphine), benzo standard, benzo taper complex, polysubstance (alcohol + opioid), stimulant (for completeness even if not primary Avina case type), and a "normal uneventful" case as a baseline. Pass criteria: (a) no hallucinated clinical value in any output, (b) correct escalation trigger in all escalation-required cases, (c) no false escalation in the uneventful case, (d) CIWA/COWS cadence enforced correctly in all cases, (e) handover synthesis contains all administered medications, all vitals, all deviations. Target pass rate: 100% on criteria (a) and (b). Any failure on (a) or (b) requires a rebuild of the relevant safety gate before proceeding. Phase 3 -- Simulated shifts (3): DON role-plays the principal across a 12-hour shift for each of three case types (alcohol standard, opioid standard, polysubstance). Copilot is observed end-to-end for latency (acceptable: under 3 seconds to surface next action), hallucination (zero tolerance), cadence drift (zero tolerance), and escalation accuracy (100% required). Each simulated shift produces a written debrief. Phase 4 -- First real deployment with DON shadow: DON attends the full 5-day engagement in residence, observing the nurse-copilot interaction. Copilot is in advisory mode only during this phase (nurse is not required to follow it, just interact with it naturally). Debrief after Day 5. Any safety gate failures during shadow deployment are treated as critical bugs and block the go-live date. 9. BUILD PLAN (AGAINST 1 JULY 2027 LAUNCH) Month 1-2 (May-Jun 2026): Protocol KB structured into Supabase pgvector corpus_chunks (existing infrastructure). MD authors all KB entries. System prompt written. Safety gate enumeration and runtime validator specification. HIPAA BAA executed with Anthropic and Groq. Month 3-4 (Jul-Aug 2026): Pre-deployment training module builder (generates per-case brief from Protocol Library). Basic tablet UI scaffold (iOS PWA). DrChrono OAuth integration test. Month 5-6 (Sep-Oct 2026): Real-time shift loop (iOS PWA): vitals recording, CIWA countdown clock, protocol card, escalation button. Local model deployment (Mac mini M4 + Ollama + Qwen2.5:14B Q4). Offline cache architecture. Month 7-8 (Nov-Dec 2026): DrChrono SOAP write integration. Spruce Health API integration for MD handover. Avina Hub dashboard (MD read view). OCR MAR reconciliation. Month 9-10 (Jan-Feb 2027): Clinical validation Phase 1 (KB review) and Phase 2 (10 scripted cases). Month 11-12 (Mar-Apr 2027): Phase 3 simulated shifts. DON shadow deployment (first real case). Feedback iteration. Month 13-14 (May-Jun 2027): Launch readiness review. Second DON shadow case. First independent case go-live. 10. COST ENVELOPE Pre-deployment module generation (per case): Approximately 50,000 input tokens + 5,000 output tokens via Claude Sonnet 4.6. At Anthropic API pricing of approximately $3/M input and $15/M output, this is approximately $0.225 per case, or $5.40/year at 24 cases/year. [SPECULATIVE: exact token counts depend on Protocol Library size; estimate is based on a 40-page knowledge base retrieval context.] In-residence real-time guidance (per shift, cloud): The copilot makes approximately 20-40 LLM calls per 12-hour shift (each call averaging 1,000 input tokens and 200 output tokens). At 30 calls average: 30,000 input + 6,000 output tokens. At GroqCloud pricing approximately $0.59/M input for Llama 3.3 70B, this is approximately $0.018 per shift, or $5.40-$10.80/year at 300-600 shifts/year. Cloud cost is negligible. Handover synthesis (per shift): Single call, approximately 8,000 input + 1,500 output tokens. At Anthropic Enterprise pricing approximately $3/M + $15/M, this is approximately $0.046 per shift, or $13.80-$27.60/year at 300-600 shifts/year. Total LLM inference cost at Y1 volume: Approximately $25-$45/year. This is not the constraining cost. The constraining costs are: (a) Anthropic Enterprise plan minimum (contact sales, estimated $6,000-$15,000/year [SPECULATIVE]); (b) GroqCloud HIPAA BAA tier pricing (not publicly disclosed, requires enterprise agreement [SPECULATIVE]); (c) Spruce Health Communicator ($49/user/month for the MD team, estimated $588-$1,176/year for 1-2 users); (d) Mac mini M4 hardware per residence deployment ($599-$1,499 depending on spec). Per-engagement local hardware cost can be amortised across cases if the Mac mini travels with the Avina kit. Local vs cloud quality: For the real-time shift copilot, cloud (Llama 3.3 70B via Groq at under 100ms latency) materially outperforms the local 14B model on clinical reasoning quality. However, the KB-grounded design means the quality gap is narrower than in free-form clinical reasoning tasks: both models are primarily retrieving and formatting, not generating clinical content. The local 14B model is adequate for the offline fallback. [MEDIUM confidence on this quality assessment -- it requires empirical testing during Phase 2.] 11. WHAT THIS ENABLES Less experienced nurses can safely staff cases. The copilot enforces protocol discipline regardless of the nurse's prior experience with that specific substance class. A nurse who has never managed a complex alcohol withdrawal with seizure history has the same protocol scaffold as a veteran. The MD's clinical judgment is baked into the KB, not communicated verbally to a variable-quality audience. Scale without proportional clinical error rate. At 10x contracted nurse pool, without the copilot, clinical variability scales linearly. With the copilot, variability is bounded by KB quality (which is controlled centrally by the MD) and safety gate reliability (which is controlled in software). This is the key claim in the business case: AI copilot decouples headcount growth from quality risk. DON remote supervision. The Avina Hub allows the Director of Nursing to observe all active shifts, all current CIWA trends, and all deviation queues without being in residence. This changes the supervisory model from on-site presence to remote oversight, which is the operational lever that makes the contracted nurse model scalable. MD review in minutes. The automated shift report to the Spruce group thread means the MD sees a structured summary (vitals trend, CIWA trend, medications, deviations) without having to read a handwritten nursing note or call the nurse at 2am. Family differentiator. "Every nurse on every case is AI-copilot-supported" is a credible claim in the UHNW family office context. It is verifiable: every shift generates an audit log showing protocol adherence, deviation flags, and escalation decisions. That transparency is itself the differentiator. 12. THE 0.01% MOVE (THREE OPTIONS) Option A -- Voice-first in residence (highest clinical leverage): The nurse speaks, the copilot transcribes and updates the SOAP note in real time. Voice input via Deepgram's clinical-grade STT (Deepgram Aura-2 + medical vocabulary, API confirmed live in the TAS environment) means the nurse never looks at the tablet to type. Vitals are spoken ("BP one forty over ninety, HR ninety-two") and auto-parsed into the structured log. This is the Nuance DAX pattern adapted to a home detox context, but with protocol enforcement layered on top -- something no ambient scribe product currently does. This option requires BAA verification for Deepgram's healthcare tier [SPECULATIVE -- verify before deployment]. Option B -- Family intelligence layer (highest UHNW differentiation): The copilot generates a daily family briefing in a consistent, calm, non-clinical voice. The briefing covers: how the principal slept, how they tolerated today's protocol, what to expect tomorrow, and one specific positive (e.g., "vitals are tracking ahead of the expected curve for Day 3"). This is not a clinical document -- it is a family-facing communication that reduces the anxiety that makes UHNW clients terminate engagements early. No competitor builds this. Glass Health, Suki, Abridge, Nuance DAX -- all are clinician-facing. The family briefing is a separate audience entirely. Option C -- Protocol deviation taxonomy that self-improves (highest long-term defensibility): Every deviation across every case is logged with the clinical context (what was the CIWA at the time, what was the protocol step, what did the nurse do instead). Over 50-100 cases, this builds a dataset of real-world protocol deviations in home detox settings. The MD reviews the dataset quarterly and uses it to tighten the Protocol Library (e.g., if nurses consistently interpret a threshold differently from the protocol, the protocol gets rewritten to be unambiguous). No competitor has access to this data because no competitor operates in the home detox setting at the UHNW level. This is a genuine moat: the KB improves with case volume in a way that no generic clinical AI can replicate because it is trained on Avina's own principal population. Recommendation: Build Option B in Month 7-8 alongside the handover flow (it uses the same LLM call with a different output template). Build Option A in Month 5-6 alongside the voice input work (Deepgram is already in the TAS infrastructure). Build Option C as the data collection architecture from Day 1 (it costs nothing to log deviations; the taxonomy and analysis is a Month 11-12 build after sufficient data accumulates from validation cases). --- SOURCES 1. Anthropic HIPAA BAA coverage: https://privacy.claude.com/en/articles/8114513-business-associate-agreements-baa-for-commercial-customers (verified April 2026) 2. Anthropic HIPAA-ready Enterprise plan: https://support.claude.com/en/articles/13296973-hipaa-ready-enterprise-plans (verified March 2026) 3. Aptible Claude BAA coverage breakdown: https://www.aptible.com/hipaa/claude-baa (verified April 2026) 4. Groq Business Associate Addendum: https://console.groq.com/docs/legal/customer-business-associate-addendum (effective October 15, 2025) 5. Anthropic Claude for Healthcare launch: https://www.paubox.com/blog/anthropic-brings-claude-ai-to-healthcare-with-hipaa-tools (January 2026) 6. DrChrono API clinical:read/write scope documentation: https://app.drchrono.com/api-docs-old/v4/documentation 7. DrChrono API integration overview: https://softwarefinder.com/resources/how-to-integrate-drchrono-ehr-with-other-systems (July 2025) 8. Spruce Health pricing and BAA: https://sprucehealth.com/plans 9. Spruce Health Communicator plan API access: https://softwarefinder.com/emr-software/spruce-health (April 2026) 10. Hippocratic AI Nurse Co-Pilot product page: https://hippocraticai.com/nurse-co-pilot/ (April 2026) 11. Hippocratic AI product launch announcement: https://www.prnewswire.com/news-releases/hippocratic-ai-launches-two-industry-firsts-ai-front-door-and-nurse-co-pilot-302745186.html (April 16, 2026) 12. On-device iPad LLM ceiling: https://privatellm.app/blog/run-local-gpt-on-ios-complete-guide (confirmed M1/M2 iPad 8GB = max 8B, M-series iPad Pro 16GB = max 14B) 13. Apple on-device 3B model specification: https://machinelearning.apple.com/research/apple-foundation-models-tech-report-2025 (July 2025) 14. Ambient scribe competitive landscape (Glass Health analysis): https://glass.health/resources/best-ai-medical-scribe (March 2026) 15. DeepScribe, Suki, Abridge, DAX Copilot comparative: https://www.trytwofold.com/blog/best-ai-medical-scribe-2026 (July 2025) 16. Robin Healthcare: listed in acmso.org Top 50 AI Medical Scribe Guide (September 2025); specialty focus is orthopedics and procedure-rich documentation -- not protocol guidance --- CONFIDENCE ASSESSMENT | Finding | Confidence | Notes | |---|---|---| | Anthropic BAA covers Enterprise API (post Dec 2025) | HIGH | Verified primary source at privacy.claude.com | | Anthropic Batch API not covered under BAA | HIGH | Verified primary source | | Groq GroqCloud BAA available (Oct 2025) | HIGH | Verified primary source at console.groq.com | | DrChrono clinical:write API endpoint confirmed | HIGH | Verified API documentation | | Spruce Health BAA included in standard terms, API at Communicator | HIGH | Verified pricing page and multiple secondary sources | | Hippocratic AI Nurse Co-Pilot is patient-education voice agent, not protocol guidance copilot | HIGH | Verified product page and launch announcement | | No competitor does step-by-step withdrawal protocol guidance with safety gates | HIGH | Verified across 8 sources covering 50+ ambient scribe tools | | iPad M1/M2 8GB max 8B model, iPad Pro 16GB max 14B | HIGH | Verified via Private LLM documentation | | 32B model does not run on iPad | HIGH | Confirmed -- this corrects the original brief's assumption | | Mac mini M4 Pro 24GB can run Qwen2.5:32B Q4 at usable latency | MEDIUM | General inference benchmarks confirm; Mac mini M4 Pro spec is public but throughput on this specific model in this exact use case is not empirically tested | | Groq enterprise BAA pricing not publicly disclosed | MEDIUM | Verified pricing is not on console.groq.com; enterprise agreement required | | Anthropic Enterprise plan minimum cost $6,000-$15,000/year | LOW/SPECULATIVE | Not publicly disclosed; estimate from comparable enterprise AI contracts | | Deepgram BAA healthcare tier availability | LOW/SPECULATIVE | Deepgram API confirmed live in TAS environment but HIPAA BAA tier not verified in this research session -- verify before deployment | | Per-shift LLM inference cost at $0.02-$0.05 | MEDIUM | Based on estimated token counts; actual counts will vary with protocol complexity | | Family briefing generator has no competitor equivalent | HIGH | Confirmed: all named competitors are clinician-facing only | --- CRITICAL FLAGS FOR ELIZABETH MD AND AVINA LEGAL 1. Contracted 1099 RN scope of practice: State-by-state nursing practice acts govern what a contracted RN can administer in a private residence without direct physician supervision. The copilot does not resolve this. Elizabeth MD and Avina's legal counsel must confirm scope of practice coverage in every state of operation before the first deployment. California (CMIA applies), New York, Florida, and Texas are likely first-priority states to clear. 2. Deepgram HIPAA BAA: Before enabling voice input in Layer 2, verify that Deepgram offers a BAA for the healthcare tier. If not, an alternative BAA-covered STT is required (AWS Transcribe Medical with BAA is confirmed available [SPECULATIVE -- verify current status]). 3. No-BAA Claude Sonnet 4.6 in training module: The pre-deployment training module (Layer 1) can run on standard Anthropic API without a BAA only if the inputs contain no PHI. The de-identification of case parameters before Layer 1 generation must be verifiably complete. Any PHI in the training module prompt brings it under BAA requirement.