Move your team from Heidi Health to Freed.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Freed — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Heidi Health is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Both tools operate as ambient AI scribes: the clinician starts a recording session and the tool listens to the patient encounter, then generates a structured clinical note. Moving from Freed to Heidi: create a Heidi account and install the web app, desktop app, or mobile app; select a matching template (standard SOAP or a custom one); tap the record button at the start of the next consult; review and edit the generated note. Moving from Heidi to Freed: download the Freed iOS or Android app or use the web interface; tap 'Capture conversation' to record; Freed's ASR layer handles specialty vocab and background noise and produces a SOAP note inline. In both directions, existing notes from the prior tool should be exported (copy/download) before switching, as neither platform imports the other's history. Freed markets the capability as saving ~2 hours/day for 26,000+ clinicians; Heidi offers unlimited transcription on all plans including Free.
- Warning: Freed's ASR is tuned specifically for SOAP note structure and includes a hallucination-check stage; Heidi generates notes according to the selected template, so note structure differences may require template customisation on Heidi to replicate Freed's output format.
- Warning: Freed supports audio file upload for sessions already recorded; Heidi also supports uploading existing audio, but the workflow differs — check platform-specific docs before relying on batch import of backlogged recordings.
- Warning: Neither product imports the other's historical note library, so historical notes must be exported from the source EHR or the tool's own export before decommissioning the prior subscription.
Both tools push finished notes into the EHR, but the mechanism differs. Freed uses a Chrome extension that maps note fields into any browser-based EHR open in Chrome with no EHR API or IT approval needed (setup under one minute). Heidi offers two paths: a Chrome extension for copy/push into browser-based EHRs, and formal API integrations for named systems (athenahealth via Athena Marketplace, Epic via Hyperspace/Hyperdrive/Haiku, eClinicalWorks via Vim, Oracle Cerner via PowerChart/FirstNet). Moving from Freed to Heidi: install the Heidi Chrome extension for an immediate like-for-like replacement of Freed's Chrome-extension push; then check Heidi's integrations page to see if your EHR has a native push integration (if so, upgrade to the Practice tier and configure it via the relevant marketplace listing). Moving from Heidi to Freed: install the Freed Chrome extension; note that Freed has no formal API integration path for any EHR — the extension is the only transfer mechanism.
- Warning: Freed's EHR push is gated to the Premier tier and Groups; the Starter and Core tiers require manual copy-paste. Heidi's full push-to-chart integrations (athenahealth, Epic, eCW, Cerner) are gated to the Practice tier — the Clinician tier has only limited EHR integration, and lower tiers are copy-paste only.
- Warning: Freed's Chrome extension works with dozens of browser-based EHRs without IT involvement; Heidi's API integrations for Epic and Cerner require coordination with the EHR's IT or marketplace team and may have enterprise approval steps.
- Warning: Freed's approach is desktop/Chrome-only; if clinicians use the EHR in a native app (not a browser tab), Freed's extension cannot push and manual copy-paste is required. Heidi's named integrations may support native app workflows depending on the EHR vendor.
Both platforms surface billing and clinical codes from the visit so the clinician can review them without a separate coding step. Freed surfaces ICD-10, CPT, and E/M code suggestions inline in the generated note; clinicians review them there and carry them into billing. Heidi surfaces ICD-10 and SNOMED codes via Ask Heidi: after a session, type a prompt such as 'find codes for this visit' in the Ask Heidi bar and Heidi returns relevant codes drawn from the transcript and note context. Moving from Freed to Heidi: after each session, prompt Ask Heidi for codes; codes can be inserted into the note or copied to the billing system. Moving from Freed to Heidi, set up a saved Ask Heidi prompt ('give me ICD-10 and CPT codes for this visit') to replicate the inline suggestion workflow. Moving from Heidi to Freed: no setup is required — Freed automatically suggests codes inline once the note is generated.
- Warning: Freed includes CPT code suggestions (historically flagged as beta); Heidi's coding via Ask Heidi emphasises ICD-10 and SNOMED but does not explicitly document CPT codes, which may mean a gap for US procedural billing.
- Warning: Freed's coding is gated to the Core tier and above on the productised plans; Heidi's coding workflow (session status / coding feature) is gated to the Clinician tier and above — Free users get only the limited monthly Ask Heidi allowance, which may not cover routine per-visit coding.
- Warning: Neither tool is a certified standalone coding or revenue-cycle-management (RCM) platform; both position coding suggestions as a convenience review layer, and billers should validate codes before submission.
Both tools support clinical documentation for encounters conducted in languages other than English and for mixed-language visits. Freed handles 90+ languages and follows mid-visit code-switching (e.g. English and Spanish in the same encounter) without clinician intervention, always outputting the SOAP note in English. Heidi requires the clinician to select the consultation language before starting the session; transcription and note generation then proceed in that language. Moving from Freed to Heidi: before each non-English session in Heidi, set the language in the session settings; confirm the note output language matches your EHR requirements (Heidi may generate the note in the selected language rather than English — verify with a test session). Moving from Heidi to Freed: no language pre-selection is needed; Freed auto-detects and follows code-switching within the visit.
- Warning: Freed explicitly documents code-switching support (conversations that switch languages mid-visit); Heidi requires pre-selecting one language before the session starts and does not document automatic mid-visit language switching — mixed-language encounters may not transcribe accurately on Heidi.
- Warning: Freed's multilingual node carries a lower confidence score (0.55), indicating the 90+ language claim comes from marketing rather than a fully verified technical spec; Heidi's exact language count (110+ reported by secondary sources) is similarly not confirmed in first-party docs.
- Warning: Freed outputs the clinical note in English regardless of the visit language, which suits US EHR workflows; Heidi's output language depends on the template and session language setting, so teams with English-only EHRs should verify Heidi produces English notes from non-English sessions.
Both platforms allow clinicians to shape note structure through specialty templates and custom builders. Moving from Freed to Heidi: in Heidi, navigate to Templates and recreate your Freed specialty template field-by-field using the custom template builder; Heidi's community template library may already contain a matching format for common specialties (family medicine, mental health, allied health). Moving from Heidi to Freed: Freed ships specialty-specific templates (psychiatry, family medicine, pediatrics, OB/GYN, orthopedics, emergency medicine, and others); use Freed's 'Custom template builder' (Core tier and above) to add any custom sections. In both cases, run 2–3 test sessions after switching to confirm note output matches expected format before relying on the template in production.
- Warning: Freed's 'Learn my format' self-learning feature personalises notes from a clinician's own edits over time; Heidi does not document an equivalent automatic style-learning mechanism, so customisation on Heidi is entirely manual via the template editor.
- Warning: Freed's instant template builder and AI editing assistant are gated to the Core tier and above; the Starter tier gets specialty templates only. Heidi's custom/advanced templates are unlimited only on the paid Clinician tier and above — Free users get only 10 advanced actions per month, which covers template use.
- Warning: Heidi's team plans include a shared team template library, which Freed's Groups plan also supports; individual plan migrants will need to rebuild templates manually on the new tool.
Both tools generate secondary documents from the visit — patient-facing instructions and clinical letters — so clinicians can produce referrals, sick notes, and after-visit summaries without retyping. Freed auto-generates plain-language patient follow-up instructions and 14+ clinical letter types (referrals, sick notes, return-to-work letters, caregiver letters) after each visit. Heidi generates 'downstream documents' via Ask Heidi or saved document templates: after the consult note is ready, prompt Ask Heidi (e.g. 'write a referral letter to cardiology based on this visit') or select a downstream-document template; output includes referral letters, patient summaries, discharge summaries, handover notes, and care plans. Moving from Freed to Heidi: for each Freed letter type, create a matching saved document template in Heidi or write a reusable Ask Heidi prompt; run one test session per document type to verify output. Moving from Heidi to Freed: Freed's output is limited to its 14+ pre-defined types; if Heidi's more flexible prompt-based documents cover types not in Freed's list, check whether Freed's 'Custom template builder' can replicate them.
- Warning: Freed's patient instructions and letter generation are gated to the Premier tier and Groups; Starter and Core users cannot auto-generate letters. On Heidi, document generation is unlimited on paid plans but 'Document & session sharing' (sharing with patients or colleagues) is gated to the Clinician tier and above.
- Warning: Freed keeps patient instructions in the language spoken during the visit (native-language instructions); Heidi generates downstream documents in the language configured in the template or as requested via Ask Heidi — verify language behaviour on Heidi before replacing Freed for non-English patient instruction use cases.
- Warning: Freed's 14+ types are pre-structured and require no prompt engineering; Heidi's flexibility via Ask Heidi means output quality depends on how the prompt is written, which may require iteration for clinicians who are not experienced with AI prompting.