54 min readAmbient capture

Implementation Guide: Transcribe care coordination calls and generate shared care summaries

Step-by-step implementation guide for deploying AI to transcribe care coordination calls and generate shared care summaries for Allied & Mental Health clients.

Hardware Procurement

Jabra Speak2 75 Conference Speakerphone

Jabra (GN Audio)2775-419 (MS Teams variant) or 2775-109 (UC variant)Qty: 4

$280–$300 per unit (MSP cost) / $369–$399 suggested resale

Primary audio capture device for in-person care coordination calls in conference rooms and shared offices. Features 4 noise-cancelling beamforming mics, full-range 65mm speaker, USB-C/USB-A plus Bluetooth connectivity, and up to 32 hours wireless battery life. Place one in each room where multi-party coordination calls occur.

Jabra Speak2 55 Desktop Speakerphone

Jabra (GN Audio)2755-419 (MS Teams variant) or 2755-109 (UC variant)Qty: 10

$140–$160 per unit (MSP cost) / $199 suggested resale

Individual clinician desktop speakerphone for one-on-one care coordination calls from private offices. Compact form factor with 4 beamforming mics, USB-C/A plus Bluetooth. Deploy one per clinician office where care coordination calls originate.

Jabra Evolve2 55 Headset

Jabra (GN Audio)25599-999-899 (USB-C, MS Teams) or equivalent UC variantQty: 10

$160–$180 per unit (MSP cost) / $199–$229 suggested resale

Wireless headset for clinicians conducting remote/telehealth care coordination calls. Active noise cancellation ensures clean audio capture even in open or shared environments. USB-C dongle plus Bluetooth dual connectivity. One per clinician.

Ubiquiti UniFi U6-Pro Wi-Fi 6 Access Point

UbiquitiU6-ProQty: 3

$130–$150 per unit (MSP cost) / $199–$229 suggested resale

Wi-Fi 6 (802.11ax) access points to ensure reliable, low-latency wireless coverage throughout the clinical space. Ambient capture requires consistent connectivity — if the connection drops, the scribe stops working. Deploy enough APs for full coverage with no dead zones. Quantity assumes a typical 2,000–4,000 sq ft clinical office.

Ubiquiti UniFi Dream Router or USG

UbiquitiUDR or USG-PRO-4Qty: 1

$180–$200 per unit (MSP cost) / $249–$299 suggested resale

Network gateway/router with VLAN support for segmenting clinical device traffic from guest and IoT networks. Required for HIPAA network segmentation best practices. If client already has a VLAN-capable firewall (e.g., Fortinet, SonicWall, Meraki), this may not be needed.

Apple iPad 10th Generation

Apple iPad 10th Generation

AppleMPQ03LL/A (64GB Wi-Fi) or equivalentQty: 2

$320 per unit (MSP cost) / $379–$399 suggested resale

Shared mobile tablets for clinicians who move between rooms or conduct coordination calls from variable locations. AI scribe companion apps run on iOS. Also useful for presenting consent forms to patients and capturing signatures digitally.

USB-C Docking Station

Anker or CalDigitAnker 575 (A8396) or CalDigit TS4Qty: 10

$80–$120 per unit (MSP cost) / $129–$169 suggested resale

Universal docking station for clinician workstations to provide a single-cable connection for the Jabra speakerphone/headset, external display, and network connectivity. Ensures clean desk setup and reliable USB audio device connectivity.

Software Procurement

Twofold Health AI Scribe

Twofold HealthSaaS per-seat (annual billing recommended)Qty: 10 clinicians

$49/clinician/month (annual) — $490/month for 10 clinicians

Primary ambient AI scribe platform for transcribing care coordination calls and generating structured clinical notes. Purpose-built for mental health with sub-30-second draft times, flat unlimited pricing, instant BAA, auto-purged audio, and SMART treatment plan generation. Supports SOAP, DAP, BIRP, and GIRP note formats. This is the core transcription and initial note generation engine.

OpenAI API (GPT-5.4)

OpenAIGPT-5.4Qty: Usage-based API

~$2.50 per 1M input tokens / $10 per 1M output tokens; estimated $50–$150/month for 10-clinician practice

Powers the custom Care Coordination Summary Generator. Takes raw transcripts from care coordination calls and generates structured shared care summaries with standardized sections (participants, discussion points, treatment plan updates, action items, follow-up dates). Used via the API with a signed BAA under OpenAI's Enterprise or Team agreement.

Deepgram Nova-3 Medical (Optional — for custom pipeline)

DeepgramNova-3 MedicalQty: Usage-based API

$0.0043/minute pre-recorded, $0.0077/minute streaming; estimated $30–$80/month for 10-clinician practice

Alternative/supplementary speech-to-text API for the custom care coordination summary pipeline. Provides medical-vocabulary-optimized transcription with speaker diarization (critical for multi-party coordination calls). BAA available for Enterprise customers. Use this if building a fully custom transcription pipeline instead of relying solely on Twofold Health's built-in transcription.

Paubox Email Suite Plus

PauboxSaaS per-domainQty: per user/month

$29–$59/user/month; practice-wide ~$200–$400/month

HIPAA-compliant encrypted email for securely sharing care coordination summaries with external providers on the treatment team. Seamless encryption with no portal required for recipients. Integrates with Google Workspace and Microsoft 365.

Spruce Health (Alternative to Paubox)

Spruce HealthSaaS per-seat

$24–$49/user/month

HIPAA-compliant secure messaging and communication platform for sharing care summaries and coordinating care within and across practices. Includes secure messaging, shared team inbox, and phone/fax capabilities. Better suited if the practice needs a unified communication hub rather than just encrypted email.

SentinelOne Singularity (via MSP Partner Program)

SentinelOneSingularityQty: Per-endpoint, annual

$3–$6/endpoint/month (MSP cost); resale at $8–$12/endpoint/month

Endpoint Detection and Response (EDR) for all clinician workstations and tablets that access PHI. Required for HIPAA endpoint security. Provides autonomous threat prevention, detection, and response with forensic logging.

Duo Security MFA

Cisco / DuoPer-user SaaS

$3–$6/user/month (MSP cost); resale at $6–$9/user/month

Multi-factor authentication for all clinician accounts accessing the AI scribe platform, EHR, and any system containing PHI. HIPAA requires access controls — MFA is the baseline. Duo integrates with virtually all SaaS and on-prem applications.

Compliancy Group (The Guard)

Compliancy GroupAnnual subscription

$300–$500/month for the practice (MSP partner pricing available)

HIPAA compliance management platform covering risk assessments, policy management, employee training tracking, BAA management, and audit readiness. MSPs can co-sell and manage on behalf of the practice. Provides the documentation trail that proves compliance in the event of an audit or breach.

KnowBe4 Security Awareness Training

KnowBe4Per-user SaaS annual

$3–$5/user/month (MSP cost); resale at $5–$8/user/month

HIPAA-specific security awareness training and phishing simulation for all practice staff. Mental health practices handle extremely sensitive PHI — one phishing compromise can be catastrophic. Includes training modules specific to healthcare and HIPAA compliance.

