Overview: Autoscriber Integrating Options

📌 Introduction

Autoscriber is a clinical digital scribe and AI assistant that does far more than just transcribe. It listens to doctor-patient conversations and intelligently generates structured documentation in real time. By automating note-taking, form completion, and even responding to clinical queries, Autoscriber helps clinicians spend less time on documentation and more time on patient care.

This guide is designed to help EHR developers understand the available integration methods and how to seamlessly incorporate Autoscriber into their platform - whether through a lightweight widget, embedded app or API.

🔁 Integration Methods

	Embedded Web App	Scribe SDK
Use Case Fit	Perfect for EHRs wanting a simple integration with Autoscriber's digital AI scribe and is happy to embed Autoscriber's UI in an iframe, with the ability to sync the resultant note with the EHR.	The scribe SDK automatically generates structured clinical documentation from medical conversations and posts them back to your EHR via API.
Capabilities	Transcribe consultations or medical dictations Generate structured summaries and coded FHIR data elements Can launch contextually (e.g., with patient name and gender) Return results to EHR via API Minimal setup with flexible integration points outside the core UI	Transcribe consultations or medical dictations Generate structured summaries and coded FHIR data elements Seamlessly integrate with existing EHR workflows and UIs Supports automation of form population using API responses
Delivery Method	Embedded via an iframe	RESTful API
Data Output Format	Structured JSON	Structured JSON
Authentication	API Key and token-based authentication	API Key and token-based authentication
Customisation Options	Theming, behaviour via config	Full control over integration, UI and data handling
EHR UI Changes	Minimal, just to create the space for the iframe	Full UI development
Latency / Real-Time	Real-time transcription and feedback in iframe, near real-time when synced with EHR	Near real-time processing
Ideal For	Fast adoption required with minimal dev resources	Deep integration required where EHR wants control over the UI
Environments	Prod, which can be integrated into the EHRs Test and Prod environments	Prod, which can be integrated into the EHRs Test and Prod environments
Security Considerations	GDPR, NEN 7510 & ISO 27001 compliant	GDPR, NEN 7510 & ISO 27001 compliant
Typical Time to Integrate	1-3 weeks	3-6 weeks (depending on EHR API maturity)
Link to Dev documentation	Here	Here

🏗️ Architecture Diagrams

The three integration methods have different architectures, which may influence which option is chosen. These can be seen below.

Embedded Web App

The embedded web app option will require a section of the EHR real-estate to allow for the embedding of the Autoscriber app via an iframe.

Scribe SDK

The scribe API option allows for complete customisation of the EHR UI, which will be populated with the results from the Autoscriber APIs.