EHR Integration Overview
Scribeable detects 15+ EHR systems. Web-based deployments get direct insertion; Citrix-hosted deployments get a guided clipboard workflow. Support tier depends on your deployment, not the vendor.
On this page
How support tiers work
How the extension behaves in your EHR depends on how your organization deploys it:
Verified
Selectors validated against a live sandbox or production instance. Updated as EHR versions change.
Best-effort
Direct insertion works in most web-based deployments; clipboard fallback fires automatically when a specific field isn't recognized.
See the verification roadmapfor what's moving from Best-effort to Verified next.
Supported EHR Systems
The Chrome extension auto-detects your EHR. Below is what to expect, organized by deployment type.
Web-based (direct insertion, Best-effort)
Epic Hyperdrive
Modern Epic web client. Smart Phrase formatting preserved.
Oracle Health Cloud
Newer Oracle Health (Cerner) web deployments.
athenahealth
Always web-based.
Meditech Expanse
Newer web-based Meditech.
NextGen
Web portal.
Allscripts / Veradigm
Web portal; thick-client falls back to clipboard.
eClinicalWorks
Cloud web platform.
DrChrono
Web-native ambulatory.
Practice Fusion
Web-native ambulatory.
Citrix / thick-client (clipboard workflow)
These deployments appear to the browser as pixel streams; there is no DOM to query. The extension auto-routes to a section-by-section clipboard workflow with paste guidance. Native desktop automation is out of scope for a browser extension.
Epic Hyperspace
Still the majority of Epic deployments today.
Cerner PowerChart (Citrix)
Legacy PowerChart desktop.
Meditech (legacy)
Pre-Expanse thick client.
Detection + generic field mapping
Detected automatically. Dedicated selectors aren't merged yet — the generic mapper works for standard note/encounter fields. These are prioritized on the verification roadmap.
Kareo / Tebra
Web-native small practice.
AdvancedMD
Web-native practice management.
Greenway Health
Thick client + portal.
Epic MyChart
Patient portal — detection only, read-only by design.
Don't see your EHR? The generic detector works on most web-based systems, and the clipboard workflow is universal. Tell us your setup to get it prioritized.
How It Works
Scribeable integrates into your existing EHR workflow in four steps:
- Record: Capture the patient encounter on your iPhone, iPad, Apple Watch, or web dashboard
- Generate: AI generates a complete clinical note with ICD-10 codes in under 60 seconds
- Review: Edit the note as needed in the app or on the web dashboard
- Insert: Click the Chrome extension icon to drop the note directly into your EHR — the extension detects your EHR, identifies the note field, and inserts the text automatically
Browser Extension Features
The Scribeable Chrome extension does more than copy-paste:
- Auto-detection: Recognizes which EHR you're in and adjusts behavior accordingly
- Field mapping: Identifies note input fields (rich text editors, textareas, contenteditable) and inserts directly
- Section-by-section insertion: Insert individual note sections into separate EHR fields when your EHR uses a template format
- Smart phrase detection: Recognizes and preserves EHR smart phrases and dot phrases
- 6-digit code transfer: Securely link your phone recording to the extension with a one-time code
- Clipboard fallback: If direct insertion isn't available (e.g., in Citrix), copies to clipboard for manual paste
Getting Started
- Install the Scribeable extension from the Chrome Web Store
- Open your EHR and navigate to a patient chart
- Generate your note in the Scribeable iOS app and get the 6-digit code
- Click the Scribeable extension icon and enter the code
- The extension auto-detects your EHR and inserts the note
For detailed setup instructions for your specific EHR, see the dedicated integration guides below.
Security & Compliance
All data handling between the extension and your EHR is:
- HIPAA compliant with signed BAA
- Encrypted end-to-end (AES-256 at rest, TLS 1.3 in transit)
- Zero PHI stored in the extension — notes are fetched on-demand and never cached locally
- Audited and logged