Prerequisites

  • Active EHR/Practice Management subscription (SimplePractice, TherapyNotes, Jane App, PIMSY, Healthie, or WebPT for allied health) — confirm exact platform and version before beginning
  • Business-grade internet service with minimum 25 Mbps symmetrical bandwidth and an SLA from the ISP — verify actual measured speeds at the site, not advertised speeds
  • HIPAA-compliant email or secure messaging already in place, or budget approved for Paubox/Spruce deployment as part of this project
  • Existing or planned endpoint protection (EDR/antivirus) on all workstations and mobile devices that will access the AI scribe platform or PHI
  • Legal review of state recording consent laws for the practice's state(s) of operation — particularly critical in all-party consent states (CA, DE, FL, IL, MD, MA, MT, NV, NH, PA, WA)
  • Completed HIPAA risk assessment within the last 12 months, or budget approved for a fresh risk assessment as part of this project (required before introducing any new PHI-processing technology)
  • Clinician buy-in: at least 2–3 clinicians identified as pilot users who are willing to adopt the technology and provide feedback during the pilot phase
  • Informed consent forms for AI recording drafted and approved by the practice's legal counsel — must be separate from general treatment consent and specific to AI ambient recording
  • If the practice treats substance use disorder (SUD) patients: 42 CFR Part 2 compliance review completed, with data segmentation and consent workflows defined for SUD records
  • Client-designated compliance officer or privacy officer identified within the practice (can be an existing role) to own consent form management and policy updates
  • MFA solution deployed or planned for all user accounts — no exceptions for clinical staff
  • Physical site access for MSP technician to perform Wi-Fi site survey and hardware installation — schedule during non-clinical hours if possible
  • Administrative access to the practice's domain registrar, email platform (Google Workspace or Microsoft 365), and network infrastructure for configuration changes

Installation Steps

Step 1: Conduct Site Assessment and Wi-Fi Survey

Before any procurement or deployment, perform a thorough site assessment. Walk the clinical space with a Wi-Fi survey tool to identify coverage gaps, interference sources, and optimal access point placement. Document the location of every room where care coordination calls will occur. Note proximity to HVAC units, medical equipment, or other sources of audio interference. Measure existing internet bandwidth with a speed test from multiple locations. This assessment determines whether network upgrades are needed and informs hardware placement.

1
Use a Wi-Fi survey tool such as NetSpot, Ekahau, or WiFi Analyzer
2
From a laptop, run a speed test at each clinical room location
3
Or use browser-based speed test: https://www.speedtest.net
4
Document: signal strength (dBm), noise floor, channel utilization
5
Target: -65 dBm or better in every clinical room
Run a speed test from each clinical room location using the CLI tool
bash
speedtest-cli --simple
Note

Schedule this during business hours to capture real-world interference from active equipment. If the practice uses a consumer-grade router (Netgear Nighthawk, Linksys, etc.), plan for a full network upgrade. Budget 4–8 hours for a typical 2,000–4,000 sq ft clinical office.

Step 2: Network Infrastructure Upgrade

Deploy enterprise-grade Wi-Fi 6 access points and configure VLAN segmentation to isolate clinical traffic from guest and IoT devices. This is both a performance requirement (ambient capture needs reliable low-latency connectivity) and a HIPAA requirement (network segmentation). Configure the UniFi Dream Router or existing firewall with at least three VLANs: Clinical (for workstations and audio devices), Guest (for patient Wi-Fi), and Management (for network infrastructure). Set up a dedicated SSID for clinical devices with WPA3 Enterprise if possible, or WPA3 Personal at minimum.

1
Factory reset and adopt the UDR via https://unifi.ui.com
2
Create VLANs in UniFi Network > Settings > Networks: VLAN 10: Clinical (192.168.10.0/24), VLAN 20: Guest (192.168.20.0/24), VLAN 30: Management (192.168.30.0/24)
3
Create Wi-Fi Networks: 'ClinicSecure' on VLAN 10, WPA3, hidden SSID optional; 'ClinicGuest' on VLAN 20, WPA2, bandwidth-limited
4
Configure inter-VLAN firewall rules
5
Adopt and place U6-Pro APs per site survey results
6
Set AP radio channels manually to avoid co-channel interference
7
Enable band steering to prefer 5GHz for clinical devices
UniFi inter-VLAN firewall rule configuration
text
# Inter-VLAN Firewall Rules:
#    - DENY Guest -> Clinical
#    - DENY Guest -> Management
#    - ALLOW Clinical -> Internet
#    - ALLOW Management -> All
Note

If the practice already has a managed firewall (Fortinet, SonicWall, Meraki MX), integrate the UniFi APs in standalone mode or use the existing vendor's AP ecosystem. The key requirement is VLAN segmentation and reliable Wi-Fi 6 coverage. Test post-deployment: run a speed test from every clinical room and verify <50ms latency to cloud endpoints. Document the network topology for the client's HIPAA technical safeguards documentation.

Step 3: Endpoint Hardening and Security Deployment

Before deploying any ambient capture software, ensure all endpoints (workstations, laptops, tablets) meet HIPAA security requirements. Deploy EDR (SentinelOne), MFA (Duo), and verify OS-level encryption is enabled. This step also includes configuring browsers for optimal AI scribe platform performance.

1
Windows 11 - Verify BitLocker encryption
2
If not encrypted, enable BitLocker
3
macOS - Verify FileVault
4
If not enabled, enable FileVault
5
Deploy SentinelOne agent (download from MSP console) — Windows and macOS
6
Deploy Duo Desktop (formerly Duo Device Health) — download from https://duo.com/docs/device-health
7
Configure Duo policies in Duo Admin Panel: Require MFA for all applications, Block access from unmanaged/unhealthy devices, Set session timeout to 8 hours for clinical workflows
8
Configure browser: Install Chrome or Edge (latest stable), Enable auto-updates, Block third-party cookies except for whitelisted AI scribe domain, Install uBlock Origin to reduce page load interference
Windows: Verify and enable BitLocker encryption
bash
manage-bde -status C:
manage-bde -on C: -RecoveryPassword
macOS: Verify and enable FileVault encryption
bash
fdesetup status
sudo fdesetup enable
Deploy SentinelOne agent (Windows and macOS)
bash
SentinelOneInstaller_windows_64bit.exe /SITE_TOKEN=<your_site_token> /quiet
sudo installer -pkg SentinelOne_macos.pkg -target /
Note

For iPads: enable MDM (Jamf, Mosyle, or Microsoft Intune) and enforce passcode, encryption, and managed app deployment. All Apple devices have hardware encryption enabled by default when a passcode is set. For BYOD scenarios (clinicians using personal devices), require enrollment in MDM with a separate work profile/container. This is a HIPAA addressable specification — document the decision either way.

Step 4: Execute Business Associate Agreements

Before creating any accounts or transmitting any PHI to the AI scribe vendor, execute BAAs with all vendors that will handle PHI. This is a legal prerequisite under HIPAA and must be completed before go-live. Collect and file BAAs for: the AI scribe vendor (Twofold Health), OpenAI (if using the API for custom summaries), Deepgram (if used), the secure messaging provider (Paubox or Spruce), and any cloud hosting provider (AWS/Azure/GCP if building custom components).

1
Request BAA from Twofold Health: contact sales@twofoldhealth.com — Verify BAA covers ambient audio recording and cloud processing — Confirm audio auto-purge policy and data retention terms
2
For OpenAI API: sign up for OpenAI Team or Enterprise plan — BAA is available at https://openai.com/policies/baa — Note: BAA requires Team ($25/user/mo) or Enterprise plan
3
For Paubox: BAA included in subscription agreement
4
File all executed BAAs in the practice's HIPAA compliance documentation — Use Compliancy Group portal if deployed
Critical

Do NOT create AI scribe accounts or process any test audio containing real PHI until BAAs are fully executed and countersigned. Use synthetic/test data only until BAAs are in place. For 42 CFR Part 2 practices: verify that the BAA includes qualified service organization agreement (QSOA) language or a separate QSOA. PIMSY with PAISLY is the only vendor with native 42 CFR Part 2 compliance built in — if SUD patients are a significant population, strongly consider PIMSY over general-purpose scribes.

Step 5: Deploy AI Scribe Platform (Twofold Health)

Create the practice's Twofold Health organization account, configure clinician user accounts, customize note templates for care coordination calls, and set up the platform's recording preferences. Twofold Health is a cloud SaaS platform accessed via web browser — no on-premise software installation is required. The platform generates clinical notes from ambient audio in sub-30 seconds.

1
Navigate to https://app.twofoldhealth.com/signup
2
Create organization account with practice admin credentials
3
Enable MFA on the admin account immediately
4
Configure organization settings: Practice name, address, NPI if applicable; Default note format: select based on clinician preference (SOAP for allied health, DAP/BIRP/GIRP for mental health); Audio retention: verify auto-purge is enabled (should be default); Enable 'Care Coordination' note type if available
5
Add clinician users: Use practice email addresses (not personal); Assign appropriate roles (Clinician, Admin, Supervisor); Each clinician receives an activation email
6
For each clinician, configure: Preferred note format (SOAP, DAP, BIRP, GIRP); Default microphone input (will be set at workstation level); Review and customize note templates for care coordination
7
Create a 'Care Coordination Call' custom template with the following fields: Participants and their roles; Key discussion topics; Treatment plan updates; Medication changes discussed; Action items with responsible party and due date; Follow-up scheduling; Patient safety concerns flagged
Note

If using Freed AI instead of Twofold Health: setup is similar but at $99/clinician/month. Freed offers a mobile app for iOS/Android in addition to the web platform. For practices treating SUD patients, strongly consider PIMSY with PAISLY instead — it is the only platform with native 42 CFR Part 2 compliance and ambient scribe built directly into the EHR, eliminating the need for copy-paste workflows.

Step 6: Configure Audio Hardware at Each Workstation

Deploy and configure the Jabra speakerphones and headsets at each clinician workstation. Ensure the operating system recognizes the device as the default audio input/output, and that the AI scribe platform is configured to use it. Test audio quality in each room with a sample recording.

1
Connect Jabra Speak2 55/75 via USB-C cable or USB-A dongle
2
Open Settings > System > Sound
3
Under 'Input', select 'Jabra Speak2 XX' as default microphone
4
Under 'Output', select 'Jabra Speak2 XX' as default speaker
5
Click 'Test your microphone' and verify levels
1
macOS: Go to System Preferences > Sound > Input > select 'Jabra Speak2 XX'
2
macOS: Go to System Preferences > Sound > Output > select 'Jabra Speak2 XX'
1
Download Jabra Direct software from https://www.jabra.com/software-and-services/jabra-direct
2
Run firmware update on all devices before deployment
1
Open the AI scribe platform in browser
2
Start a test recording, speak for 30 seconds at normal volume
3
Verify transcript accuracy and audio clarity
4
Repeat in each clinical room with the room's specific device
Note

For rooms with the Jabra Speak2 75 (conference rooms), place the device in the center of the table, away from HVAC vents, computer fans, and windows. The device's 4-mic beamforming array works best when participants are equidistant. For headsets (Evolve2 55), ensure Bluetooth pairing is completed with the clinician's primary workstation and phone if dual-use is intended. Label each speakerphone with its room number for asset tracking.

Step 7: Build Custom Care Coordination Summary Generator

Deploy a custom middleware component that takes raw care coordination call transcripts (from the AI scribe platform or from the Deepgram API) and generates structured, shareable care coordination summaries using the OpenAI GPT-5.4 API. This is a lightweight Python application hosted on a HIPAA-eligible cloud service (AWS with BAA, Azure with BAA, or GCP with BAA). The component receives a transcript, applies a standardized prompt template, calls GPT-5.4, and outputs a formatted care summary ready for secure distribution.

1
Install prerequisites
2
Create project directory
3
Create .env file (never commit to version control)
4
Create the main application (see custom_ai_components for full code)
5
Deploy to AWS Elastic Beanstalk, Azure App Service, or GCP Cloud Run
Install required Python packages
bash
pip install openai python-dotenv flask gunicorn cryptography
Create project directory
bash
mkdir care-summary-generator && cd care-summary-generator
Create .env file — never commit to version control
bash
cat > .env << 'EOF'
OPENAI_API_KEY=sk-your-api-key-here
OPENAI_ORG_ID=org-your-org-id
FLASK_SECRET_KEY=generate-a-secure-random-key
ALLOWED_ORIGINS=https://your-practice-domain.com
EOF
1
Install EB CLI: pip install awsebcli
2
Initialize: eb init -p python-3.11 care-summary-generator
3
Configure HIPAA: ensure the EB environment uses a VPC with encryption
4
Deploy: eb create care-summary-prod --single --instance-type t3.small
5
Set environment variables: eb setenv OPENAI_API_KEY=sk-xxx
AWS Elastic Beanstalk deployment commands
bash
eb init -p python-3.11 care-summary-generator
eb create care-summary-prod --single --instance-type t3.small
eb setenv OPENAI_API_KEY=sk-xxx
Azure App Service deployment commands
bash
az webapp up --name care-summary-generator --runtime PYTHON:3.11
az webapp config appsettings set --settings OPENAI_API_KEY=sk-xxx
Note

This component is optional if the AI scribe platform's built-in note output is sufficient for care coordination summaries. However, most ambient scribes generate notes optimized for the treating clinician's own chart — they don't produce summaries formatted for sharing with other providers on the care team. This custom component fills that gap. For practices that don't want a custom deployment, the same functionality can be achieved with a structured prompt template that clinicians paste into the OpenAI ChatGPT Team interface (which has a BAA) — see the custom_ai_components section for both approaches.

Step 8: Configure Secure Summary Sharing Workflow

Set up the HIPAA-compliant channel for distributing care coordination summaries to external providers on the patient's treatment team. This involves configuring Paubox encrypted email or Spruce Health secure messaging, creating distribution lists for common care team configurations, and establishing the end-to-end workflow from transcript → summary generation → clinician review → secure distribution.

Paubox Setup (Encrypted Email)

1
Sign up at https://www.paubox.com
2
Configure MX records for the practice domain
3
Verify domain ownership in Paubox admin console
4
Configure user accounts for clinicians who will send summaries
5
Create email templates in Paubox for care coordination summaries
DNS records required for Paubox domain configuration
dns
DNS TXT record: v=spf1 include:_spf.paubox.com ~all
DNS CNAME: selector1._domainkey -> provided by Paubox

Spruce Health Setup (Secure Messaging)

1
Sign up at https://www.sprucehealth.com
2
Create practice account and add clinician users
3
Configure shared team inbox for care coordination
4
Set up external provider contacts (receiving providers)
5
Create message templates for care coordination summaries

Care Coordination Summary Email Template

Standard template for care coordination summary messages — use in either Paubox or Spruce Health
text
Subject: Care Coordination Summary - [Patient Initials] - [Date]
Body: [Standardized summary sections from AI generator]
Footer: 'This summary was generated with AI assistance and reviewed
         by [Clinician Name, Credentials]. Please contact [phone/email]
         with questions or corrections.'
Note

If the practice's EHR has built-in secure messaging (e.g., SimplePractice patient portal, Healthie messaging), that can be used for intra-practice sharing. However, care coordination summaries typically need to reach EXTERNAL providers (the patient's psychiatrist, PCP, school counselor, etc.) who are not on the same EHR. Paubox is recommended for email-centric workflows; Spruce Health for practices wanting a unified communication platform. In some regions, providers still rely heavily on fax — Spruce Health includes HIPAA-compliant e-fax capabilities.

Deploy the informed consent framework for AI ambient recording. This is the most critical non-technical step. Create and deploy: (1) a standalone AI Recording Consent Form separate from general treatment consent, (2) verbal confirmation scripts for clinicians to read at the start of each recorded call, (3) physical signage for rooms where ambient capture is active, (4) an opt-out process that allows patients to decline recording without impacting care, and (5) a consent tracking mechanism in the EHR or compliance platform.

1
Consent form deployment: Upload AI Recording Consent Form to practice's forms system. For SimplePractice: Settings > Client Portal > Intake Forms. For TherapyNotes: Tools > Custom Forms. For Jane App: Settings > Forms > Custom Forms. Add to new patient intake packet and existing patient re-consent workflow.
2
Verbal confirmation script (print and laminate for each room): 'Before we begin, I want to let you know that we use an AI-assisted recording tool to help document our care coordination discussions. The recording will be used to generate a summary of our conversation, which will be reviewed by me before being shared or saved. Your audio is not stored permanently. You may opt out at any time without any impact on your care. Do I have your permission to proceed with recording today?'
3
Room signage template: 'NOTICE: AI-Assisted Recording May Be In Use. This clinical space may use AI-assisted ambient recording technology to support clinical documentation. All recordings are processed securely under HIPAA protections and are not permanently stored. You have the right to opt out at any time. Please speak with your provider if you have any questions or concerns.'
4
Track consent in EHR: Create a custom field: 'AI Recording Consent: Yes/No/Date'. Flag patients who opt out so clinicians see it before each session.
5
Annual re-consent: Set calendar reminders or EHR automated reminders. Re-consent required when vendors or technology change.
Critical

CRITICAL for Illinois practices: Illinois HB 1806 (2025) requires a SEPARATE consent form for AI transcription — a general intake consent is NOT sufficient. Penalties up to $10,000 per violation. CRITICAL for California practices: AB 3030 (effective Jan 1, 2025) requires healthcare providers using generative AI to include disclaimers and provide instructions for contacting a human provider. CRITICAL for 42 CFR Part 2 practices: SUD counseling notes require SEPARATE patient consent beyond standard HIPAA. Consult legal counsel before deploying in SUD treatment settings. All consent forms should be reviewed by the practice's legal counsel before deployment.

Step 10: Pilot Deployment with 2–3 Clinicians

Deploy the complete solution to 2–3 willing clinicians for a 2-week pilot period. Monitor audio quality, transcription accuracy, summary quality, workflow integration, and clinician satisfaction. Collect structured feedback and identify issues before full rollout. During the pilot, every AI-generated summary must be carefully reviewed word-by-word by the clinician — this is both a quality assurance step and a malpractice protection requirement.

1
Audio quality check: Review 2-3 random transcripts per clinician per day. Check for garbled audio, missed speakers, background noise issues. If issues found: adjust mic placement, check network connectivity.
2
Transcription accuracy spot check: Have clinician rate accuracy on 1-5 scale for 3 calls per day. Target: 4+ average (good to excellent accuracy). Document any consistent errors (medical terms, proper nouns).
3
Summary quality review: Clinician reviews every summary before sharing. Check for: hallucinated content, missed discussion points, incorrect attribution of statements to wrong participants. THIS IS MANDATORY — AI hallucinations in clinical summaries create malpractice exposure.
4
Workflow timing: Measure time from call end to summary available. Measure time clinician spends reviewing/editing summary. Measure time to share summary via secure channel. Target: total workflow under 5 minutes per call.
5
Collect weekly feedback: Brief (10-minute) check-in with each pilot clinician. What's working well? What's frustrating or broken? What would make this more useful?
Note

Common pilot issues to anticipate: (1) Speakerphone placement causes echo or picks up hallway noise — move device or close doors, (2) Multi-party calls have speaker attribution errors — this is a known limitation of most ambient scribes; the care summary generator prompt should instruct the LLM to use '[Speaker]' when attribution is uncertain rather than guessing, (3) Clinicians initially spend more time reviewing AI output than they would writing manually — this improves dramatically in week 2 as they learn the tool's patterns and build trust, (4) Patients express discomfort — have the clinician reinforce the consent process and demonstrate the opt-out mechanism.

Step 11: Full Rollout and Clinician Training

After the pilot validates the solution, roll out to all remaining clinicians. Conduct structured training sessions covering: the complete workflow from call initiation to summary sharing, consent procedures, how to review and edit AI-generated content, how to handle opt-outs, and troubleshooting common issues. Provide written quick-reference guides for each clinician's workspace.

Training session agenda (2 hours per group of 5 clinicians):

Hour 1: Workflow and Technology

  • Demo: starting a recording in the AI scribe platform (10 min)
  • Demo: reviewing and editing a generated note (15 min)
  • Demo: generating a care coordination summary (10 min)
  • Demo: sharing summary via Paubox/Spruce (10 min)
  • Hands-on practice: each clinician records a mock call (15 min)

Hour 2: Compliance and Troubleshooting

  • Consent workflow: when and how to obtain consent (10 min)
  • Opt-out procedures: what to do when a patient declines (10 min)
  • AI limitations: hallucinations, the mandatory review step (10 min)
  • Troubleshooting: mic not detected, poor audio, network issues (10 min)
  • Q&A and feedback (20 min)

Post-Training: Quick-Reference Cards

  • One-pager: 'How to Record a Care Coordination Call'
  • One-pager: 'How to Generate and Share a Care Summary'
  • One-pager: 'Troubleshooting Common Issues'
Note

Schedule training during existing staff meeting time if possible to minimize disruption. Record the training session (with staff consent) so new hires can review it later. Designate one clinician per location as the 'AI Champion' — a peer resource for questions and troubleshooting. The MSP should be available for live support during the first week of full rollout.

Custom AI Components

Care Coordination Summary Generator

Type: agent A lightweight Python Flask application that accepts raw care coordination call transcripts and generates structured, shareable care summaries using OpenAI GPT-5.4. The application exposes a REST API endpoint that receives a transcript (plain text or JSON with speaker labels), applies a carefully engineered clinical prompt template, calls the OpenAI API, and returns a formatted care coordination summary. The summary includes standardized sections: Participants & Roles, Discussion Summary, Treatment Plan Updates, Medication Changes, Action Items with Assigned Party and Due Dates, Safety Concerns, and Follow-Up Plan. The application includes authentication, input validation, audit logging, and HIPAA-compliant error handling (no PHI in logs).

Implementation

care_summary_generator.py
python
# Complete Flask application for generating care coordination summaries

# care_summary_generator.py
# Complete Flask application for generating care coordination summaries

import os
import json
import logging
import hashlib
import datetime
from functools import wraps
from dotenv import load_dotenv
from flask import Flask, request, jsonify
from openai import OpenAI

load_dotenv()

app = Flask(__name__)
app.config['SECRET_KEY'] = os.environ.get('FLASK_SECRET_KEY', 'change-me')

# Configure logging - NEVER log PHI
logging.basicConfig(
    level=logging.INFO,
    format='%(asctime)s - %(name)s - %(levelname)s - %(message)s'
)
logger = logging.getLogger('care_summary_generator')

# OpenAI client
client = OpenAI(
    api_key=os.environ.get('OPENAI_API_KEY'),
    organization=os.environ.get('OPENAI_ORG_ID')
)

# API key authentication
API_KEYS = os.environ.get('AUTHORIZED_API_KEYS', '').split(',')

def require_api_key(f):
    @wraps(f)
    def decorated(*args, **kwargs):
        api_key = request.headers.get('X-API-Key')
        if not api_key or api_key not in API_KEYS:
            logger.warning(f'Unauthorized access attempt from {request.remote_addr}')
            return jsonify({'error': 'Unauthorized'}), 401
        return f(*args, **kwargs)
    return decorated

# The core prompt template for care coordination summaries
CARE_COORDINATION_PROMPT = """You are a clinical documentation assistant specializing in care coordination for allied and mental health practices. You will receive a transcript of a care coordination call between healthcare providers discussing a shared patient.

Your task is to generate a structured Care Coordination Summary from this transcript. The summary will be shared with all providers on the patient's treatment team.

IMPORTANT RULES:
1. ONLY include information explicitly stated in the transcript. NEVER infer, assume, or fabricate clinical details.
2. If speaker attribution is unclear, use "[Unidentified Speaker]" rather than guessing.
3. If a medication name, dosage, or clinical detail is unclear in the transcript, flag it as "[VERIFY: unclear in recording]" rather than guessing.
4. Use professional clinical language appropriate for inter-provider communication.
5. Do not include verbatim patient quotes unless clinically relevant.
6. Protect patient privacy: use initials or "the patient" rather than full names in the summary.
7. Flag any safety concerns (suicidal ideation, self-harm, abuse, neglect) prominently at the top of the summary.

Generate the summary using EXACTLY this structure:

---
CARE COORDINATION SUMMARY
Date: [date of call]
Generated: [current date/time] (AI-assisted, pending clinician review)

SAFETY ALERTS:
[List any safety concerns discussed, or state "No safety concerns identified in this call."]

PARTICIPANTS:
- [Name, Credentials, Role] (e.g., "Dr. Jane Smith, PhD, LCSW - Primary Therapist")
- [Name, Credentials, Role]

PATIENT IDENTIFIER: [Patient initials and DOB if mentioned, or other identifier used in the call]

PURPOSE OF CALL:
[1-2 sentence summary of why this coordination call was held]

CLINICAL DISCUSSION SUMMARY:
[3-8 bullet points summarizing key clinical topics discussed, organized by theme]

TREATMENT PLAN UPDATES:
[Bullet points listing any changes to the treatment plan discussed or agreed upon]
[If no changes discussed, state "No treatment plan changes discussed."]

MEDICATION DISCUSSION:
[Any medication changes, concerns, or recommendations discussed]
[If no medication discussion, state "No medication topics discussed."]

ACTION ITEMS:
| # | Action Item | Responsible Party | Due Date |
|---|------------|-------------------|----------|
| 1 | [specific action] | [who] | [when] |
[Include ALL action items mentioned in the call]

FOLLOW-UP PLAN:
- Next coordination call: [date/timeframe if discussed]
- Next steps: [any agreed-upon next steps]

NOTES:
[Any additional context, caveats, or items that don't fit above categories]

---
DISCLAIMER: This summary was generated with AI assistance from an audio recording of the care coordination call. It must be reviewed and approved by a licensed clinician before distribution or entry into the medical record. AI-generated content may contain errors. The reviewing clinician is responsible for verifying accuracy.
---
"""

@app.route('/api/v1/generate-summary', methods=['POST'])
@require_api_key
def generate_summary():
    """Generate a care coordination summary from a transcript."""
    try:
        data = request.get_json()
        
        if not data or 'transcript' not in data:
            return jsonify({'error': 'Missing required field: transcript'}), 400
        
        transcript = data['transcript']
        call_date = data.get('call_date', datetime.date.today().isoformat())
        note_format = data.get('format', 'standard')  # standard, brief, detailed
        
        # Input validation
        if len(transcript) < 50:
            return jsonify({'error': 'Transcript too short to generate meaningful summary'}), 400
        if len(transcript) > 500000:  # ~100k words
            return jsonify({'error': 'Transcript exceeds maximum length'}), 400
        
        # Build the messages
        format_instruction = ''
        if note_format == 'brief':
            format_instruction = '\nGenerate a CONCISE version - limit the Clinical Discussion Summary to 3-4 bullet points and keep the overall summary to one page.'
        elif note_format == 'detailed':
            format_instruction = '\nGenerate a DETAILED version - include comprehensive clinical discussion notes and expand on treatment rationale where discussed.'
        
        messages = [
            {
                'role': 'system',
                'content': CARE_COORDINATION_PROMPT + format_instruction
            },
            {
                'role': 'user',
                'content': f'Call Date: {call_date}\n\nTRANSCRIPT:\n{transcript}'
            }
        ]
        
        # Call OpenAI GPT-5.4
        response = client.chat.completions.create(
            model='gpt-5.4',
            messages=messages,
            temperature=0.2,  # Low temperature for clinical accuracy
            max_tokens=4000,
            top_p=0.95
        )
        
        summary = response.choices[0].message.content
        
        # Log metadata only - NEVER log the transcript or summary (PHI)
        request_hash = hashlib.sha256(transcript[:100].encode()).hexdigest()[:12]
        logger.info(
            f'Summary generated | request_hash={request_hash} | '
            f'transcript_chars={len(transcript)} | '
            f'summary_chars={len(summary)} | '
            f'model={response.model} | '
            f'tokens_used={response.usage.total_tokens}'
        )
        
        return jsonify({
            'summary': summary,
            'metadata': {
                'model': response.model,
                'tokens_used': response.usage.total_tokens,
                'generated_at': datetime.datetime.utcnow().isoformat(),
                'format': note_format,
                'status': 'DRAFT - REQUIRES CLINICIAN REVIEW'
            }
        })
    
    except Exception as e:
        # Log error without PHI
        logger.error(f'Summary generation failed: {type(e).__name__}')
        return jsonify({'error': 'Summary generation failed. Please try again.'}), 500


@app.route('/api/v1/health', methods=['GET'])
def health_check():
    return jsonify({'status': 'healthy', 'timestamp': datetime.datetime.utcnow().isoformat()})


if __name__ == '__main__':
    app.run(host='0.0.0.0', port=5000, debug=False)
requirements.txt
text
flask==3.0.3
gunicorn==22.0.0
openai==1.35.0
python-dotenv==1.0.1
cryptography==42.0.8
Procfile — for deployment
text
web: gunicorn care_summary_generator:app --bind 0.0.0.0:$PORT --workers 2 --timeout 120
Dockerfile — alternative deployment
dockerfile
FROM python:3.11-slim
WORKDIR /app
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt
COPY care_summary_generator.py .
EXPOSE 5000
CMD ["gunicorn", "care_summary_generator:app", "--bind", "0.0.0.0:5000", "--workers", "2", "--timeout", "120"]

Manual Care Summary Prompt Template (No-Code Alternative)

Type: prompt For practices that do not want or need a custom API deployment, this prompt template can be used directly in OpenAI's ChatGPT Team interface (which supports BAAs). The clinician copies the transcript from their AI scribe platform, pastes it into ChatGPT Team with this prompt, and receives a structured care coordination summary. This is the zero-infrastructure alternative to the Care Coordination Summary Generator API.

Implementation

Setup Instructions for MSP

1
Sign up for OpenAI ChatGPT Team at https://openai.com/chatgpt/team/
2
Execute BAA (available in Team plan settings)
3
Create a shared Custom GPT within the Team workspace named 'Care Coordination Summary Generator'
4
Paste the following as the Custom GPT's system instructions:
Custom GPT system instructions
text
# paste into the Care Coordination Summary Generator GPT configuration

You are a clinical documentation assistant for an allied and mental health practice. When given a transcript of a care coordination call, you generate a structured Care Coordination Summary.

RULES:
- ONLY include information explicitly stated in the transcript
- NEVER fabricate, infer, or hallucinate clinical details
- If speaker identity is unclear, write "[Unidentified Speaker]"
- If any clinical detail (medication, dosage, diagnosis) is unclear, write "[VERIFY: unclear in recording]"
- Use "the patient" or initials instead of full patient names
- Flag ALL safety concerns (SI, SH, abuse, neglect) at the very top

OUTPUT FORMAT:

CARE COORDINATION SUMMARY
Date: [call date]
Generated: [today's date] (AI-assisted — REQUIRES CLINICIAN REVIEW)

SAFETY ALERTS:
[List any safety concerns, or "No safety concerns identified."]

PARTICIPANTS:
- [Name, Credentials, Role]

PATIENT: [Initials/DOB as mentioned]

PURPOSE: [1-2 sentences]

CLINICAL DISCUSSION:
- [Bullet points of key topics]

TREATMENT PLAN UPDATES:
- [Changes discussed, or "No changes discussed."]

MEDICATION DISCUSSION:
- [Medication topics, or "None discussed."]

ACTION ITEMS:
| # | Action | Responsible | Due Date |
|---|--------|-------------|----------|
| 1 | ... | ... | ... |

FOLLOW-UP:
- Next call: [date/timeframe]
- Next steps: [agreed actions]

DISCLAIMER: AI-generated summary requiring clinician review before distribution or charting.

Clinician Workflow

1
Complete the care coordination call with AI scribe recording
2
Copy the raw transcript from the AI scribe platform
3
Open the 'Care Coordination Summary Generator' Custom GPT in ChatGPT Team
4
Paste the transcript with the prefix: 'Generate a care coordination summary for this call from [DATE]:'
5
Review the generated summary carefully — check every clinical detail against your memory of the call
6
Edit any errors, add missing context, resolve any [VERIFY] flags
7
Copy the final approved summary
8
Send via Paubox/Spruce to the care team
9
Paste into the patient's EHR chart as a care coordination note

Transcript Preprocessing Pipeline

Type: workflow

An optional data preprocessing workflow for practices using the custom API approach with Deepgram for transcription. This workflow handles: (1) receiving audio from the recording device, (2) sending it to Deepgram for transcription with speaker diarization, (3) formatting the transcript with speaker labels, and (4) passing it to the Care Coordination Summary Generator. This is only needed if the practice chooses to build a fully custom pipeline instead of using an off-the-shelf AI scribe like Twofold Health.

Implementation:

transcript_preprocessor.py
python
# End-to-end pipeline processing audio through Deepgram transcription and
# into the Care Coordination Summary Generator API

# transcript_preprocessor.py
# Processes audio files through Deepgram and prepares for summary generation

import os
import json
import requests
from dotenv import load_dotenv

load_dotenv()

DEEPGRAM_API_KEY = os.environ.get('DEEPGRAM_API_KEY')
SUMMARY_API_URL = os.environ.get('SUMMARY_API_URL', 'http://localhost:5000/api/v1/generate-summary')
SUMMARY_API_KEY = os.environ.get('SUMMARY_API_KEY')

def transcribe_audio(audio_file_path: str) -> dict:
    """
    Send audio file to Deepgram Nova-3 Medical for transcription.
    Returns raw Deepgram response with speaker diarization.
    """
    url = 'https://api.deepgram.com/v1/listen'
    
    params = {
        'model': 'nova-3-medical',  # Medical vocabulary model
        'smart_format': 'true',      # Punctuation and formatting
        'diarize': 'true',           # Speaker identification
        'diarize_version': 'latest',
        'punctuate': 'true',
        'paragraphs': 'true',
        'utterances': 'true',
        'language': 'en-US'
    }
    
    headers = {
        'Authorization': f'Token {DEEPGRAM_API_KEY}',
        'Content-Type': 'audio/wav'  # Adjust based on actual format
    }
    
    with open(audio_file_path, 'rb') as audio_file:
        response = requests.post(url, params=params, headers=headers, data=audio_file)
    
    response.raise_for_status()
    return response.json()


def format_transcript_with_speakers(deepgram_response: dict) -> str:
    """
    Convert Deepgram response into a readable transcript with speaker labels.
    """
    utterances = deepgram_response.get('results', {}).get('utterances', [])
    
    if not utterances:
        # Fallback to paragraphs if utterances not available
        paragraphs = deepgram_response.get('results', {}).get('channels', [{}])[0].get('alternatives', [{}])[0].get('paragraphs', {}).get('paragraphs', [])
        formatted_lines = []
        for para in paragraphs:
            speaker = para.get('speaker', 'Unknown')
            sentences = ' '.join([s.get('text', '') for s in para.get('sentences', [])])
            formatted_lines.append(f'Speaker {speaker}: {sentences}')
        return '\n\n'.join(formatted_lines)
    
    formatted_lines = []
    current_speaker = None
    current_text = []
    
    for utterance in utterances:
        speaker = f"Speaker {utterance.get('speaker', 'Unknown')}"
        text = utterance.get('transcript', '')
        
        if speaker != current_speaker:
            if current_speaker and current_text:
                formatted_lines.append(f'{current_speaker}: {" ".join(current_text)}')
            current_speaker = speaker
            current_text = [text]
        else:
            current_text.append(text)
    
    # Don't forget the last speaker
    if current_speaker and current_text:
        formatted_lines.append(f'{current_speaker}: {" ".join(current_text)}')
    
    return '\n\n'.join(formatted_lines)


def generate_summary(transcript: str, call_date: str, note_format: str = 'standard') -> dict:
    """
    Send formatted transcript to the Care Coordination Summary Generator API.
    """
    headers = {
        'Content-Type': 'application/json',
        'X-API-Key': SUMMARY_API_KEY
    }
    
    payload = {
        'transcript': transcript,
        'call_date': call_date,
        'format': note_format
    }
    
    response = requests.post(SUMMARY_API_URL, json=payload, headers=headers)
    response.raise_for_status()
    return response.json()


def process_care_coordination_call(audio_file_path: str, call_date: str, note_format: str = 'standard') -> dict:
    """
    End-to-end pipeline: audio -> transcription -> formatted transcript -> care summary.
    """
    # Step 1: Transcribe with Deepgram
    print(f'Transcribing {audio_file_path}...')
    deepgram_result = transcribe_audio(audio_file_path)
    
    # Step 2: Format with speaker labels
    print('Formatting transcript with speaker labels...')
    formatted_transcript = format_transcript_with_speakers(deepgram_result)
    
    # Step 3: Generate summary
    print('Generating care coordination summary...')
    summary_result = generate_summary(formatted_transcript, call_date, note_format)
    
    return {
        'transcript': formatted_transcript,
        'summary': summary_result.get('summary'),
        'metadata': summary_result.get('metadata')
    }


if __name__ == '__main__':
    import sys
    if len(sys.argv) < 3:
        print('Usage: python transcript_preprocessor.py <audio_file> <call_date YYYY-MM-DD>')
        sys.exit(1)
    
    result = process_care_coordination_call(sys.argv[1], sys.argv[2])
    print('\n=== FORMATTED TRANSCRIPT ===\n')
    print(result['transcript'])
    print('\n=== CARE COORDINATION SUMMARY ===\n')
    print(result['summary'])

Type: integration A complete informed consent form template for AI ambient recording in allied and mental health settings. This form is designed to meet HIPAA requirements, state recording consent laws (including Illinois HB 1806 and California AB 3030), and emerging best practices for AI in behavioral health. The MSP should provide this template to the practice's legal counsel for review and customization before deployment. This is a clinical-legal document, not a software component, but it is a mandatory integration point in the workflow.

Implementation:

Critical

MUST BE REVIEWED BY PRACTICE'S LEGAL COUNSEL BEFORE USE

AI-Assisted Recording and Documentation Consent Form — Template for Allied & Mental Health Practices
text
# AI-ASSISTED RECORDING AND DOCUMENTATION CONSENT FORM
# Template for Allied & Mental Health Practices
# MUST BE REVIEWED BY PRACTICE'S LEGAL COUNSEL BEFORE USE

---

## CONSENT FOR AI-ASSISTED AMBIENT RECORDING AND DOCUMENTATION

**Practice Name:** [Practice Name]
**Date:** _______________
**Patient Name:** _______________
**Date of Birth:** _______________

### PURPOSE
Our practice uses AI-assisted technology to record and transcribe clinical conversations, including care coordination calls between your treatment providers. This technology helps us create accurate, timely documentation and care coordination summaries to improve the quality and continuity of your care.

### WHAT THIS MEANS
- **Recording:** Audio from your clinical sessions and/or care coordination calls involving your care may be recorded using a microphone in the treatment room or on a phone/video call.
- **Transcription:** The audio recording is processed by an AI (artificial intelligence) system to create a written transcript of the conversation.
- **Documentation:** The AI system generates draft clinical notes and/or care coordination summaries based on the transcript.
- **Human Review:** ALL AI-generated documents are reviewed, edited, and approved by your licensed healthcare provider before being finalized, shared, or entered into your medical record.
- **Audio Handling:** Audio recordings are processed by [Vendor Name], our HIPAA-compliant technology partner. [Audio is automatically deleted after processing / Audio is retained for X days before automatic deletion — customize based on vendor policy].

### HOW YOUR INFORMATION IS PROTECTED
- All audio and text data are encrypted during transmission and storage.
- Our technology vendor has signed a Business Associate Agreement (BAA) as required by HIPAA.
- Audio recordings are NOT used to train AI models and are NOT shared with third parties beyond what is necessary for processing.
- Your information is protected by federal (HIPAA) and state privacy laws.
- [FOR SUD PRACTICES: Your substance use disorder treatment information is additionally protected under 42 CFR Part 2, which provides heightened confidentiality protections. This AI recording consent is separate from and in addition to your Part 2 consent for disclosure.]

### YOUR RIGHTS
- **You may decline this recording at any time** without any impact on the quality or availability of your care.
- If you decline, your provider will document your sessions manually, as was done before this technology was available.
- You may withdraw this consent at any time by notifying your provider or our front office staff.
- You may request information about what AI-generated documentation has been created from your recorded sessions.
- [CALIFORNIA: As required by California AB 3030, you may contact a human healthcare provider at any time regarding any AI-generated communication or documentation by calling [practice phone number] or emailing [practice email].]

### LIMITATIONS OF AI TECHNOLOGY
- AI-generated transcripts and summaries may contain errors. Your provider reviews all output for accuracy.
- The AI system may occasionally miss or misinterpret spoken words, particularly medical terminology, accents, or overlapping speech.
- AI-generated documentation is a tool to assist — not replace — your provider's clinical judgment.

### CONSENT

By signing below, I acknowledge that:

- [ ] I have read and understand this consent form.
- [ ] I understand that my clinical sessions and/or care coordination calls may be recorded and processed by AI technology.
- [ ] I understand that all AI-generated documentation will be reviewed by a licensed clinician before use.
- [ ] I understand that I may decline or withdraw consent at any time without impact on my care.
- [ ] I have had the opportunity to ask questions about this technology and its use.

**Patient Signature:** _______________  **Date:** _______________

**Provider Signature:** _______________  **Date:** _______________

**Witness (if required by state law):** _______________  **Date:** _______________

---

**Consent Declined:**
- [ ] Patient declines AI recording consent. Manual documentation will be used.

**Patient Signature:** _______________  **Date:** _______________

---

*This consent is valid for 12 months from the date of signature and will be renewed annually or when there are material changes to the technology or vendor used.*

*Form Version: 1.0 | Last Updated: [Date] | Next Review: [Date + 12 months]*

EHR Copy-Paste Workflow Automation (Browser Extension Concept)

Type: workflow Since most mental health EHRs (SimplePractice, TherapyNotes, Jane App) lack public APIs, the primary integration method is a structured copy-paste workflow. This component defines the exact workflow steps and a conceptual browser bookmark/snippet that formats the care summary for pasting into common EHRs. For practices on Healthie (which has a GraphQL API), an automated integration path is also described.

Workflow A: Manual Copy-Paste (SimplePractice, TherapyNotes, Jane App)

1
Complete care coordination call with AI scribe recording active
2
Open AI scribe platform (Twofold Health) in browser tab 1
3
Wait for note generation (sub-30 seconds)
4
Review generated note — edit any errors, resolve any [VERIFY] flags
5
If care coordination summary is needed: a. Copy the approved transcript from the AI scribe, b. Open ChatGPT Team (or the Care Summary Generator API interface) in tab 2, c. Paste transcript and generate care coordination summary, d. Review and approve the summary
6
Copy the finalized summary
7
Open EHR in browser tab 3
8
Navigate to the patient's chart > Progress Notes > New Note
9
Select 'Care Coordination' note type (or closest equivalent)
10
Paste the summary into the note body
11
Save/sign the note in the EHR
12
For external sharing: copy the summary into Paubox/Spruce and send to care team

Browser Bookmark Formatter (JavaScript Bookmarklet)

Bookmarklet: Format Care Summary for EHR Paste.
javascript
// Drag this to your bookmarks bar. Select care summary text on the page
// first, then click the bookmark to format and copy to clipboard.

javascript:(function(){
  var text = window.getSelection().toString();
  if(!text){alert('Select the care summary text first, then click this bookmark.');return;}
  // Clean up formatting for EHR plain-text fields
  text = text.replace(/\|/g, ' ').replace(/---/g, '').replace(/\n{3,}/g, '\n\n');
  // Add EHR-friendly header
  var formatted = 'CARE COORDINATION NOTE\n';
  formatted += 'Date: ' + new Date().toLocaleDateString() + '\n';
  formatted += 'Type: Care Coordination Call Summary (AI-Assisted)\n';
  formatted += '---\n' + text;
  formatted += '\n---\nReviewed and approved by: [Provider Name, Credentials]';
  // Copy to clipboard
  navigator.clipboard.writeText(formatted).then(function(){
    alert('Formatted summary copied to clipboard. Paste into your EHR.');
  });
})()

Workflow B: Healthie API Integration (For practices on Healthie EHR)

Push care coordination summaries directly to Healthie EHR via GraphQL API.
python
# Requires Healthie Enterprise plan with API access.

# healthie_integration.py
# Push care coordination summaries directly to Healthie via GraphQL API

import requests
import os

HEALTHIE_API_URL = 'https://api.gethealthie.com/graphql'
HEALTHIE_API_KEY = os.environ.get('HEALTHIE_API_KEY')

def create_care_coordination_note(patient_id: str, summary: str, call_date: str, provider_id: str) -> dict:
    """
    Create a new chart note in Healthie with the care coordination summary.
    Requires Healthie Enterprise plan with API access.
    """
    mutation = '''
    mutation createFormAnswerGroup($input: createFormAnswerGroupInput!) {
      createFormAnswerGroup(input: $input) {
        form_answer_group {
          id
          created_at
        }
        messages {
          field
          message
        }
      }
    }
    '''
    
    # Note: Actual Healthie GraphQL schema may vary.
    # Consult Healthie API docs for exact mutation structure.
    # This is a representative example.
    variables = {
        'input': {
            'user_id': patient_id,
            'form_id': 'care_coordination_form_id',  # Pre-configured form template ID
            'form_answers': [
                {
                    'custom_module_id': 'summary_field_id',
                    'answer': summary
                },
                {
                    'custom_module_id': 'call_date_field_id', 
                    'answer': call_date
                }
            ],
            'finished': True
        }
    }
    
    headers = {
        'Authorization': f'Basic {HEALTHIE_API_KEY}',
        'Content-Type': 'application/json',
        'AuthorizationSource': 'API'
    }
    
    response = requests.post(
        HEALTHIE_API_URL,
        json={'query': mutation, 'variables': variables},
        headers=headers
    )
    
    return response.json()

Workflow C: HIPAA-Compliant Fax (for providers who only accept fax)

1
Copy approved care coordination summary
2
Open e-fax interface (SRFax, Updox, or Spruce Health)
3
Enter recipient fax number
4
Paste summary into the fax body
5
Send

Testing & Validation

Client Handoff

The client handoff should be a structured 2-hour session with the practice owner/manager, compliance officer, and at least one clinical champion. Cover the following:

1
Solution Overview (15 min): Walk through the complete architecture — what hardware is deployed where, what software is running, how data flows from microphone to care summary to EHR to shared communication. Use a visual diagram.
2
Compliance Documentation Handoff (20 min): Deliver a complete compliance package including: (a) list of all vendors with BAA execution dates and filed copies, (b) the AI Recording Consent Form master template with instructions for deployment, (c) the verbal confirmation script and room signage files, (d) network topology diagram for HIPAA technical safeguards documentation, (e) data flow diagram showing where PHI is processed and stored, (f) the practice's updated HIPAA risk assessment reflecting the new AI technology.
3
Day-to-Day Workflow Training Review (20 min): Confirm all clinicians have been trained and can demonstrate: starting a recording, reviewing an AI-generated note, generating a care coordination summary, sharing it securely, entering it into the EHR, and handling an opt-out.
4
Quick Reference Guides (10 min): Hand over laminated or printed quick-reference cards for each workstation: 'How to Record a Care Coordination Call,' 'How to Generate and Share a Care Summary,' 'Troubleshooting Common Issues,' and 'Consent Workflow Checklist.'
5
Success Criteria Review (15 min): Review measurable success criteria together: (a) clinician documentation time reduced by 50%+ for care coordination calls, (b) care summaries distributed to treatment team within 24 hours of call (vs. previous baseline), (c) >90% clinician adoption rate within 30 days, (d) zero consent workflow violations, (e) zero HIPAA incidents related to the new technology.
6
Support and Escalation (10 min): Define the support model: what the practice handles internally (consent management, clinical review of AI output), what the MSP handles (technical issues, vendor liaison, network problems, security incidents), and how to escalate (MSP helpdesk number, SLA response times, emergency contact for security incidents).
7
Ongoing Optimization Roadmap (15 min): Discuss future improvements: custom note template refinement based on clinician feedback, potential EHR migration to a platform with API access (e.g., Healthie), expansion to additional clinical use cases (session notes, intake documentation), and annual technology review.
8
Sign-off (15 min): Have the practice owner sign a project completion acknowledgment documenting: all hardware and software deployed, all training completed, all compliance documentation delivered, and the start date of ongoing managed services.

Maintenance

Monthly Responsibilities

  • Review AI scribe platform usage metrics: active users, sessions recorded, notes generated. Flag any clinicians who have stopped using the system for re-engagement.
  • Verify all endpoint security agents (EDR, MFA) are active and reporting. Remediate any endpoints that have fallen out of compliance.
  • Review and apply firmware updates to Jabra audio devices via Jabra Direct software.
  • Check AI scribe platform for software updates, new features, or changes to terms of service that could affect compliance.
  • Monitor network performance: run speed tests from clinical rooms, review Wi-Fi controller for connectivity issues or interference.
  • Review secure messaging platform (Paubox/Spruce) delivery logs for any failed or bounced summary distributions.

Quarterly Responsibilities

  • Conduct a brief (30-minute) check-in with the practice manager and clinical champion. Review: clinician satisfaction, workflow efficiency, any emerging issues, and feature requests.
  • Review and update care coordination summary prompt templates based on clinician feedback — if clinicians are consistently editing the same sections, refine the prompt.
  • Verify BAA status for all vendors — confirm no vendor changes, acquisitions, or policy updates that affect the BAA.
  • Run a HIPAA compliance spot check: verify encryption, access controls, audit logs, and consent form compliance.
  • Review OpenAI API usage and costs; optimize model selection (e.g., switch to GPT-5.4 mini for routine summaries if quality is sufficient) to manage costs.

Semi-Annual Responsibilities

  • Conduct a formal HIPAA risk assessment update incorporating the AI ambient capture technology. Document any new risks or changes.
  • Review state law updates for recording consent and AI-in-healthcare regulations — this is a rapidly evolving area. Check for new state laws similar to Illinois HB 1806 and California AB 3030.
  • Evaluate AI scribe vendor landscape for any new entrants, pricing changes, or feature improvements that could benefit the practice.
  • Coordinate with the practice's compliance officer on consent form re-authorization for patients approaching 12-month consent expiration.

Annual Responsibilities

  • Full technology review: evaluate whether the current AI scribe platform is still the best fit. Review alternatives, pricing changes, and new capabilities.
  • Hardware refresh assessment: check audio device condition, battery health (for wireless devices), and whether newer models offer meaningful improvements.
  • Complete HIPAA annual risk assessment with the AI technology fully integrated.
  • Renew all software subscriptions and verify BAAs are current.
  • Conduct refresher training for all staff, incorporating any workflow changes from the past year.
  • Review and update the AI Recording Consent Form to reflect any technology or vendor changes.

Escalation Paths

  • Level 1 (MSP helpdesk): Audio device not working, browser/connectivity issues, password resets, basic workflow questions. SLA: 4-hour response, next-business-day resolution.
  • Level 2 (MSP senior tech): Network issues, EHR integration problems, API errors in custom summary generator, security alerts. SLA: 2-hour response, same-day resolution.
  • Level 3 (MSP + vendor): AI scribe platform outages, transcription quality degradation, BAA or compliance issues, data breach investigation. SLA: 1-hour response, continuous work until resolution.
  • Emergency: Any suspected PHI breach, unauthorized access to transcripts/summaries, or patient complaint about recorded session. Activate incident response plan immediately — notify practice compliance officer and MSP security team within 1 hour.
Critical

Any suspected PHI breach, unauthorized access to transcripts/summaries, or patient complaint about recorded session requires immediate action. Activate incident response plan — notify practice compliance officer and MSP security team within 1 hour.

Model/Prompt Retraining Triggers

  • If clinicians report consistent hallucinations or errors in care summaries (>5% of summaries require major edits), review and revise the GPT-5.4 prompt template.
  • If OpenAI releases a new model version (e.g., GPT-4.5, GPT-5), test it against the current prompt with synthetic data before migrating.
  • If the practice adds new service lines (e.g., adds psychiatry, adds group therapy), create new prompt variants optimized for those note types.
  • If Deepgram releases an updated medical model, test transcription quality and switch if accuracy improves.

Alternatives

PIMSY EHR with PAISLY AI (Native Ambient Scribe for SUD Practices)

For practices that treat substance use disorder (SUD) patients, replace the Twofold Health + separate EHR approach with PIMSY, a behavioral health EHR that has an ambient AI scribe (PAISLY) built directly into the platform. PIMSY is the only vendor with native 42 CFR Part 2 compliance and integrated ambient documentation, eliminating the need for copy-paste workflows, separate AI scribe subscriptions, and complex compliance layering.

Freed AI Instead of Twofold Health

Use Freed AI ($99/clinician/month) as the ambient scribe platform instead of Twofold Health ($49/clinician/month). Freed offers broader specialty support (20+ specialties including allied health), a mobile app for iOS/Android, and has gained significant traction among individual practitioners. The implementation workflow is nearly identical.

Eleos Health (Enterprise Behavioral Health Platform)

For larger behavioral health organizations (20+ clinicians, multiple locations), deploy Eleos Health instead of a consumer-grade AI scribe. Eleos is the most widely deployed enterprise-grade behavioral health AI platform, with $120M+ in funding, clinical outcome measurement integration, supervision workflows, and quality assurance tools built on top of ambient documentation.

Fully Custom Pipeline (Deepgram + OpenAI API, No Off-the-Shelf Scribe)

Instead of using an off-the-shelf AI scribe like Twofold Health or Freed, build a fully custom ambient capture pipeline using Deepgram Nova-3 Medical for transcription and OpenAI GPT-5.4 for note and summary generation. This approach gives the MSP full control over the workflow, data handling, and output formatting, and can be offered as a white-labeled managed service.

ChatGPT Team with Manual Workflow (Lowest Cost, No Custom Development)

Skip all custom development and use only the off-the-shelf AI scribe (Twofold Health) for transcription plus ChatGPT Team ($25/user/month, BAA available) with the custom prompt template for care coordination summary generation. Clinicians copy transcripts from the AI scribe and paste them into a Custom GPT in ChatGPT Team to generate summaries. No API deployment, no custom code, no cloud hosting needed.

Want early access to the full toolkit?